Why are you trying to save the result in Uncompressed RGB after it's been converted is YV12?
As a test, make sure you have mencoder (it's part of MeGUI's updates, in the tools/mplayer folder). If you don't want to edit the Windows PATH to include it*, then just copy mencoder.exe and mplayer subfolder (not the main mplayer directory, the one residing inside it) to wherever your script is. Go into the mplayer folder and open up mencoder.conf in a text editor. Then copy and paste this over the stuff that's in there, then save it:
- Code: Select all
ass=no
subcp=enca:ru:cp1251
fontconfig=no
nosound=yes
autoexpand=no
ovc=lavc=yes
lavcopts=vcodec=ffvhuff:context=1:vstrict=-1:pred=2
ffourcc=HFYU
force-avi-aspect=1/1
That configuration will output a YV12-mode HuffYUV file. If you use ffdshow to read HuffYUV, then everything'll be fine. The reason I recommend that particular format and decoder combo is because it's freakin' fast on playback.
*Putting it in Windows' PATH will make it available throughout your system, without having to have the physical exe residing in the directory you're in. Alternately, you can stick it (and the 'mplayer' folder) in C:\WINDOWS, which does essentially the same thing.
Now, open up a command prompt in the directory the script is in (easy to do if you use the Open Command Prompt Here shell extension from either Microsoft or
KTechComputing - the latter is recommended if you're running Vista, since the Microsoft one is only for XP, AFAIK).
Copy and paste the following commandline into the prompt and hit enter or return:
- Code: Select all
mencoder "input.avs" -o "output.avi"
If it *still* gives you fits around frames 808-810, then there's something deeper that's wrong (like a bad export from the editing program). The Thread cycling/live lock warning in VDub is usually just an indicator that the script is slow. mencoder simply isn't as prone to that kind of issue, although if something is wrong with the video stream itself it'll still tell you.