[ardour-dev] ardour2 - SMPTE confusion
plutek
plutek at infinity.net
Thu Dec 21 08:24:18 PST 2006
greetings!
before submitting this as a bug, let me just make sure i'm not off base:
[ardour2beta9 rev1232]
29.97non-drop framerate appears to be incorrect:
at a SMPTE position of 00:60:00:00, the clock shows 00:58:03.484.
(it should be 01:00:03.6036)
at a SMPTE position of 00:00:59:00, the clock shows 00:00:57.090.
(it should be 00:00:59.059, which it IS in 29.97drop - just before the
first dropped frame count. so, the framerate appears to be correct in
29.97drop, but not in 29.97non-drop)
also, around the 1-hour point, 29.97non-drop runs to 00:62:00:11 (with
00:59:59.967 showing on the clock) and then jumps to 01:00:00:00 (with
01:00:00.000 also on the clock). i believe 29.97non-drop should just
continue slipping away from real time forever (and should always show
smaller numbers than the real clock, by a factor of 29.97/30).
one other issue is that the timeline graph in 29.97non-drop simply
lines up with the clock timeline (and shows only seconds, no frames),
all the way along - it is neither at the incorrect "29.97" framerate,
nor at the correct 29.97 framerate.
as a side note, i am enjoying ardour2 immensely (on an fc5 ccrma
laptop), and finding that it syncs well to MTC sent from other software
via jack, and also to my old jl cooper pps-1 (which, sadly, only does
30non-drop). my old opcode studio64-xtc, which does 24, 25, 29.97nd,
29.97d, and 30nd is another story; MTC sent from it sometimes puts
ardour into "fits", alternating rapidly between playback and stop, and
sometimes does nothing. so, i'm learning that all sync boxes are not to
be trusted!
if we get a few confirmations here, from people who deal with timecode
more frequently than i do, i'll submit this as a bug. my understanding
of all this comes from reading on the internet, particularly at
http://www.tonmeister.ca/main/textbook/node857.html
best wishes for the holidays!
.pltk.
More information about the Ardour-Dev
mailing list