Jerry Tan <Jerry.Tan at Sun.COM> wrote:
> Please correct me if I am wrong.
>
> 1. Cdrdao extract hidden Audio Tracks that live in the pregap of track 1.
> It seems that cdrecord has this feature in its todo list,
> but no one request that, it is not a important feature, right?
Cdrecord in it's preferred default interface is based on "one file" == "one
track" and one *.inf file per track. As cdrecord and cdda2wav (in contrary to
all other known software) extract and write audio CDs the way it has been
intended by the creators of the CD, you are able to rearrange the order of
audio tracks by just reordering the files in the argument list without a need
to edit the audio file content or the *.inf file content.
This would cause me to introduce a "track 0" if I like to support data in the
pregap for track 1. This is because content of the pregap for track 'n'
is part of the audio content of track 'n-1'.
Once there is a verification for a real interest at the users side, I will
support it.
> 2. Cdrecord use cue file ,which is much better than toc file, right?
cdrdao implements "toc" files that are similar but not identical to "cue" files.
cdrdao is able to read (or convert) "cue" files (*) but it only implements
limited "cue" file support. Even the "toc" file support seems to be limited.
Every time I tried to copy a CD using cdrdao (because it was not supported by
cdrecord at that time and because cdrdao claimed support for this type of CD)
I failed because the feature did not work in cdrdao also. So I usually
implemented support for that CD type in cdrecord.
*) "cue" files have been introduced by Jeff Arnolds with his program "CDRWin".
They are widely in use by many programs now and if you find a *.dat/*.cue file
pair in the net, there is a 99% probability that they are understood by
cdrecord.
> If these 2 answers are all yes, we have no reason to integrate cdrdao
> into Solaris,
> since cdrecord can do most of work that cdrdao can do.
OK ;-)
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
schilling at fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily