Page 1 of 1
VS X2 H264 interlaced decoding artifacts!
Posted: Thu Feb 12, 2009 3:23 pm
by Efenstor
Just discovered that you'd better not use VS X2 for editing 60i-encoded 24p video. Look how it looks when fields are separated:
Note that the artifacts look like an
additional interlacing within separated frames! And when it's inverse-telecined it looks like this:
Pinnacle Studio gives no such artifacts.
Patch is needed!!!
P.S.: sorry for the large images.
Posted: Fri Feb 13, 2009 4:01 am
by Ron P.
Please resize your images...
Posted: Fri Feb 13, 2009 11:47 am
by Efenstor
vidoman wrote:Please resize your images...
Done.
Posted: Fri Feb 13, 2009 11:29 pm
by Clevo
Can I ask why you seperated the fields if it's natively in progressive mode?
Posted: Sat Feb 14, 2009 6:46 pm
by Efenstor
Clevo wrote:Can I ask why you seperated the fields if it's natively in progressive mode?
Natively progressive? Not in a way. Canon Vixias shoot in 24p which is encoded in 60i using telecining. That's why I am forced to edit it in 60i and only then convert it into true progressive with AviSynth plugins. Of course I can beforehand convert all the footage to 24p using the same method but it would be wasting too much time.
If you asked why I have separated fields here: it's just to point out what causes the artifacts shown there below. Seemingly it's the ULead H264 Decoder slightly incorrectly decodes interlaced video, and that "slightly" becomes obvious in 24p-inside-60i cases when something fast and colourful is shown, like a fire.
It's like a curse: I have a lot of videos on my HDD since the summer and cannot edit them -- every editor I try has some flaws: the latest Corel has interacing problems, the latest Pinnacle renders only a half of the project, the latest Power Director crashes. As to Sony Vegas it seems fine but I cannot buy it because of my stupid bank that requires CVV code to be specified for every transaction.