>> >> > Why do you like to create a cue file anyway? >> >> > >> >> > Cdda2wav splits the data at the right location and it icludes the >> >> > paranoia code. >> >> >> >> I read a comparison where somebody ripped a CD with cdrdao and a >> >> couple other tools and then burned the images back to CDs and compared >> >> the CDs, and cdrdao was the only one that ended up with being >> >> indistinguishable from the original as reported by the tool he used. >> > >> > There have been several tests that show up that cdda2wav/cdrecord are >> > the best choice - even compared with Win32 programs. >> >> Can you point me toward any of those? > > 2+ Years ago, there have been several long discussions in > de.comp.hardware.laufwerke.brenner > > One is here > http://groups.google.de/group/de.comp.hardware.laufwerke.brenner/browse_thread/thread/355e88b312c2a2f1/269396c366fe2117?hl=de&lnk=st&q=cdda2wav+eac#269396c366fe2117 > but there have been better ones... > > Try to search for cdda2wav and EAC or ALCOHOL.... in > de.comp.hardware.laufwerke.brenner > > >> >> I want to create a cue file because it's required for converting the >> >> CD image to FLAC with the flac command. I'm actually not interested >> >> in burning CDs, FLAC files only. >> > >> > Mmm I see no reason why there should be a need for a cue sheet just to do a >> > simple compression. >> >> If not the flac command then cuebreakpoints. Is there a way to split >> a FLAC file with a toc file? > > cdda2wav writes a single file per track. Why do you like additional splits?
I like to end up with a raw/toc pair of files to act as a raw backup of the CD, and a series of individual FLAC files for each track. For the individual files, would you do that like this: # cdda2wav -B -Oraw # rm audio.cddb # rm audio.cdindex # rm *.inf # flac --best --endian=big --sign=signed --channels=2 --bps=16 --sample-rate=44100 --verify CD/audio_*.raw How would you generate a raw/toc(inf?) pair for backup? - Grant
