From: patrick reardon <swpatrick@earthlink.net>
To: alsa-devel@lists.sourceforge.net
Subject: possible problems with rc6 aplay
Date: Sun, 15 Dec 2002 15:59:54 -0600 [thread overview]
Message-ID: <3DFCFB5A.9B34D27C@earthlink.net> (raw)
hi everyone:
i'm running on a PIII with kernel 2.4.18 and Alsa 0.9.0rc6 and a Hammerfall 9636 card.
Alsa has been working fine for the last year, or so it seems. recently a scsi CD burner
was installed. i have some recordings of live performances made with "arecord", version
0.9.0beta8a. they play back just fine, but when i tried to burn them to CD, they were low
by about 2 to 3 half steps.
Joerg Shilling suggested that Alsa was writing the wrong headers. so i upgraded to rc6
and on the first try on each of the old WAV files, "aplay" also played them too slowly.
however, on subsequent runs, everything was fine again. i don't understand this behaviour
at all.
someone on LAU suggested that since it was too low by about 2-3 half steps, data was being
recorded at 48000 but Alsa thought it was at 44100.
info in /proc/asound/hammerfall/rme9652:
------------snip-------------
.
.
Latency: 4096 samples (2 periods of 16384 bytes)
Hardware pointer (frames): 0
Passthru: no
Clock mode: autosync
Pref. sync source: ADAT1
IEC958 input: Coaxial
IEC958 output: Coaxial only
IEC958 quality: Consumer
IEC958 emphasis: off
IEC958 Dolby: off
IEC958 sample rate: error flag set
ADAT Sample rate: 44100Hz
.
.
---------snip-----------------
for months up until about an hour ago the ADAT sample rate read 48000. in that hour i
changed my .asoundrc from
-----------snip---------------
pcm.hammerfall { #"hammerfall" is the alias for "snd-rme9652" in /etc/modules.conf
type hw
card0
}
ctl.hammerfall {
type hw
card0
}
-----------snip---------------
to the following
-----------snip---------------
pcm.rme9652 { #changed from "hammerfall" to "rme9652" on 12.15.2002
type hw
card 0
}
ctl.rme9652 { #same as above comment
type hw
card 0
}
---------snip-----------------
after the .asoundrc change i recorded a fresh WAV and burned it to CD but with the same
problem -- too slow. also, with the new .asoundrc, version rc6 plays WAV's recorded with
the old .asoundrc and version rc6 a little too fast. i'm at a loss for new ideas to debug
this.
can anyone enlighten me about this, or does anyone know where i can download some
reference WAV files (for example, a middle C tone) to check whether the burning problem
might involve Alsa or whether it's something else in my setup?
any pointers would be greatly appreciated.
tia,
patrick
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
next reply other threads:[~2002-12-15 21:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 21:59 patrick reardon [this message]
2002-12-15 22:15 ` possible problems with rc6 aplay Mark Knecht
2002-12-16 3:13 ` Paul Davis
2002-12-16 4:38 ` Mark Knecht
2002-12-16 10:17 ` Martin Langer
2002-12-16 12:04 ` Mark Knecht
2002-12-16 13:49 ` Paul Davis
2002-12-16 13:57 ` Takashi Iwai
2002-12-16 14:29 ` Paul Davis
2002-12-16 14:53 ` alsasound init script (Re: possible problems with rc6 aplay ) Takashi Iwai
2002-12-16 15:23 ` Paul Davis
2002-12-16 14:36 ` possible problems with rc6 aplay Martin Langer
2002-12-16 14:51 ` Paul Davis
[not found] ` <20021216144807.8950gmx1@mx005-rz3.gmx.net>
2002-12-17 17:54 ` clock mode problem [was: possible problems with rc6 aplay] Martin Langer
[not found] <20021216134609.VYJW9197.sccrgwc02.attbi.com@newmx2.fast.net>
2002-12-16 21:20 ` possible problems with rc6 aplay Mark Knecht
[not found] <200212151910.18nLEb5ck3NZFjX0@robin>
2002-12-16 22:53 ` patrick reardon
2002-12-17 1:44 ` Mark Knecht
2002-12-17 2:48 ` Paul Davis
[not found] <200212161844.18o7IP2Gs3NZFjV0@sparrow.mail.pas.earthlink.net>
2002-12-17 17:08 ` patrick reardon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DFCFB5A.9B34D27C@earthlink.net \
--to=swpatrick@earthlink.net \
--cc=alsa-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox