Topic: Linux users- CD Wave equivalent?

[tim in jersey]

I'm pretty much exclusively on Linux (Ubuntu 10.04).

I've scoured the 'net and haven't had much luck finding a way to port CD Wave via Wine. The *only* Window$ app that I actually miss. Been tracking in Audacity, but it's a pain. I have to track out the 24 bit and 16 bit versions separately.

Loved CD wave for the fact that I could track out either the 16 or 24 bit version, save the cue sheet and simply apply it to the other version.

Does such an animal exist in *nix land?

[flipp]

wavbreaker - version.10 handles 24 bit files, previous versions were limited to 16 bit

http://wavbreaker.sourceforge.net/index.html

[tim in jersey]

Nice! Gonna give it whirl when I get home.

[SmokinJoe]

What I have always done is type the split times into a text file, then "shntool split -f splits.txt -o flac -n xxx2010-10-20d1t blah".  It's seems tedious, but I also type in the song titles at the same time.  From there I have a bunch of homebrew scripts that would take it from there to generate my .txt file and my flac metatags, etc.  In the end it reduces my overall workflow.

[frogger]

Never used CD Wave since I've been in the Linux world for several years but in Audacity just save the labels that you created to make the tracks in the first place.    Do File>Export Labels.  When you reopen the file just do a File>Import>Labels and you're all set to export the tracks.

[rjp]

Note that you can set Audacity to snap to CD-frame boundaries, to eliminate SBEs. This affects both labels and region selection. Sometimes it's necessary to leave Snap-To mode to get your editing right, so you need to be careful to turn it back on when you add labels.

[tim in jersey]

Never used CD Wave since I've been in the Linux world for several years but in Audacity just save the labels that you created to make the tracks in the first place.    Do File>Export Labels.  When you reopen the file just do a File>Import>Labels and you're all set to export the tracks.

I'll give that a whirl, but I was under the impression that the labels don't line up properly when applying labels from 24>16 bit versions of the same source. Am I wrong?

[frogger]

I'll give that a whirl, but I was under the impression that the labels don't line up properly when applying labels from 24>16 bit versions of the same source. Am I wrong?

My masters are all 24-bit/48 and I always work from that.  I'll open the master, import the labels, modify as needed without changing the length, and then extract multiple to the appropriate format (24/48 or 16/44.1).  I haven't noticed any issues with the breaks.  Note that you can also setup audacity to set to cd boundaries as mentioned above.

[tim in jersey]

I'll give that a whirl, but I was under the impression that the labels don't line up properly when applying labels from 24>16 bit versions of the same source. Am I wrong?

My masters are all 24-bit/48 and I always work from that.  I'll open the master, import the labels, modify as needed without changing the length, and then extract multiple to the appropriate format (24/48 or 16/44.1).  I haven't noticed any issues with the breaks.  Note that you can also setup audacity to set to cd boundaries as mentioned above.

Ah, now I see what you mean. I was saving the labels from the 24 bit wav and importing and applying to a big 16 bit version of the untracked show, which definitely caused the tracks to be in the wrong spot. Not sure why I didn't think to extract multiple to 24 *and* 16 bit. Seems so simple, but somehow I overlooked that. Thanks!