From: Takashi Iwai <tiwai@suse.de>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] Fix buffer position for ATI SB4x0
Date: Fri, 06 Jun 2008 18:49:28 +0200 [thread overview]
Message-ID: <s5hfxrqcxuv.wl%tiwai@suse.de> (raw)
In-Reply-To: <20080606115232.411c13e3@gaivota>
At Fri, 6 Jun 2008 11:52:32 -0300,
Mauro Carvalho Chehab wrote:
>
> On Thu, 29 May 2008 16:20:21 +0200
> Takashi Iwai <tiwai@suse.de> wrote:
>
> > At Thu, 29 May 2008 11:10:22 -0300,
> > Mauro Carvalho Chehab wrote:
> > >
> > > ATI SB4x0 doesn't need any fix at position.
> >
> > It's not about the position fixing but whether to use the
> > position-buffer. The devices on the blacklist are the ones that have
> > no position buffer. So, it would fall into LPIB mode, and this list
> > avoids it from the beginning.
> >
> > > This patch solves the issue of receiving several clicks during capture on those
> > > devices.
> > >
> > > Tested with a Gateway Notebook MX-6453.
> >
> > The click noise is often a different problem. Did you already try
> > the patch below?
>
> The click seems associated to some residual samples inside the buffer. Here it
> is a sample of the king of click noise I'm hearing here (captured from CD input entry):
> http://linuxtv.org/~mchehab/snd.ogg
(I didn't check the ogg file yet, and just a wild guess)
Is it with dsnoop plugin? With "default" PCM, ALSA uses dsnoop for
capture to allow multiplexing for HD-audio. Does it happen with "hw"
or "plughw" PCM?
Takashi
next prev parent reply other threads:[~2008-06-06 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 14:10 [PATCH] Fix buffer position for ATI SB4x0 Mauro Carvalho Chehab
2008-05-29 14:20 ` Takashi Iwai
2008-06-02 14:14 ` Mauro Carvalho Chehab
2008-06-06 14:52 ` Mauro Carvalho Chehab
2008-06-06 16:49 ` Takashi Iwai [this message]
2008-06-06 18:31 ` Mauro Carvalho Chehab
2008-06-07 8:27 ` Takashi Iwai
2008-06-09 13:17 ` Takashi Iwai
2008-06-09 20:29 ` Mauro Carvalho Chehab
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=s5hfxrqcxuv.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=mchehab@infradead.org \
/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