Help, codecs not listed in VDubMod.

[WorBry]

For some reason I can no longer see the list of installed vfw codecs under Compression, only Uncompressed RGB. Cant be sure, but I think it happened after attempting to inactivate Cedocida with VCSwap, which threw-up an error message.

I can still see all of the codecs listed in VCSwap, its just that they dont now appear in VDubMod and other editing programs that I have installed with an output compression format option e.g. Ulead Video Studio 11. Tried reinstalling VDubMod but same result.

Unfortunately, a search on the forum hasnt turned up a solution. Would appreciate some help. I'm running Vista by the way.

Cheers.

[clsid]

The registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32" now probably contains something that Windows and those other programs don't like.

[WorBry]

Any idea of how I might go about identifying the culprit?

[unskinnyboy]

WorBry, do you have any registry entries in there in the format VIDC.XXXX, where XXXX would be fourCC values like ffds, i420, mrle etc, with the corresponding driver DLLs listed against them?

[WorBry]

Yes I do:

vidc.cvid
vidc.dvsd
vidc.i420
VIDC.IYUV
vidc.mrle
vidc.msvc
VIDC.UYVY
vidc.XVID
VIDC.YUY2
vidc.yv12
VIDC.YVU9
VIDC.YVYU

Edit: Full Drivers32 listing here:

http://rapidshare.com/files/93861701/Drivers32.jpg.html

[clsid]

List looks ok to me. But you can easily test what entry causes problems.

First export the current contents of the key to a .reg file. That way you can always restore it.
Then just start deleting the values in the key until the problem is gone.
Finally restore the original list. Delete just the entry that you found to be causing problems.

[WorBry]

OK, tried that but still no joy. Evidently, the vfw codecs I can see listed in the registry key and VCSwap are working; I can decode DV with Cedocida and AutoGK works OK encoding to XviD.

Clearly however VCSwap and Vista dont get along. Tried to inactivate Cedocida again but get the same error 'Failed to set data for vidc.mrle'. Likewise with the other codecs.

Tried removing VCSwap, VDubMod and AutoGK and then re-installing VDubMod, but no improvement.

I'm really stumped as to what to try next.

[unskinnyboy]

WorBry, I am not able to replicate your issue. On my Vista machine, I was able to deactivate and reactivate Cedocida v0.2.0 using VCSwap without any issue. When deactivated, VirtualDubMoD didn't list Cedocida in its codec list (as expected), and when reactivated, it came back on VirtualDubMoD's codec list (again, as expected). So this issue is specific to you.

Are you running under an Admin account? Do you have Vista's UAC turned off? If not, can you turn it off, and then retry everything?

[WorBry]

Yes, you're right, disabling UAC allows me to deactivate and reactivate the codecs OK, but still no codecs listed in VDubMod, so I guess that wasnt the cause of the problem.

Just came across this thread from back in 2002 which described a similar problem:

http://forum.doom9.org/showthread.php?p=124480#post124480

I'll give DigitAl's 'BigFix' tool are whirl for what it's worth, although I cant imagine that it does anything more than the registry exercise I've tried already and I couldnt see any empty vidc entries in the key.

Edit: As suspected, BigFix didnt fix it.

[WorBry]

Seems I'm not the only one who has experienced this problem:

http://forum.videohelp.com/topic346156.html#1818153

I'm inclined to suspect its a Video Studio bug.

[WorBry]

Found a fix; check the videohelp link I gave above.

There was an empty 'vidc.uldx' entry in a replicate HKCU...Drivers32 key, which I deleted. The vfw codecs are now visible in VirtualDubMod.

Whoopee

[squid_80]

What was the full replicate key?

[clsid]

After some testing it seems to be
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Drivers32

[squid_80]

Ah. So vfw32 loads codecs from HKCU as well as HKLM? That's slightly disconcerting. I'll have to do some testing...

[WorBry]

After some testing it seems to be
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Drivers32

Yes, exactly that. One assumes the empty 'vidc.uldx' entry originated from Video Studio 11 Plus (i.e. ul = Ulead)

Edit: Apparently, Ulead (Corel) decided to drop support for vfw codecs in their VS10 Vista update pack, and presumably VS11+ also, because "vfw is not supported in Vista" (no I dont understand that either):

http://phpbb.ulead.com.tw/EN/viewtopic.php?t=29380

Evidently, the empty entry is their little legacy spanner in the works, as deleting it also brings the installed vfw codec listing back up in VS11+