Xvid Bug

[kastro68]

I get big, huge, gigantic blocks; it does'nt occur often, but usually occurs where there is a scene change, or lots of flashing or action.

You can usually get it to appear by jumping forward and back in time quickly, repeatedly.

I get the problem when DX50 B-VOP compatibility is not ticked.


I'm not sure whether or not this bug has already been reported because exams are near and I don't have time to keep up to date with all the posts.

-Using koepies oct 22 build
-I do 2 pass encode with h.263 on first pass, mod on 2nd pass
-motion search 6
-everything else is on default
- One B frame at 200 percent

I tried both Xvid Fourcc and DX50 fourcc

also when Nics DSF is used, there is some minor bleeding at left edge of video... very obvious when there is lots of red in the frame.

[kastro68]

I just installed Nics 23 oct build

bleeding is still there...well, it doesn't really look like bleeding, it lookes more like there are stitches on the left edge of the video when Xvid fourcc is used.

and the stitching appears regardless of whether or not DX50 B-VOP compatibility is used.

haven't had time to check if blocks are still there with 23 build though.

[Koepi]

I'm quite sure it's a usual setup problem - tweak the right value and the problem is gone.

Please choose a better topic next time!

If you can narrow down what "bug" you're meaning some time later it would be nice to know, but your description is somewhat too useless as _everything_ we need for analysis is missing.

Btw., DivX50 FourCC isn't the smae as DivX50 BVOP compatibility.
It's recommanded to use divx50 bvop compatibility as that mode bframes are treated more correctly. Since bframe decision is dynamically even in 2nd pass I can't recommand using it for final encodes yet, it will for sure mess up the result, it would look nicer with propper 2pass support.

So, if your result is just deriving from overquantized bframes then please consider using a stable build instead of writing xvid is buggy - and then you write something which is immanent and mentioned nearly 100 times now. (look at the bframes in xvid sticky).

Regards
Koepi

[Abel]

I also get these huge blocks like kastro68 at some scene changes, but only when using nic's xvid.ax. With ffdshow these artifacts disappear, but the image quality degrades a lot. (using b-frames and no q-pel)

[kastro68]

Originally posted by Koepi


Btw., DivX50 FourCC isn't the smae as DivX50 BVOP compatibility.




I am aware of the difference. :)


It's just that Nics DSF isn't working for me right now...it has never worked properly for me... I am starting to think that it might be my video card, because no one else seems to experience the same problem.
---

"tweak the right value and the problem is gone"
What value do I tweak??? :confused:

---

The setup that works for me without any problems(that i am aware of):

-divx50 bvop ticked, solves the blockiness issue
-and DX50 fourCC, solves the stitching

PS: I don't use ffdshow

---
I am aware of the problems with development builds... just thought i report the bugs in the hope that it can be fixed for for future builds.

[Gaia]

Katstro68: This is not a bug. You are just doing somenthing wrong. Like Koepi said it must me be your settings. I have tested all these dev-builds quite a lot and i have never seen this "bug" you trying to descripe!

Nic's decoder has always worked fine so it's your system!

I think this forum have became real boring after Nic and Koepi started to release those dev-builds. Just full of senseless bug reports, questions which have been answered in other treads etc. People just use stupid settings and report it as a bug(i know i have done this once but i solved i myself) etc.

[kastro68]

Like I said, it is probably a hardware issue.


I am perfectly content using DX50 fourCC, no big deal. I just use whatever works for me. You can use whatever works for you.

And another note, someone has to report bugs...but hey, I don't have to do it anymore. Well, I refuse to report anymore bugs, I'll just sit back and let others do the testing.

[Rrrough]

@kastro68

come on, chill, please. don't get angry because of some people's arrogance using the "stupid" label always and everywhere, just because they think they've seen all and know all, but don't come up with ANY help.
this person is doing that on another thread as well, telling people it's their stupidity and it's best if they format their windows partition. but this shouldn't keep anyone from testing and reporting.

cheers

[Gaia]

What bothers me is bug reports like this"I tried this and that build and it crashed". No details, no nothing. Or i got blocks with that build and didn't get blocks with next build. Even if nothing or very little is chanced in CVS somepeople claim they got better results with latest build.

If you don't know formating and reinstalling OS can often solve crashing problems, especially if you have lots of different filters installed. Formatting and reinstalling have solved often lots of issues with my system. That's why i adviced to do what because i can't think anything else if all the settings are fine etc.

Reason why i have called some people "stupid" is because i have tried these dev-buils with 3 different systems(Duron(at home),XP(friend's system), and P4(at work))without one single crash. I had few crashes with very first dev build but i did somenthing wrong, stupid settings.
I just wanted to point out that it's not nessecary a bug if you guys get those crashes. Maybe it's Windows releted problem, i haven't tested them with XP.

[iago]

@Gaia,

Sorry pal, but in my humble opinion, whatever the reason is, it's not a favourable attitude to call others "stupid"! I guess rather than rationalizing why you use this word, it would be much better to apologize to everyone here.

regards,
iago

[Rrrough]

I think this forum have became real boring after Nic and Koepi started to release those dev-builds. I feel sorry for you. I still think it's very interesting.

"I tried this and that build and it crashed". No details, no nothing. You admitted that you got crashes with motion search 6 and bframes and with interlacing filters WITHOUT posting a single line of your avisynth script or your settings. You accuse people of using stupid settings WITHOUT ever telling what settings YOU use

If you don't know formating and reinstalling OS can often solve crashing problems, especially if you have lots of different filters installed. true, but if a lot of people have the same problem, the probability for this is very small. doing this implicates a great effort, backing up important data, installing all important programs afterwards, etc. (I know how to use Ghost, and I'm using it quite often, but it's not true for everyone, though) Thus it's better to try to exclude every other possibilities.

Reason why i have called some people "stupid" is because i have tried these dev-buils with 3 different systems(Duron(at home),XP(friend's system), and P4(at work))without one single crash. that doesn't guarantee that you can reproduce every bug/error/whatever

I had few crashes with very first dev build but i did somenthing wrong, stupid settings. great that you have such a great personal insight, but it could be useful for others telling WHAT you did wrong...

I don't want to start a personal flamewar with you, but I don't like the way you're labelling people as "stupid". maybe there are a lot of superfluos bug reports from people who don't know better, but do you really prefer stopping people from testing and reporting ? that's the way, some problems/bugs with xvid have been discovered/solved in the past. and a friendly reminder can have the same effect, telling people that their problem is not a real bug, because of similar personal experiences, and the way you solved them.

[Gaia]

Ok ok, i am very sorry. No offence and i didn't call anyone stupid. No hard feelings i am very sorry about everything i have posted here recently. No more stupid wars.

I use very basic avisynt scripts, here's one example:

mpeg2source("C:\DVDVOLUME\movie.d2v",cpu=0,lumoff=-2)
UnFilter(5,5)
crop(0,77,720,422)
LanczosResize(624,336)(i use Bicubic or LanzosResize)

I have also tried Convolution3D without problems. I haven't tested scripts with lots of different filters because i don't normally use them. If i am not happy with the results i just use higher bitrate and do 2CD rip. I have no experience of capturing. I use only DVD sources.

Currently i don't use Alt. curve scaling, i disable it. I use linear scanling or StatsReader, i think they both preserve details slightly better. They are also easier to use, no need to worry about lots of settings. I have used Alt.curve scaling before dev-builds so i am familiar with it.

For B-frames encoding i use MPEG quantization and Custom matrix for normal encoding.

No ME hints. I have tried QPel but i was not happy with the results so i have done only very small tests with it. No full movies.

My B-frames settings are 2 and 200% B-VOP compatibility on. Motion search 5.

My "stupid" settings:

I got crashes with first dev-builds because i tried to use QPel together(motion search 6) with B-frames.

Got crashes just 2 frames before end of second pass if fourcc used was "DIVX", with xvid no problems. This made me almost mad but solution was very simple.

I have tried Decomb and few other interlacing filters and it always crashed during first pass. I haven't reported it because i have seen posts about it and i personally don't need interlacing. Xvid's Interlacing mode works fine, no crashes. Can't give right now example of those scripts but nothing special, very simple scripts

I have only done 2-pass testing with these builds. I can't confirm that other encodings modes work with B-frames.

I hope this helps, no offence, no more calling anybody's settings stupid.

[MaTTeR]

Originally posted by Gaia
I have tried Decomb and few other interlacing filters and it always crashed during first pass.
I had this happen a few times last week also, can't remember which dev build I had installed at the time though. I switched from Decomb to TomsMoComp and things were fine.

[Rrrough]

ok, apology accepted, no offence taken.
and sorry if I offended you.
thank you for clarifying.

cheers