Blue_MiSfit
11th March 2008, 00:18
Hey folks,
So, I've got a tricky one today.
Here's an unprocessed M2V source:
http://www.megaupload.com/?d=TZNRVEUS
Upon first inspection it looks like vanilla 3:2 pulldown. We've got 3 clean progressive frames, followed by two combed frames.
Standard TFM().TDecimate() with either order=1 or order=0 results in a real mess - with every fourth frame showing combing, and something that looks more serious. This pattern is mostly consistent, but not totally. Sometimes I see 2, 3 or even 4 combed frames in a row.
I did SeparateFields() and had a look, and to my surprise some of the individual fields have combing! I've never seen this before.
Ideas on how to fix? Or, is this a lost cause? If so, I can possibly get my hands on a better source.
Thanks!
~MiSfit
So, I've got a tricky one today.
Here's an unprocessed M2V source:
http://www.megaupload.com/?d=TZNRVEUS
Upon first inspection it looks like vanilla 3:2 pulldown. We've got 3 clean progressive frames, followed by two combed frames.
Standard TFM().TDecimate() with either order=1 or order=0 results in a real mess - with every fourth frame showing combing, and something that looks more serious. This pattern is mostly consistent, but not totally. Sometimes I see 2, 3 or even 4 combed frames in a row.
I did SeparateFields() and had a look, and to my surprise some of the individual fields have combing! I've never seen this before.
Ideas on how to fix? Or, is this a lost cause? If so, I can possibly get my hands on a better source.
Thanks!
~MiSfit