Canopus, MainConcept or Panasonic codec for DV decoding ?

[LordVader]

Anyone?

[mwkurt]

I can recommend the MC DV Codec. There have been folks on the Vegas forums who have done test's using the MC DV codec. They went through 100 generations of a video clip and found that there was virtually no loss in detail at all.
Mark

[LordVader]

Wich version of MC?

what about the chroma bug?

[mwkurt]

I use the 25/50 DV codec version 3.0.16.0. Never heard about a Chroma Bug over on the Vegas forum. So I can't comment. I was just searching and reading some information on the Doom9 forum about this and what I read was that it is only really noticable on big screen TV's and Hi Def stuff. I don't have anything like that so I have never seen anything wrong with the chroma information. Personally, I don't think it's that big of a deal if it even trully exists.
Mark

[LordVader]

Yeah, apparently is really good , i did some tests yesterday, with the 3.0.16, and it seems that it has the chroma bug fixed.

BTW, i did notice that in some cases, interpolation correction is more accurate with some third-party plugins, instead of using a DV codec with the chroma bug fixed already.

But it's a great Great codec i guess.

Also, if you change the fourCC code to "dv50" in your DV files, you can force mainconcept to decode the DV file using the DV50 codec, wich doesn't make any difference at all, but makes you sleep well

[vhelp]

Also, if you change the fourCC code to "dv50" in your DV files,
you can force mainconcept to decode the DV file using the DV50 codec,
wich doesn't make any difference at all, but makes you sleep well

If the information is not there (speaking of dv25, when you change the
code through "hacking" the source file header info) it won't really
matter, and the decode will bump down to the *true* format.. hence,
the dv25 format

From my understanding, the dv50 is a 422 format, and the dv25 is a
411 format. Its safe to say, that the dv50 codec senses this (when you
hack the avi to look like a dv50 by chaning the 4cc to dv50, and the
software responsible to opening up the avi reads in the avi header
info, and determined that it needs to use the dv50 codec) I'm saying
that when, after it determines to use the dv50 codec, that the dv50
codec is now processing the avi, and is seeing that it is not a true
dv50 format avi, and bumps to the the method/subroutine that handles
411 format
.
In your case, I'm guessing that this is what happend in your attempted test.

-vhelp 3377