[LUNI] recording audio to cd

[Walter]

ide-scsi was either dropped or depreciated from the 2.6 series. Most of
the newer forks of cdrecord will take the device filename as the
argument to "dev=". In other words you can now do "dev=/dev/hdc" instead
of "dev=0,1,1".
On Mon, 2006-12-11 at 19:18 -0600, Richard Lynch wrote:
> On Mon, December 11, 2006 6:59 pm, Mark Stuart Burge wrote:
> > Any suggestions for recording about 30min or more of audio through
> > jack
> > + jamin and then burning the result to cd in a few simple steps ?
> 
> I don't know nothing about jack or jamin, but I do record audio for
> hours on end every night with Linux...
> 
> We pretty much just use "record" which is a command line tool that
> takes the audio straight from the sound card to the hard drive at CD
> quality.
> 
> It's pretty much a no-brainer:
> record -o filename
> 
> You get an ASCII art 2-channel output of what's going to the hard drive.
> 
> You can skip to a new file by hitting "N" so you can turn them into
> tracks on the CD.
> 
> After you quit, you'll have:
> filename000.wav
> filenamn001.wav
> filename002.wav
> .
> .
> .
> with a new file number for each time you hit "N"
> 
> Then just use "cdrecord" to burn the CDs -- or "burncd" I think also
> works fine.
> 
> cdrecord is a bit involved, in that you have to specify the CD drive
> and you have to give it permission to "pad" the audio files out to an
> even multiple of [mumble some silly number] so it can be a RedBook CD:
> 
> cdrecord dev=0,0,0 -pad -eject filename*.wav
> 
> dev will be like 0,0,0 or 0,0,1 or 0,0,2 or... 0,0,7 or 0,1,0 or 0,1,1...
> 
> It's the SCSI system of numbering.
> 
> Ooooh.  And you have to add the Linux ide-scsi thingie.
> /sbin/insmod ide-scsi
> 
> But that's a "do it once and forget it" type of thing.
> 
> Note that the -pad option will add some digital silence to the audio
> files to "pad" them out to make them the even multiple required by
> audio CDs.  I think newer versions of "record" might have a "T" key or
> something where it will force the break to happen at an even multiple,
> so that no padding is needed...
> 
> 
> I believe I have linked to all of these tools and have a bit more info
> here:
> http://uncommonground.com/sound.htm
> 
> > I am currently using ardour, but it involves too many steps to get to
> > the wav file.
> >
> > Tried timemachine (great program, but saves data in an uncommon form
> > of
> > wav or w64 file which seems incompatible with k3b or gnomeburner)
> 
> Is w64 64-bit wav???
> 
> > Audacity is still problematic with Jack (at least on ubuntu it is)
> >
> > Rezound stalls trying to redraw the waveform on large files.
> >
> > Maybe there is a command line option where I can convert from w64 to a
> > raw file and then burn it ?
> 
> sox would almost for sure convert w64 to regular wav.
> 
> sox converts damn near any audio format to whatever you want.
> 
> > Would be great if the burning software could include an option to read
> > from an audio stream !
> 
> This would generally lead to buffering overrun/underrun problems
> somewhere in the chain...
> 
> Maybe on super-high-end hardware with lots of tweaking and a ton of
> research, you can make it work, but I wouldn't recommend you head down
> this path...
> 
> -- 
> Some people have a "gift" link here.
> Know what I want?
> I want you to buy a CD from some starving artist.
> http://cdbaby.com/browse/from/lynch
> Yeah, I get a buck. So?
>