[Kdenlive-devel] DV NTSC is only interlaced??

[sean darcy]

On 04/28/2011 12:03 AM, Dan Dennedy wrote:
> On Wed, Apr 27, 2011 at 6:58 PM, sean darcy<seandarcy2 at gmail.com>  wrote:
>> On 04/26/2011 01:04 AM, Dan Dennedy wrote:
>>> On Mon, Apr 25, 2011 at 8:25 PM, sean darcy<seandarcy2 at gmail.com>    wrote:
>>>> I'm starting with a DV avi file, 720x480 30 fps progressive
>>>> (non-interlaced). I want to output it to the same. But when I choose a
>>>> profile in DK-2.0-rc1, the closest is DV NTSC which is _interlaced_.
>>>> (FWIW, I didn't think any dv was interlaced.)
>>>
>>> yes, DV is usually interlaced
>>>
>>>> I can't find any profile that fits. Can I create a custom one somehow?
>>>
>>> You can just set Scanning to progressive when you render or create a
>>> custom project profile based on the DV one.
>>>
>> Hmm. So a dv on a consumer camera tape is interlaced. But if I import it
>> using a forlorn, but not forgotten, program called kino,
>>
>> ffprobe JulyPlay2005-2005.07.24_15-06-27.dv
>> .........
>> Input #0, dv, from 'JulyPlay2005-2005.07.24_15-06-27.dv':
>>    Duration: 00:04:51.55, start: 0.000000, bitrate: 28771 kb/s
>>      Stream #0.0: Video: dvvideo, yuv411p, 720x480, 28771 kb/s, PAR 8:9
>> DAR 4:3, 29.97 tbr, 29.97 tbn, 29.97 tbc
>>      Stream #0.1: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s
>
> where do you see progressive in that output? the p at the end of
> yuv411p stands for planar.
>
29.97 tbr, 29.97 tbn, 29.97 tbc :

I thought this meant 29.97 fields/second and 29.97 frames/second. 
Fields/sec = Frames/sec, therefore progressive.

sean