From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-user@lists.sourceforge.net,
ALSA devel <alsa-devel@alsa-project.org>,
Gadi Oron <gadior@gmail.com>
Subject: Re: [alsa-devel] Metallic recording in cs46xx on Thinkpad T22
Date: Wed, 12 Mar 2008 17:39:48 +0100 [thread overview]
Message-ID: <47D80754.1020400@keyaccess.nl> (raw)
In-Reply-To: <s5hk5k89f52.wl%tiwai@suse.de>
On 12-03-08 15:43, Takashi Iwai wrote:
> At Tue, 11 Mar 2008 23:01:39 +0100,
> Rene Herman wrote:
>> On 11-03-08 08:24, Gadi Oron wrote:
>>
>>> I am trying to record sound on an old Thinkpad T22 that uses the cs46xx
>>> sound driver.
>>>
>>> Each time you start to record you have a 10% chance of having the
>>> recording completely distorted and having a metallic sound. When you
>>> look at the waveform it looks as though there are small segments with
>>> sharp transitions between them, a little like if these segments were
>>> moved a little from their correct place.
>> No insights, but I confirm the bug with a TerraTec DMX XFire 1024 (CS4624).
>
> Hm, cs46xx driver hasn't been much changes since long time ago (around
> year 2005). The only big change was about some PM fixes, and I don't
> think it's relevant... Could you run als-info.sh to get the status?
At:
http://pastebin.ca/939784
Script was run just after repeating the problem. I have two of these same
cards (TerraTec DMX XFire 1024) by the way and the same thing happens on
both. If desperately need be, I can also test a CS4630 in the form of a
TerraTec SiXPack 5.1+.
This may indeed have been broken for a long time. I (sometimes) use this
card in a little P1-133 machine in my living room to feed music to my
regular amp and, seldomly, use it to record from for example LP.
Last time that I did was some 2 months ago and I experienced the problem and
at the time I remembered seeing that problem before, which may well have
been 2005. As said, it doesn't happen each time and I use recording on that
card seldomly...
I expect this is going to be difficult to debug. It's no doubt a timing
problem and yes, Gadi's description matches. This is what a bad capture
sounds like:
http://members.home.nl/rene.herman/cs4624-bad-capture.wav
(a good capture is just, well, good)
Didn't report it before since when I'm recording on that thing I'm recording
for someone else and when I'm busy trying to do something _with_ a computer
instead of _to_ a computer, all those pesky little linux problems just get
on my nerves so incredibly bad at times...
Rene.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-12 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3948f0730803110024k1e7b90ecr31b745e333913c1d@mail.gmail.com>
2008-03-11 22:01 ` [Alsa-user] Metallic recording in cs46xx on Thinkpad T22 Rene Herman
2008-03-12 14:43 ` Takashi Iwai
2008-03-12 16:39 ` Rene Herman [this message]
2008-03-12 16:59 ` Takashi Iwai
2008-03-12 17:17 ` [alsa-devel] " Rene Herman
2008-03-13 10:48 ` [Alsa-user] " Takashi Iwai
2008-03-13 12:11 ` [alsa-devel] " Gadi Oron
2008-03-13 12:20 ` [Alsa-user] " Takashi Iwai
2008-03-13 12:56 ` Rene Herman
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=47D80754.1020400@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=gadior@gmail.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.