On Mon, Apr 30, 2012 at 5:26 PM, Fons Adriaensen <fons@xxxxxxxxxxxxxx> wrote: > On Mon, Apr 30, 2012 at 05:03:28PM -0400, Paul Davis wrote: >> On Mon, Apr 30, 2012 at 4:54 PM, Fons Adriaensen <fons@xxxxxxxxxxxxxx> wrote: >> >> > But there is one strange thing. There are 75 CD sectors per >> > second (Ardour calls them frames). But in the location dialog, >> > times are shown in a format that divides a second in 30 units >> > (probably time code frames, FPS is set to 30, no drop). >> >> timecode frames. >> >> > Why is that ? If track start and end times must correspond to >> > CD sectors, that means that the times shown in that dialog are >> >> "CD frames (sectors)" are not available as a clock mode at this time. >> >> there is only type of clock object in Ardour's GUI, so the limitations >> of one apply to all (and vice versa). > > But that seems to be a display limitation only. As far as I can see, > computation of the track lenght correctly rounds to multiples of > 1/75 before taking the difference and then displaying it using > timecode frames. So the 'clock object' seems to do its internals > to full precision anyway. That is what makes me wonder why it > doesn't display in the same way. the clock is showing a precise location for a marker. because the marker is noted as a CD marker, it will be rounded to CD frames when appropriate, which currently does not include display time. _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
