How can I make Xvid codec default?
I'm afraid it's a silly question. And I think it was answered once, but I cannot find the thread.
I opened an avs script in VirtualDub and it said under 'File Information...' that the codec in use is DivX 5.0.5... But I want XviD to be the one to be used for decoding!. I played with XviD decoding options and it says FourCC support for DIVX, DX50 and mp4v. Where can I tell may system to use XviD for decoding?. I remember posts with errors in colors due to DiX decoding, I'd prefer to use XviD. Thankyou |
Deinstalling / reinstalling XVid generally works.
|
Thanx Dialhot.
I thought this also (I should have said that in my first post) and uninstalled previous xvid codec, and reinstalled the latest version, but this didn't the trick (maybe it will work after rebooting the system). Any other hint? |
The "Merit System" that decides what decoder will be used is updated only after a reboot. So rebooting your system is a worthy try.
If it doesn’t work, use ZoomPlayer to increase the XviD merit over the DivX merit. (... and reboot :wink: ) |
Rebooting didn't work. Still when I open an avs file in VirtualDub it says it's opened with DivX.
I downloaded ZoomPlayer Standard (BTW, looks great, even it doesn't yet play my m1v tests). I don't know where look for associations, and how change them... Some help else, please :wink: |
Remove Divx and see if Xvid is used.
Then install Divx and see what happens. I dontt know, I never had such problem :-D |
Quote:
First use advanced options, then go to Filter Control -> Registered Filter Manager. There you will be able to change the merits or even unregister any filter. Btw, be careful there... :wink: |
Thanx muaddib,
I could follow your instructions, and changed merit of DivX (in fact I had 2: one in windows/system32 and a second one don't know where) to 600000, leaving XviD in 800000 "most preferred". After closing ZoomPlayer I saw no change. I'll reboot and post result. You've been very helpful. |
changing directshow filter merit wont help a lot with VDub, it is VFW based.
if youre on Win2K or XP, run regedit go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 youll see a value vidc.yv12 linked to divx.dll (or something like that) right-click on it and select modify, then link to the xvid dll (look at your vidc.XVID for the correct file name) NOTE: all messing up of your registry is for your own account. if you not sure what do with this, ignore this post. (For Win98 i dont know how to fix it) |
Well stephanV, you were right: modifying filter merit didn't change anything. VirtualDub keeps saying it's opening my avs files with DivX.
I followed your fine advice. I don't know if I have a problem here: there's no entry in my registry named vidc.yv12. I have vidc.UYVY, vidc.YUY2, vidc.YVU9, and vidc.YVYU (between some others, like vidc.XVID and vidc.DIVX). Should I generate a new value named vidc.YV12 and link it to xvidvfw.dll (the one linked to vidc.XVID)?. In fact, my problem is not what codec does VirtualDub use to open my avs scripts, but what codec is used by TMPGenc or CCE when they are opening avisynth scripts... I feel I'm getting closer, but I don't know how to know what codec is being used by avisynth to read my d2v files and feed frames to encoders, neither how can I change the codec in case it is not xvid... Still need some help. :roll: |
Just a question on the side : where do you read than Divx has colors problems for handling YV12 ?
|
Hmmm, yes as far as I can remember only ffdshow had some color issues or "upside down" frameserving.
And I'm not quite sure but I think I read that it has been solved. To be honest I never heard DivX had color problems, but I don't know why, I would feel safer knowing that I was using XviD instead ;-) Maybe I'm wrong about this. What do you think about that Phil? I mean, you use some AVI sources once in a while. You would know better than us. Cheers |
Quote:
Concerning MPEG4 sources themselves, opened with an avisource command in the script, I never had any color concerns, whatever the codec. |
Quote:
And I'll have to search the forums to find the answer, but I can asure you that I keep the feeling it was better to have XviD decoding YV12 streams. Don't remember the argument (fastest?, color fidelity?,...) But if it is not necessary, I'll just forget it. I'll keep curious about how to change decoder in my system. |
Quote:
This advice started with release of avisynth2.5. At this time, Divx codec was around 5.0 and didn't decode YV12. So we (I) adviced to install XVid for this purpose, insteed of some codec like aviYV12 that has color problems ! Afterwards, when someone missed a YV12 codec, I adviced to use Xvid, just because this is the one I always advidced. Quote:
:idea: Perhaps VD does not read the file in YV12 but in something else that you have in your registry (maybe with Divx). And if Divx is configured to force the ouput in YV12, then you have the codec that outputs YV12 even if it was called by the system to output an other colorspace. |
Quote:
|
Quote:
Quote:
Quote:
|
I can't remember what was in 5.0.5 but in 5.2.1 this setting is called "Enhanced Yuv mode".
Edit: I just use "codec_sniper" (found on dvdrhelp.org forum) and check that vid.yv12 is decoded on my PC by xvidvfw.dll :!: |
Quote:
Quote:
|
Quote:
|
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.