View Full Version : Xvid bug?
sapient
19th April 2003, 00:24
Hi,
Every time I try to encode using xvid (koepi's or nic's latest build), virtualdubmod 1.14.13.2v2 and avisynth 2.51 I get an error:
"VIRTUALDUBMOD caused an invalid page fault in
module XVID.DLL at 01af:0451a75d."
ususally followed by multiple instances of:
"VIRTUALDUBMOD caused an invalid page fault in
module KERNEL32.DLL at 01af:bff87ede."
My settings are:
2pass-1st pass, motion search precission 6, quantization H.263, vhq 1, chroma motion on, b-frames 2 and everything else on default.
My os is win98se
Is this a bug? Am I doing something wrong?
sapient
Koepi
19th April 2003, 09:40
do you overclock your system? check your memory and harddisk, looks like a hardware failure.
Regards
Koepi
kilg0r3
19th April 2003, 11:00
Well, since I installed FFvfw, I am also gettingsome wierd error messages with vdm. So ...
For stability testing your cpu and ram please use prime95! Do not rely on sandra! If preime says it is stable, it is.
sapient
19th April 2003, 20:42
I do not overclock and I have no hardware problems... I haven't done a thorough test with a special utility (except sandra), but I do not get any errors in any other programs, including games and other resource demanding apps, for over a year. Divx works just fine, too. I have not installed FFvfw. The system is recently formatted, so there is no registry clutter or any other problems associated with an aged installation.
For all of the above reasons, I would think that this has something to do with xvid.
My system is an athlon @ 1200 with 256mb ram if that is any help. I have used older versions of xvid under winxp a few months back on the same system with no problems. (I am using win98se now)
sapient
Koepi
20th April 2003, 09:54
...so now you're using a FAT file system. Maybe your pagefile became corrupted. Maybe some dll's got replaced by some weird programs.
It's definatly no fault of xvid, else far more people would have that problem.
Best in this situation is to use a real OS and not an DOS-extender *hint*
Best regards
Koepi
Nic
20th April 2003, 10:31
Have you tried reseting XviD settings? (i.e. pressing the defaults button/removing xvid settings from the registry)
Have you tried it in standard VirtualDub?
Have you tried to encode different clips or are you trying the same clip over and over?
Do the error messages occur as soon as the encoding starts or actually someway through the encoding process?
Whenever reporting bugs, please give as much information as possible, no matter how verbose. Without it you won't recieve much help im afraid.
-Nic
sapient
20th April 2003, 13:00
Testing a little bit more, I found that the problem appears only when I use hinted ME. It appears with mpeg type quantization too, and with vhq 0. Note also that I have max I-frame interval @ 250, although I don't think it matters.
Hinted ME seemed to work when I was using xvid a few months back. If it's known to be broken, I apologise, I didn't know.
@koepi
I have tried this more than once (so it can't be a problem of a corrupted page file). I have also tried reinstalling xvid and vistualdubmod and I am guessing that any other dlls used are the same as with divx.
@nic
The error occurs immediately after starting the encoding. I have tried resetting the settings. I have tried 2 different clips of different resolutions (always mod16) and using different filters in avisynth. I have not tried standard virtualdub since I am using avisynth 2.51 and working in YV12
sapient
Selur
20th April 2003, 13:03
"when I use hinted ME"
*gig* If I remember right "hinted ME" is broken a long time :D
(and if I also remember right there was a thread, which had the conclusion that the best way would be not to have tried it in the first way)
Cu Selur
Ps.: btw. hinted ME / MV file also is broken / not present in DivX 5.0.4 *gig*
Koepi
20th April 2003, 13:03
hinted ME is broken. It never was reported that it got fixed.
I think i'll remove it completely from the GUI in my next build.
Koepi
Selur
20th April 2003, 13:05
"I think i'll remove it completely from the GUI in my next build."
Man, I've been waiting for this. Good idea. :)
Cu Selur
sapient
20th April 2003, 13:28
I apologise again, I have been out of touch for a while.
@selur
using the mv.info file option still exists in divx 5.04. I haven't tried the final, but it was working in the betas.
cult
20th April 2003, 16:24
From what I ve heard its broken in 5.04 final too
Acaila
20th April 2003, 18:57
Indeed it is, check this (http://forum.doom9.org/showthread.php?s=&postid=298901#post298901).
Decryptor
3rd May 2003, 09:06
I have a tiny Noob question here: it involves Xvid and VirtualDub, so I thought i'd post it here...
I recently switched over from DivX 5 to Xvid, and must say that even with the standard settings the quality of Xvid is far better than that of DivX.
I usually start the encoding process at night using VirtualDub's job control, and here's my question: When I check out the job status in the morning, Xvid conversion was always 'Done (warnings)'...
Is there a log-file for these warnings? Where can I see what went wrong ?
I also noticed that the Xvid movie has less frames than the original (about 30-40 less). (can it be that frames where dropped during the End-credits encoding ?)
However: if I scan the video stream for errors, no errors occurred.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.