3 Dec
2002
3 Dec
'02
4:22 p.m.
hello everyone,
i don't know if this is the right forum for my question, but here goes.
i'm running on Intel PIII with kernel 2.4.18, ALSA, and a Hammerfall 9632 card. CD
quality WAV files recorded with ALSA from live performances play back with no problem via
"aplay".
a Yamaha CRW8424S scsi burner was recently installed and i burned the WAV files to CD
with
both "cdrecord" and "cdrdao". data is actually transferred but when i
play the CD's with
a CD player, the tunes are too slow and too low by about a minor third.
i tried burning at various speeds from 1x to 8x, but always the same problem. have also
tried a variety of other options to "cdrecord," like using a really big buffer,
etc. the
commands "file" and "aplay" give the following information:
--------snip-----------
$ file blues1.wav
blues1.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 Hz
$ aplay blues1.wav
Playing WAVE 'blues1.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
--------snip-----------
i wrote to Jorg Schilling who developed "cdrecord", but he only said i need to
use 44100
Hz data and that if ALSA wrote incorrect headers, i should write the ALSA group instead.
i doubt it's a problem with ALSA.
at any rate, i'm out of ideas. has anyone experienced a similar problem? any
pointers
would be greatly appreciated.
tia,
patrick
3 Dec
3 Dec
4:45 p.m.
patrick reardon wrote:
hello everyone,
i don't know if this is the right forum for my question, but here goes.
i'm running on Intel PIII with kernel 2.4.18, ALSA, and a Hammerfall 9632 card. CD
quality WAV files recorded with ALSA from live performances play back with no problem
via
"aplay".
a Yamaha CRW8424S scsi burner was recently installed and i burned the WAV files to CD
with
both "cdrecord" and "cdrdao". data is actually transferred but when
i play the CD's with
a CD player, the tunes are too slow and too low by about a minor third.
i tried burning at various speeds from 1x to 8x, but always the same problem. have also
tried a variety of other options to "cdrecord," like using a really big buffer,
etc. the
commands "file" and "aplay" give the following information:
--------snip-----------
$ file blues1.wav
blues1.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100
Hz
$ aplay blues1.wav
Playing WAVE 'blues1.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
--------snip-----------
i wrote to Jorg Schilling who developed "cdrecord", but he only said i need to
use 44100
Hz data and that if ALSA wrote incorrect headers, i should write the ALSA group instead.
i doubt it's a problem with ALSA.
at any rate, i'm out of ideas. has anyone experienced a similar problem? any
pointers
would be greatly appreciated.
He always says things like that. The truth is that he is usually right
though. He is extreemely well versed in the details of cdburning and
also has a serious bone to pick with the Linux community so doesn't give
extremely positive feedback in regards to Linux.
It *could* be cdrecord and cdrao are not reading the headers correctly
too ;P
What version of alsa are you using? You may need to update to a more
recent version. If that doesn't work you should contact alsa-devel with
a link to the files if possible and let them see. If you want to save
those other files you could try converting them with sox or reading them
in a wave editor then saving over a new version using that app to make
the correct header. Snd is probably the most reliable in that regard but
maybe something like the gnome wave cleaner could do it too.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
4 Dec
4 Dec
12:24 p.m.
The 44100 Hz sample rate is absolutely the only one ever used for CD's,
but high end audio cards like the Hammerfall tend to be more flexible.
So probably a bug or misconfiguration of the audio card or driver is
causing the wavs to be recorded (and played back) at a faster sample
rate. "arecord" thinks it is getting 44100 Hz data, so that's what it
puts in the header, but it is evidently mistaken. "cdrecord" only knows
what is in the header, so it doesn't realize the data is at the wrong
sample rate. Look for a way to tell the Hammerfall what sample rate to
use, either a module option, ALSA config file option, or a
Hammerfall-specific utility program. Sorry to be so vague, but I've
reached (if not passed) the limit of my knowledge.
On Tuesday 03 December 2002 03:17 pm, patrick reardon wrote:
hello everyone,
i don't know if this is the right forum for my question, but here
goes.
i'm running on Intel PIII with kernel 2.4.18, ALSA, and a Hammerfall
9632 card. CD quality WAV files recorded with ALSA from live
performances play back with no problem via "aplay".
a Yamaha CRW8424S scsi burner was recently installed and i burned the
WAV files to CD with both "cdrecord" and "cdrdao". data is actually
transferred but when i play the CD's with a CD player, the tunes are
too slow and too low by about a minor third.
i tried burning at various speeds from 1x to 8x, but always the same
problem. have also tried a variety of other options to "cdrecord,"
like using a really big buffer, etc. the commands "file" and
"aplay"
give the following information:
--------snip-----------
$ file blues1.wav
blues1.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16
bit, stereo 44100 Hz
$ aplay blues1.wav
Playing WAVE 'blues1.wav' : Signed 16 bit Little Endian, Rate 44100
Hz, Stereo --------snip-----------
i wrote to Jorg Schilling who developed "cdrecord", but he only said
i need to use 44100 Hz data and that if ALSA wrote incorrect headers,
i should write the ALSA group instead. i doubt it's a problem with
ALSA.
at any rate, i'm out of ideas. has anyone experienced a similar
problem? any pointers would be greatly appreciated.
tia,
patrick
--
"Can you remember the future? Forget it!"
12:58 p.m.
Hi,
This problem can occur (a bit more in Linux than Windows since Linux
gives us more freedom but requires more study) if you actually recorded your
session at 48K, but are putting it on CD at 44.1K. If the notes are off by
about 1 whole note (a recorded C became a B flat on the CD) then this is
likely what you're hearing.
If your wave files are really 48K (no matter what they say they are) then
look into resampling them down to 44.1K before writing the CD. There is open
source software to do that, but I haven't used any yet.
I've been burned by this problem a couple of times. The most interesting
one was when I was doing a 48K Pro Tools session and sending an ADAT sync to
a GigaStudio box, but using 44.1K libraries. In that case I had to play a
whole note low because the libraries were getting played back too fast.
It happens...
Mark
-----Original Message-----
From: linux-audio-user-admin(a)music.columbia.edu
[mailto:linux-audio-user-admin@music.columbia.edu]On Behalf Of Speaker
to Vegetables
Sent: Wednesday, December 04, 2002 8:20 AM
To: linux-audio-user(a)music.columbia.edu
Subject: Re: [linux-audio-user] Playback slow from burned CD's
The 44100 Hz sample rate is absolutely the only one ever used for CD's,
but high end audio cards like the Hammerfall tend to be more flexible.
So probably a bug or misconfiguration of the audio card or driver is
causing the wavs to be recorded (and played back) at a faster sample
rate. "arecord" thinks it is getting 44100 Hz data, so that's what it
puts in the header, but it is evidently mistaken. "cdrecord" only knows
what is in the header, so it doesn't realize the data is at the wrong
sample rate. Look for a way to tell the Hammerfall what sample rate to
use, either a module option, ALSA config file option, or a
Hammerfall-specific utility program. Sorry to be so vague, but I've
reached (if not passed) the limit of my knowledge.
On Tuesday 03 December 2002 03:17 pm, patrick reardon wrote:
hello everyone,
i don't know if this is the right forum for my question, but here
goes.
i'm running on Intel PIII with kernel 2.4.18, ALSA, and a Hammerfall
9632 card. CD quality WAV files recorded with ALSA from live
performances play back with no problem via "aplay".
a Yamaha CRW8424S scsi burner was recently installed and i burned the
WAV files to CD with both "cdrecord" and "cdrdao". data is actually
transferred but when i play the CD's with a CD player, the tunes are
too slow and too low by about a minor third.
i tried burning at various speeds from 1x to 8x, but always the same
problem. have also tried a variety of other options to "cdrecord,"
like using a really big buffer, etc. the commands "file" and
"aplay"
give the following information:
--------snip-----------
$ file blues1.wav
blues1.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16
bit, stereo 44100 Hz
$ aplay blues1.wav
Playing WAVE 'blues1.wav' : Signed 16 bit Little Endian, Rate 44100
Hz, Stereo --------snip-----------
i wrote to Jorg Schilling who developed "cdrecord", but he only said
i need to use 44100 Hz data and that if ALSA wrote incorrect headers,
i should write the ALSA group instead. i doubt it's a problem with
ALSA.
at any rate, i'm out of ideas. has anyone experienced a similar
problem? any pointers would be greatly appreciated.
tia,
patrick
--
"Can you remember the future? Forget it!"
4:07 p.m.
look into using sox for downsampling -- it has enough configuration
options that you can really fine tune the quality. I've used it for a
ton of projecst -- it's the swiss army knife of audio tools.
Mark Knecht wrote:
Hi,
This problem can occur (a bit more in Linux than Windows since Linux
gives us more freedom but requires more study) if you actually recorded your
session at 48K, but are putting it on CD at 44.1K. If the notes are off by
about 1 whole note (a recorded C became a B flat on the CD) then this is
likely what you're hearing.
If your wave files are really 48K (no matter what they say they are) then
look into resampling them down to 44.1K before writing the CD. There is open
source software to do that, but I haven't used any yet.
I've been burned by this problem a couple of times. The most interesting
one was when I was doing a 48K Pro Tools session and sending an ADAT sync to
a GigaStudio box, but using 44.1K libraries. In that case I had to play a
whole note low because the libraries were getting played back too fast.
It happens...
Mark
-----Original Message-----
From: linux-audio-user-admin(a)music.columbia.edu
[mailto:linux-audio-user-admin@music.columbia.edu]On Behalf Of Speaker
to Vegetables
Sent: Wednesday, December 04, 2002 8:20 AM
To: linux-audio-user(a)music.columbia.edu
Subject: Re: [linux-audio-user] Playback slow from burned CD's
The 44100 Hz sample rate is absolutely the only one ever used for CD's,
but high end audio cards like the Hammerfall tend to be more flexible.
So probably a bug or misconfiguration of the audio card or driver is
causing the wavs to be recorded (and played back) at a faster sample
rate. "arecord" thinks it is getting 44100 Hz data, so that's what it
puts in the header, but it is evidently mistaken. "cdrecord" only knows
what is in the header, so it doesn't realize the data is at the wrong
sample rate. Look for a way to tell the Hammerfall what sample rate to
use, either a module option, ALSA config file option, or a
Hammerfall-specific utility program. Sorry to be so vague, but I've
reached (if not passed) the limit of my knowledge.
On Tuesday 03 December 2002 03:17 pm, patrick reardon wrote:
hello everyone,
i don't know if this is the right forum for my question, but here
goes.
i'm running on Intel PIII with kernel 2.4.18, ALSA, and a Hammerfall
9632 card. CD quality WAV files recorded with ALSA from live
performances play back with no problem via "aplay".
a Yamaha CRW8424S scsi burner was recently installed and i burned the
WAV files to CD with both "cdrecord" and "cdrdao". data is actually
transferred but when i play the CD's with a CD player, the tunes are
too slow and too low by about a minor third.
i tried burning at various speeds from 1x to 8x, but always the same
problem. have also tried a variety of other options to "cdrecord,"
like using a really big buffer, etc. the commands "file" and "aplay"
give the following information:
--------snip-----------
$ file blues1.wav
blues1.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16
bit, stereo 44100 Hz
$ aplay blues1.wav
Playing WAVE 'blues1.wav' : Signed 16 bit Little Endian, Rate 44100
Hz, Stereo --------snip-----------
i wrote to Jorg Schilling who developed "cdrecord", but he only said
i need to use 44100 Hz data and that if ALSA wrote incorrect headers,
i should write the ALSA group instead. i doubt it's a problem with
ALSA.
at any rate, i'm out of ideas. has anyone experienced a similar
problem? any pointers would be greatly appreciated.
tia,
patrick
--
"Can you remember the future? Forget it!"
8078
days inactive
8079
days old
linux-audio-user@lists.linuxaudio.org
4 comments
5 participants
participants (5)
-
Mark Knecht -
Michael L Welles -
patrick reardon -
Patrick Shirkey -
Speaker to Vegetables