Dear XviD developers, once upon a time (up to June 2003), some XviD codec installers (at least those from Koepi) registered for the FourCCs 'xvid' as well as 'yv12'. XviD dev-4-api or 1.0 RC1 do no longer register for 'yv12'; furthermore, they seem to unregister a previous XviD codec version (probably due to calling its uninstaller). I always thought that VirtualDubMod was able to read YV12 video natively (e.g. I want to use AviSynth 2.5x and encode to XviD using "Fast recompress" mode). Now that XviD 1.0 does no longer register the 'yv12' FourCC, no codec is registered for this FourCC now - and suddenly, VirtualDubMod brings the usual error message "source image format not acceptable (-2)". Obviously, "native YV12 support" was a totally wrong assumption, VirtualDubMod still needs the help of a registered codec (or a color space conversion in the AviSynth script). Therefore, I have a whish for the next XviD installers: Please include a checkbox which allows me to register the XviD codec to handle 'yv12' video if I want. Or tell me why I unfortunately thought that VirtualDubMod would support YV12 natively... ;)
RE: Please allow YV12 registration in future XviD 1.0 installers!
You could also just install the Helix YV12 codec.
--------------------- "It's better to be blown than stroked." 98 supercharged 318ti Sport (track toy) 04 325i Sport Wagon (5spd, her toy) 91 318is (daily fix)
RE: Please allow YV12 registration in future XviD 1.0 installers!
Huh, it doesn't register YU12? I remember I changed the order in which colourspcaes are recommended (YUY2 first [edit: a typo. thanks LigH] ) but didn't remove anything like that. I'll fix it, then... Checkboxes are not a bad idea, I'd like to add DX50 support as well. Radek
--------------------- Things you might like to buy: Lots of Z3 stuff!
RE: Please allow YV12 registration in future XviD 1.0 installers!
actually, the reg key for YV12 didn't change for me... however seeing as the dll files have different names now, the regkey for YV12 saying "xvid.dll" was useless. change it to "xvidvfw.dll" and all is well
RE: Please allow YV12 registration in future XviD 1.0 installers!
Yeah - just found out the same as 'Mug Funky': The changed file naming is the reason that it didn't work any more... But I still wonder why I thought that VDMod would be able to read YV12! __ @ sysKin: Please, be careful when discussing FourCCs, misspelled ones don't make any sense! YUY2 is packed 4:2:2, YV12 is planar 4:2:0.
--------------------- 95 318is POS Bosal exhaust * CAI * Sumitomo HTR Z II * Clears front and side * Aluminum Guage Faces (thx seed) * Illuminated shift knob * ///M3 mirrors * Infinty Kappas front (MTX 302) & rear * 2 JLAudio 12's (MTX 302)
RE: Please allow YV12 registration in future XviD 1.0 installers!
I think I got it! I have to disable the option "Use DirectX for display panes". Then VirtualDubMod is able to both encode YV12 input in Fast Recompress mode, and also display the input while dubbing (okay - as if I would need it...).
RE: Please allow YV12 registration in future XviD 1.0 installers!
The quartz.dll is the default handler for uncompressed video formats, roughly said - installed during the first hour of Windows on your harddisk. __ Which graphic cards do you have on these two computers? I have an ELSA Gladiac GeForce2 GTS - and I guess that it is not able to display YV12 directly. And please look at the VDubMod option about using DirectX panes, too!
RE: Please allow YV12 registration in future XviD 1.0 installers!
i made a few tests but the results are mostly contradicting :( i managed to simulate the problem with vdubmod again by uninstalling xvid. switching off the DirectX Panes in vdubmod 1.5.10.1 didn't help at all (i didn't find a similar option in 1.5.4.1) (i also was unable to play any raw yv12 files (unless configuring ffdshow to do so)) then i experimented with deleting the vidc.yv12 string and installing/uninstalling xvid: at first vdubmod still couldn't proccess yv12 content unless i created a vidc.yv12 string with a value of 'xvidvfw.dll' but after that first time the problem was gone! i didn't have to create a vidc.yv12 string anymore... the moment i installed xvid vdubmod was able to proccess yv12... all the tests were made without restarting, maybe if i uninstall and restart the problem will come up again... anyway i see that the registry value for vidc.yv12 doesn't play such a big role..., can't see why though...???...(that also explains why i could still play yv12 before [regarding my previous post], bsplayer can't play any yv12 if i uninstall xvid (with ffshow disabled)...)