Re: [Traverso-devel] CDRDAO export

[Nicola Döbelin]

Am 12.05.2007 um 23:56 schrieb ben levitt:

> On 5/12/07, Nicola Döbelin <address@hidden> wrote:
> > > This is super-cool!  And I also look forward to optional on-the- 
> > fly CD
> > > recording that writes the audio data straight to cdrdao, instead of
> > > writing wav files to disk first.  :)
> >
> > Hehe, I doubt this is going to work with cdrdao...
>
> Just a quick note to point out that cdrdao can write audio data to
> disk from cdrdao's stdin if you give an audio filename as    FILE "-"
> 0:00:00 01:00:00
>
> (It also allows you to give a FIFO instead of a file, which could work
> too, but would be less cross-platform.)
>
> I was talking to remon about this...  I think we could pass in
> cdrdao's stdin to the export code, and have it output directly to that
> instead of a file on the hd...  (If you set your burn speed lower, or
> have a burn-free writer, it should be safe enough...

Ah, I didn't know that. Sounds good.

How will the cd writing work on windows? Using cdrdao, too? I'm  
asking because I'm having difficulties compiling cdrdao on OS X.  
However, OS X shippes with a disc recording framework, which is part  
of the system SDK and provides all libs necessary to write CDs. But  
it would require a totally different export function, e.g. each track  
must be a separate wave file, and I don't know if it supports pre- 
gaps at all. (CD-TEXT is supported, thought.) Another option would be  
to use the toc-to-cue program shipped with cdrdao, to convert the  
output into a cue/bin file, which could be written with any  
standalone program.

Now that I think of it, wouldn't it be cleaner to write each track  
into a separate wave file anyway? It would have several advantages:

- once we switch to internal cd writing libs, we will probably need  
it anyway (at least the framework of OS X requires "track objects",  
which can be wave files)
- the wave files can be converted to mp3, written to CD with another  
application, re-imported into traverso etc., which is much more  
convenient if one file = one track.

The naming scheme could be similar to the toc file name, that is  
depending on whether we export the current song or all songs, the  
file names could be "SongName-01.wav" or "ProjectName-01.wav", so as  
to  have consistent names from SongName-01.wav ... SongName-0n.wav or  
ProjectName-01.wav ... ProjectName-0n.wav.

What do you think of that idea (and who volunteers ;-) ? I would, but  
you are much better coders than I am...)

Greetings
Nic