From: Takashi Iwai <tiwai@suse.de>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: alsa-user@lists.sourceforge.net,
ALSA devel <alsa-devel@alsa-project.org>,
Gadi Oron <gadior@gmail.com>
Subject: Re: [Alsa-user] Metallic recording in cs46xx on Thinkpad T22
Date: Thu, 13 Mar 2008 11:48:04 +0100 [thread overview]
Message-ID: <s5hwso699y3.wl%tiwai@suse.de> (raw)
In-Reply-To: <47D81037.7030901@keyaccess.nl>
At Wed, 12 Mar 2008 18:17:43 +0100,
Rene Herman wrote:
>
> On 12-03-08 17:59, Takashi Iwai wrote:
>
> > At Wed, 12 Mar 2008 17:39:48 +0100,
> > Rene Herman wrote:
> >> 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
> >
> > The output seems truncated. Could you give the generated file via
> > "alsactl -f somefile store", just to be sure ?
>
> Hmm, alsa-info.sh freshly downloaded from current hg.
Is the original data also truncated at the middle or is it a paste.bin
problem?
> control.26 {
> comment.access 'read write'
> comment.type INTEGER
> comment.count 2
> comment.range '0 - 32767'
> iface MIXER
> name 'ADC Volume'
> value.0 29492
> value.1 29492
> }
Try to put this to full once.
Takashi
next prev parent reply other threads:[~2008-03-13 10:48 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 ` [alsa-devel] " Rene Herman
2008-03-12 16:59 ` [Alsa-user] " Takashi Iwai
2008-03-12 17:17 ` [alsa-devel] " Rene Herman
2008-03-13 10:48 ` Takashi Iwai [this message]
2008-03-13 12:11 ` 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=s5hwso699y3.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=gadior@gmail.com \
--cc=rene.herman@keyaccess.nl \
/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