Now that we have a burner at home, I make up compilations whenever I feel like it. It's not normally too difficult, unless you find that your input CDs were recorded at wildly differing volumes. We don't have any sophisticated audio software, and so far we've never needed any. I do audio processing with nothing more user-friendly than command-line sox. However, I'm failing to make any sense out of this part of man sox:
fade [ type ] fade-in-length [ stop-time [ fade-out-length ] ]
Add a fade effect to the beginning, end, or both of the audio data.
For fade-ins, this starts from the first sample and ramps the volume of the audio from 0 to full volume over fade-in-length seconds. Specify 0 seconds if no fade-in is wanted.
For fade-outs, the audio data will be trucated at the stop-time and the volume will be ramped from full volume down to 0 starting at fade-out-length seconds before the stop-time. No fade-out is performed if these options are not specified.
I typed in sox infile.wav oldfile.wav fade 0 200 4, and got a four-second sample out instead of the 200-second sample I'd been expecting. Various fiddling, and I discovered sox infile.wav oldfile.wav fade 0 2000 gives a 52-second file. Clearly, stop-time is not measured in seconds. But what is it measured in?
Update: 21:00. There seems to be a bug in sox version 12.17.1. stop-time should indeed be measured in seconds. Downloading 12.17.3 fixed the problem. Just thought I'd let you know :)