On Fri, 17 Sep 2004 10:46, Volker Kuhlmann wrote: > > The output from wav2cdr in the sample below gave a file "span1.01". > > > > [EMAIL PROTECTED] wav2cdr --monostereo --tocdr processed1.wav span1 > > The output file span1.01 is then in CDR format, which you can directly > burn with cdrecord. > > > K3b can't recognise this file type > > It's probably been idiot-proofed by way of dumbing it down to an > extent where it's no longer a usable tool for those who know what they > want to do. > > I had a row with the nero-people once because their burner point-blank > refused to burn an ext2 filesystem image to DVD with the "burn image to > disk" function... and the Mickey-head in the lab told me "have you > heard of joliet? that's what you should be using, it does everything > one would want to do"... ROTFL. Different issue, but similar nature. > > Unfortunately KDE has almost 100% copied Redmond and only detects file > types by extensions. In the case of the audio-CD format there are no > headers or other identifiable parts in the file, and no universally > recognised 3-letter acronym commonly used as extension. Therefore > /usr/bin/grep is a valid CDR file (it'll sound terrific!). That's why I > think there's a good chance k3b isn't able to burn CDR files (or it > expects an extension which you haven't yet tried), to prevent the > clueless from listening to grep. Please file a bug report / ehancement > with k3b :) > > As Rex pointed out, these days cdrecord can burn .wav files directly, > though it's always looked very silly to me to rip CDs to .wav (swapping > all the bytes), then burning the .wav to CD (swapping all the bytes > again). But then I was on a 486 when I made wav2cdr... > > Volker
Volker thanks for taking the time to reply, that makes it things a lot clearer -- cheers................dave G Mail to: "[EMAIL PROTECTED]" ____________________________________________ KMail 1.6.2 & Kontact - KDE Desktop 3.2.3 SimplyMEPIS Linux - Kernel 2.6.7 (i686) ____________________________________________
