30 Apr
2012
30 Apr
'12
2:05 p.m.
Hello all,
After reading all the online docs I could find I'm not sure how to
do the following.
I have an Ardour session that will be used to burn an audio CD.
There are three 'songs' in it, but each one should correspond
to more than one CD track. In other words some tracks start
in the middle of the music and there should be no gaps at
those points.
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 ?
Ciao,
--
FA
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)
30 Apr
30 Apr
2:27 p.m.
On Mon, Apr 30, 2012 at 8:05 AM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
Hello all,
After reading all the online docs I could find I'm not sure how to
do the following.
I have an Ardour session that will be used to burn an audio CD.
There are three 'songs' in it, but each one should correspond
to more than one CD track. In other words some tracks start
in the middle of the music and there should be no gaps at
those points.
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 ?
my impression is that if you use a disk-at-once burner (as you need to
to avoid gaps) then the precise placement of markers is less
important. you'll export a single wave file, with a TOC file, give
that to cdrdao or equivalent, and the track markers will simply be
used to provide, ahem, metadata, that a CD player can use. if you
don't do this, and instead use track-at-once burning, the CD standard
mandates gaps between tracks.
3:18 p.m.
On Mon, 30 Apr 2012, Fons Adriaensen wrote:
Hello all,
After reading all the online docs I could find I'm not sure how to
do the following.
I have an Ardour session that will be used to burn an audio CD.
There are three 'songs' in it, but each one should correspond
to more than one CD track. In other words some tracks start
in the middle of the music and there should be no gaps at
those points.
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 ?
Simply assemble the session as you want it to be heard, with gaps where
you want them. Place markers with appropriate names in the 'CD Markers'
line at the points where you want each 'track' to begin, then export the
entire session as a 16-bit, 44.1khz WAV file, and select the option to
produce a TOC or CUE file. When you go to burn the CD, select the TOC or
CUE file in your burner software, and it'll pull in the .WAV
automatically.
--
Rick Green
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-Benjamin Franklin
"As for our common defense, we reject as false the choice between our
safety and our ideals."
-President Barack Obama 20 Jan 2009
6:31 p.m.
On Mon, Apr 30, 2012 at 8:05 AM, Fons Adriaensen <fons(a)linuxaudio.org>wrote;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.
Seablade
10:54 p.m.
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(a)linuxaudio.org>wrote;wrote:
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.
Ciao,
--
FA
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)
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.
11:03 p.m.
On Mon, Apr 30, 2012 at 4:54 PM, Fons Adriaensen <fons(a)linuxaudio.org> 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).
11:26 p.m.
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(a)linuxaudio.org> wrote:
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.
Ciao,
--
FA
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)
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).
11:49 p.m.
On Mon, Apr 30, 2012 at 5:26 PM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
On Mon, Apr 30, 2012 at 05:03:28PM -0400, Paul Davis
wrote:
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.
On Mon, Apr 30, 2012 at 4:54 PM, Fons Adriaensen
<fons(a)linuxaudio.org> wrote:
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. 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).
4399
days inactive
4399
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Fons Adriaensen -
Paul Davis -
Rick Green -
Thomas Vecchione