Detecting ALL DV codecs, and removing them! (Question)

[Colmino]

Subject speaks for itself. The fact: Not all DV codecs are created equal. The problem: Generally speaking, software which uses a DV codec tends to pick whichever one it wants, typically without enabling the user to know which is being used, nor allowing a method for choosing a preferred codec.

The solution? Well, the only one that seems really obvious is to erase those annoying sub-par codecs! Then the software would have little choice indeed.

I'm seeking two things: 1) A method for identifying exactly which DV codecs I have installed on my machine, without necessitating the purchase of special software (ie, if VirtualDub is the only thing that can do this, then fine! But I still don't know how. ;P ) 2) A method for uninstalling whichever codec(s) I don't want to ever see in my DV-manipulating software.

Answering problem #2 may involve more than one method for the various codecs out there. Ideally, I'd like a machine that only has the Sony or Canopus codec, and, most particularly, one which lacks the Microsoft codec. (Using XP.)

[adam]

If you go to Control Panel/System/Harware/Device Manager/Sound, Video, and Game Controllers/Video Codecs/

Double click on that to see the properties then click on the properties tab. All installed codecs should be listed there and you can get further information and settings on them or remove them.

[rcb]

for list, use AviCodec > codecs & filters tab or go in to your Device Manager > video codecs > properties

for removal - outside of M$ add/remove, dunno for sure.

EDIT: better yet, go with Adam's advice

[Colmino]

Thanks. Tried that before, but it seemed like it wasn't providing the whole story. None of the codecs it listed seemed to be for DV decoding. This is in spite of the fact that I can play a DV AVI in Adobe Premiere, and I also installed Vegas Video, which presumably installs the Sony codec as part of the package.

On the other hand, when I go to load the DV AVI into VirtualDub, I get: "Couldn't locate decompressor for format 'dvsd' (unknown). Virtualdub requires a Video For Windows (VFW) compatible codec to decompress video. DirectShow filters, such as those used by Windows Media Player, are not suitable." So VirtualDub isn't finding any codec that it likes, either because it's not there or because VDub is confused.

Anyway, the codecs list in the device manager doesn't seem to work in this case. Any other possible solutions?

[Colmino]

Used AVIcodec to try to get more information. "dvsd" apparently means "Sony Digital Video". Unfortunately, the app does not mention which codec, from among the list it presents (which is a close match for what I get from the device manager), would actually be used to playback the AVI.

[BJ_M]

vegas sony codec is not useable outside vegas (it can be decoded by ms (and other) codec but can not be used by any other app)

premiere pro dv codec = same thing

premiere 6.5 = uses MS dv codec

ms dv codec -- CAN be removed with trouble but not a good idea -- it will not show up in list of installed codecs on most systems ..

[BJ_M]

Used AVIcodec to try to get more information. "dvsd" apparently means "Sony Digital Video". Unfortunately, the app does not mention which codec, from among the list it presents (which is a close match for what I get from the device manager), would actually be used to playback the AVI.

dvsd means DV codec ... thats it ...

you need the main concept or panasonic dv codec to work with virtualdub

[Colmino]

Okay. I was trying to choose between Sony and Canopus, but if the Sony codec will only work from within Vegas, then I must go with Canopus. I briefly checked out Vegas, but its inferface reminded me of the kludgy (to me) SoundForge interface, which I guess is not terrifically surprising. But more to the point, there's a million effects plugins for Premiere and After Effects, and seemingly next to zero for Vegas. Or at least, it's nigh-infinitely easier to find plugins for AA.

Now all I need to know is what good the Canopus codec would do me if I were to install it. It's starting to sound like there's nothing under the sun that would use it.

[adam]

You'll probably be interested in this FAQ. http://forum.doom9.org/showthread.php?s=&threadid=33526

It lists the more popular dv codecs and describes their advantages and disadvantages. I personally use the Canopus codec and "capture" (why do they call it capture?) in Premiere and then frameserve to Procoder. It works for me.

[Colmino]

Anyone know if the Canopus DV codec still has the chroma bug? I'm very familiar with the phenomenon from my history of DVD player headaches. I hadn't known you could fix it losslessly, though. Matter of fact, I'm still not convinced. And to be honest, it'd be too much trouble.

[Colmino]

I personally use the Canopus codec and "capture" (why do they call it capture?) in Premiere and then frameserve to Procoder.

This sounds like precisely what I'll probably do. Assuming the chroma bug is gone, of course. But I do wonder how one chooses the Canopus codec from within Premiere (Pro).

[adam]

Codec stands for compressor/decompressor. When you capture in Premiere it is just a direct copying over of the data as it is stored on the tape, since no compression or decompression has occurred yet. It isn't until you render your footage that the codec is used.

So I capture in Premiere and then use the Canopus plugin to frameserve to Procoder. It uses the Canopus DV codec to do the rendering. If you wanted to export to DV avi using the Canopus codec then you would just do export timeline/movie and set video compressor to "Canopus DV Codec DVBooster Pack" (That's what mine says anyway).

As for the chroma upsampling bug, if it is having any effect on my encodes I can't tell. They look good to me.

[Colmino]

So I capture in Premiere and then use the Canopus plugin to frameserve to Procoder. It uses the Canopus DV codec to do the rendering.

Right, got that. I'm just wondering how you got Premiere to use that plugin to render. From what I have read, Premiere 6.x uses the Microsoft codec and there's no way to change it from within the software, while Premiere Pro uses its own built-in codec which, while superior to the Microsoft codec, is not Canopus. And again, no known way to change it from within the software.

(Adobe's coders are braindead. It's a shame all the nice filters are for their software.)

[BJ_M]

Okay. I was trying to choose between Sony and Canopus, but if the Sony codec will only work from within Vegas, then I must go with Canopus. I briefly checked out Vegas, but its inferface reminded me of the kludgy (to me) SoundForge interface, which I guess is not terrifically surprising. But more to the point, there's a million effects plugins for Premiere and After Effects, and seemingly next to zero for Vegas. Or at least, it's nigh-infinitely easier to find plugins for AA.

Now all I need to know is what good the Canopus codec would do me if I were to install it. It's starting to sound like there's nothing under the sun that would use it.

odd - most people say the reverse .. adobe is kludgy -- but each to thier own ..

there are many plug-ins for vegas - but the point being that vegas has a lot more features built in and doesnt need plug-ins to make it work ..

adobe pro uses trhe main concept dv codec now ..

[BJ_M]

You'll probably be interested in this FAQ. http://forum.doom9.org/showthread.php?s=&threadid=33526

It lists the more popular dv codecs and describes their advantages and disadvantages. I personally use the Canopus codec and "capture" (why do they call it capture?) in Premiere and then frameserve to Procoder. It works for me.

good link -- if you read it to the end they find the initial finding with main concept had changed with the release of the new MC DV codec and it was much better -- and now in fact it has been improved once again .. so has the canopus codec

[andie41]

There is a very useful program called VCSwap http://members.ams.chello.nl/p.bekke/ with which you can quickly see what codecs you have installed and which are active and quickly activate or deactivate. I find it very useful for testing codecs. Sorry if this has already been mentioned - I haven't seen it.