30 Apr
2004
30 Apr
'04
9:26 a.m.
Hi,
On the topic of burning a CD, is it possible to define
the start and stop points for many songs within one
large file?
I always use cdrdao and produce distinct files for
each song. However, when mastering muliple songs with
Ardour and JAMin a significant amount of time can be
saved if the final audio product could be one file.
ron
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
30 Apr
30 Apr
10:03 a.m.
On the topic of burning a CD, is it possible to
define
the start and stop points for many songs within one
large file?
Sure, and you can easily see this looking at the output of
cdrdao read-toc
$ cdrdao read-toc --fast-toc --device 0,0,0 /tmp/foo.toc
(0,0,0 is my cdrom device, with ide-scsi emulation)
this contains stuff like:
// Track 5
TRACK AUDIO
NO COPY
NO PRE_EMPHASIS
TWO_CHANNEL_AUDIO
FILE "data.wav" 14:42:15 03:06:20
// Track 6
TRACK AUDIO
NO COPY
NO PRE_EMPHASIS
TWO_CHANNEL_AUDIO
FILE "data.wav" 17:48:35 03:03:58
As you can see, it uses one large data.wav file, and starting points
in that file + length for each track (and in this case, with no silence
in between).
10:28 a.m.
On Fri, Apr 30, 2004 at 06:18:56AM -0700, R Parker wrote:
On the topic of burning a CD, is it possible to
define
the start and stop points for many songs within one
large file?
The cdrdao manual says this right at the end of the TOC FILE section:
INDEX MM:SS:FF
Increments the index number at given position
within the track. The first statement will incre
ment from 1 to 2. The position is relative to the
real track start, not counting an existing pre-gap.
I haven't tried this, but it looks like what you want.
I don't know whether incrementing the index number is sufficient to be
seen as a track mark when skipping tracks in a player, or whether that
needs some other kind of marker inserted in the data.
--
Anahata
anahata(a)treewind.co.uk -+- http://www.treewind.co.uk
Home: 01638 720444 Mob: 07976 263827
7:16 p.m.
INDEX MM:SS:FF
Increments the index number at given position
within the track. The first statement will incre
ment from 1 to 2. The position is relative to the
real track start, not counting an existing pre-gap.
I haven't tried this, but it looks like what you want.
I don't know whether incrementing the index number is sufficient to be
seen as a track mark when skipping tracks in a player, or whether that
needs some other kind of marker inserted in the data.
No, I suspect he wanted to create TRACK boundaries. Not all consumer
cd-players actually let you select INDEX numbers. In any event, seeking to
INDEX numbers is never as fast as skipping tracks since determining the
INDEX number requires tasting the subcode [actually reading one frame of
data] as it skips forward/backwards. Seeking to another track is a known
quantity because of the TOC information. There is a formula that can be
used to determine how many mm out from the origin of the CD (also defined in
a standard) given MSF values. With INDEX values, there is no such shortcut
possible.
When about to destroy the Ring of Power, you cannot ignore Quality,
=MB=
--
A focus on Quality.
1 May
1 May
3:08 p.m.
On Fri, Apr 30, 2004 at 04:08:48PM -0700, Malcolm Baldridge wrote:
No, I suspect he wanted to create TRACK boundaries.
Not all consumer
cd-players actually let you select INDEX numbers.
Ooops - My bad - I'd forgotton that index numbers were a separate thing
altogether.
--
Anahata
anahata(a)treewind.co.uk -+- http://www.treewind.co.uk
Home: 01638 720444 Mob: 07976 263827
7306
days inactive
7307
days old
linux-audio-user@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Anahata -
Maarten de Boer -
Malcolm Baldridge -
R Parker