21 Oct
2002
21 Oct
'02
1:40 a.m.
Apparently my subscription to the list got dropped. I guess
that's why things have seemed so quiet lately in Linux audio
land.
I just searched the archives on this and the suggestions there
didn't help.
I'm trying to convert some mp3 files into wav files. First I
tried having Audacity export a wav file. Then I tried loading the
mp3 into Broadcast 2000 and having it render it to a wav. Finally
I tried the suggestion in the archives of mpg123 -w filename.wav
filename.mp3.
In each case, when I tried to burn a CD from the resulting wav
file, cdrecord reports "inappropriate audio coding in
[filename]." I'm using Eroaster 2.0.10 as a front end to
cdrecord.
Audacity and Broadcast 2000 both load all these wav files and
play them just fine.
Anybody know what's going on here?
Thanks.
Howard Sanner
flagstad(a)mindspring.com
21 Oct
21 Oct
2:22 a.m.
On Sun, 20 Oct 2002 23:38:46 -0400
Howard Sanner <flagstad(a)mindspring.com> wrote:
In each case, when I tried to burn a CD from the
resulting wav
file, cdrecord reports "inappropriate audio coding in
[filename]." I'm using Eroaster 2.0.10 as a front end to
cdrecord.
What does "file filename.wav" tell you? It should be something like this:
sc-solo4.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM,
16 bit, stereo 44100 Hz
(on one line)
The only thing that I can think of is that perhaps your mp3s are mono.
cdrecord expects to see stero wavs.
Cheers,
- Graham Percival
3:13 a.m.
Graham Percival wrote:
The only thing that I can think of is that perhaps your mp3s are mono.
cdrecord expects to see stero wavs.
Bingo! They are, indeed, mono mp3's. I'll used Broadcast 2000 to
create a 2nd track and see where that gets me.
Thanks a bunch. I'd never have figured that on my own.
Howard Sanner
flagstad(a)mindspring.com
3:35 a.m.
On Mon, 21 Oct 2002 01:11:31 -0400
Howard Sanner <flagstad(a)mindspring.com> wrote:
Graham Percival wrote:
If you're doing a lot of mono mp3 -> cdrom stuff, then you might be interested
in this command I found somewhere amongst the ecasound stuff (maillist or
examples):
ecasound -a:1 -f:16,1,44100 -i mono-1.wav
-a:2 -f:16,1,44100 -i mono-2.wav -erc:1,2 -eac:0,1
-a:1,2 -f:16,2,44100 -o stereo.wav
If you replace both mono-1.wav and mono-2.wav with mono.wav, then it makes
the mono wav into a stero wav with the same thing on each channel. It's
simple to stick that into a script and insert that into the conversion
process:
# mpg123 -$OPTIONSfoo.mp3 foo-mono.wav
# dostero foo-mono.wav foo.wav
# cp foo.wav ~/to-burn/foo.wav
HTH,
- Graham Percival
The only thing that I can think of is that
perhaps your mp3s are mono.
cdrecord expects to see stero wavs.
Bingo! They are, indeed, mono mp3's. I'll used Broadcast 2000 to
create a 2nd track and see where that gets me. 
8:52 a.m.
Hi,
Howard Sanner hat gesagt: // Howard Sanner wrote:
Graham Percival wrote:
Or you could also use the mpg123 option
--stereo
Force stereo output: duplicates mono stream on second output
channel. Useful for output for devices that don't understand mono,
such as some CD players.
I would add: "... and some cdrecording programs like cdrecord"
ciao
--
Frank Barknecht _ ______footils.org__
If you're doing a lot of mono mp3 -> cdrom stuff, then you might be interested
in this command I found somewhere amongst the ecasound stuff (maillist or
examples):
This worked like a champ! Many thanks.
3:24 a.m.
Graham Percival wrote:
What does "file filename.wav" tell you? It should be something like this:
sc-solo4.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM,
16 bit, stereo 44100 Hz
(on one line)
Well, my bright idea of cloning another channel didn't work.
file's output says:
ovt.rendered.wav: RICE image v17990 (42203 x 24576)
which sure doesn't look good to me.
Thanks.
Howard
8063
days inactive
8064
days old
linux-audio-user@lists.linuxaudio.org
6 comments
3 participants
participants (3)
-
Frank Barknecht -
Graham Percival -
Howard Sanner