25p on MiniDV tape ?

farss wrote on 5/23/2005, 5:45 AM
Just captured a tape with the trusty DSR-11 and media properties tells me it's Field Order = None (progressive). It also had the AR wrong at 4:3 instead of 16:9 but then that's never that reliable. But how could the thing have ever been recorded as progressive?
Obviously that's wrong, changed it to LFF and Vegas stopped chuging along trying to play it out.

Although, then again, it is a Panasonic tape and they've been know not to like things interlaced. Or was it that the artist who made the program is from the progressive school?
Bob.

Comments

jaegersing wrote on 5/23/2005, 7:19 AM
Hi Bob. On a sort of related subject, I've been having some fun trying to make Procoder recognise my Canon XL2 clips as 25p. Canopus say that DV only supports interlaced formats, so Procoder is correct (however to be fair to Canopus they are trying to help resolve this).

The interesting part though is that if I capture XL2 clips using Vegas, they are always tagged correctly. Interlaced clips are Lower Field first, and 25p clips are None. If DV really doesn't support progressive clips, I wonder how Vegas knows what's what?

Richard Hunter
farss wrote on 5/23/2005, 3:14 PM
Well you cannot write true progressive video to DV tape, it's always recorded as two fields. What those fields contain is another matter of course.
Still Procoder should let you encode a mpeg file as however you like, I'm pretty certain the MC Vegas encoder will let you do whatever you want.
Bob.
jaegersing wrote on 5/23/2005, 5:21 PM
Yes I understand that DV is always interlaced, but there must also be something embedded in the data that lets Vegas detect that it is from a progressive source.

The problem with Procoder is that it does not accept "None" as a valid field order for DV source data, and insists on dealing with "progressive" DV clips as interlaced, which produces interlacing artifacts. If I use a single-line avisynth script to input the clip to Procoder (as a .avs file rather than .avi), the "None" option becomes available and everything is fine. It's quite a simple workaround but I would prefer a proper fix.

Richard