[Ardour-Dev] Ardour Timecode

[Robin Gareus]

Hi Reuben,

That's interesting. How come quicktime devs managed to screwed that
up..?! Pro-Tools seems to follow their lead. Probably because eventually
quicktime will be used to MUX A/V and in this case twice wrong makes it
right again.

I was afraid that it would turn out this way.

Ardour2 is also using 29.97, recent Ardour3 uses 30000/1001 (and similar
N/1001 for other non-integer framerates).

I believe that ardour should do the /right thing/ and use N/1001,
however that may void interoperability.

The non-plus-ultra would be to have a checkbox in Ardour that allows to
select whether to use fixed-point or rational framerates; OTOH that will
make things even more confusing.  But, telling the OSX crowd: "quicktime
is b0rked, complain at Apple" is not going to solve anything..  I'm
curious what other DAWs (e.g Cubase and Pyramix) or Pro NLEs (The Avid) do.

any options?
robin



On 10/29/2012 10:34 PM, Reuben Martin wrote:
> Anything from Apple (using quicktime at least) usually screws up the framerate 
> for NTSC compatible content. Most of the time you will see stuff like 2997/1000 
> which is wrong. NTSC should always use 1001 for the fame-base. (Those tiny 
> little factional differences add up pretty quickly)
> 
> -Reuben
> 
> On Sunday, October 28, 2012 10:03:18 PM Robin Gareus wrote:
>> Hi all!
>>
>> I'm looking into subframe and fractional framerate rounding issues.
>>
>> Maths be damned, I'm interested in interoperability for the time being.
>> If you have access to a DAW other than Ardour or some pro NLE, please
>> consider to help completing the table at http://gareus.org/wiki/timecode
>>
>> Thanks in advance,
>> robin
>> _______________________________________________
>> ardour-dev mailing list
>> ardour-dev at lists.ardour.org
>> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org