[LAU] CD tracks in Ardour

Fons Adriaensen fons at linuxaudio.org
Mon Apr 30 20:54:19 UTC 2012

On Mon, Apr 30, 2012 at 12:31:20PM -0400, Thomas Vecchione wrote:
> On Mon, Apr 30, 2012 at 8:05 AM, Fons Adriaensen <fons at linuxaudio.org>wrote:
> >
> > As far as I could find out, each track should correspond to a range,
> > and those ranges must not overlap. So should I manually ensure that
> > the start of range N+1 corresponds exactly to the end of range N,
> > or is there a better way to do this ?
> >
> Use the location dialog in Ardour to do this.  Next to the position clocks
> for the start and end markers of every CD range are buttons to jump the
> playhead to that marker, and to use the current position of the playhead
> for the time of that marker.  It makes it nice and easy to line up ranges
> if needed.  I do this quite often in a similar, but not quite identical,
> fashion to what you are doing I believe.

That is exactly what I ended up doing. 

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).
Why is that ? If track start and end times must correspond to
CD sectors, that means that the times shown in that dialog are
not in fact exact. The actual markers probably are, since the
the track lengths as shown are not always equal to the the
difference of start and end. This is to be expected if the 
lenght is computed from start and end rounded to a CD sector
instead of as the difference of the displayed start and end.
But it leaves me wondering why a dialog showing CD track markers
doesn't use 75 units per seconds as its display format.



A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)

More information about the Linux-audio-user mailing list