Quote:
I'm sorry this thread it's growing too much for a matter that I'm afraid it is not of general interest, but I cannot sort this out on my own. With your help I'm understanding (or not) better what happens (or doesn't) in my system. But still need some help else... |
Quote:
Look at how are the entry vidc.YUY2 for instance, and create a new one for vidc.YV12 that point to "xvidvfw.dll" Note: I wonder if, when you install XVID, the vfw module is optional or not. Did you check it at the intallation of xvid codec (koepie's release) ? |
Related to your first suggestion: I already had thought to do that, but as my system has not complaint til now of a YV12 decoder missing, I thought it would be useless, as it seems it doesn't need an entry for vidc.YV12. But I may try and see what happens: if doesn't work, just erase the registry entry.
Related to your note: I "re-installed" (aborted when asked if ready for instal) XviD, and there's no VFW option: it seems it's installed by default... But... Playing with XviD "Configure Decoder" I saw a combobox named Output Colourspace, I had "No force" selected, and I changed to "YV12"... I don't know if this will help. I'll see, if not, I'll try to add a new entry in registry. I'll post my results. Thanx |
I suggest you try the Helix YV12 codec as the decoder.
http://forum.doom9.org/showthread.ph...ght=helix+yv12 Both XviD and DivX have sometimes problems when you crop the image - even if it's cropped by the rules, Helix has worked well. You only need to install the package, it then decodes YV12 by default. |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.