From: Daniel Mack <daniel@zonque.org>
To: LANGLOIS Olivier PIS -EXT
<olivier.pis.langlois@transport.alstom.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [ISSUE] crackles and clicks
Date: Tue, 14 Jan 2014 17:08:54 +0100 [thread overview]
Message-ID: <52D56116.2060407@zonque.org> (raw)
In-Reply-To: <89F8E4011FD7234ABFE48744E300CBC206BC449B@041-DB3MPN1-093.041d.mgd.msft.net>
On 01/14/2014 04:59 PM, LANGLOIS Olivier PIS -EXT wrote:
> I experience the audible clicks with VLC but I have reproduced it
> with aplay as well. The clicks that I hear corresponds to underruns.
> For the records, this is not happening with a USB device. I have a
> Intel HDA sound card.
Ok, sorry. I missed that detail.
> I did chime in the discussion to point out that
> the problem could come from something else than ALSA or the sound
> card driver. Here is the output of my aplay session. This makes me
> doubt my hypothesis. I'll check the cpu usage while the Wifi is on
> but not connected or see if running aplay in real-time prio makes
> things any better.
I see, and I'd say that's a sign that the wifi driver is holding off the
system way too long somewhere, rather than a problem with the sound driver.
Could you repost your findings from the earlier mail and send them to
Larry.Finger@lwfinger.net and linux-wireless@vger.kernel.org? The
wireless people might have an idea what's going on.
Daniel
next prev parent reply other threads:[~2014-01-14 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 8:34 [ISSUE] crackles and clicks Eric F
2014-01-13 12:11 ` Takashi Iwai
2014-01-13 16:32 ` LANGLOIS Olivier PIS -EXT
2014-01-14 14:42 ` Daniel Mack
2014-01-14 15:59 ` LANGLOIS Olivier PIS -EXT
2014-01-14 16:08 ` Daniel Mack [this message]
2014-01-21 23:59 ` LANGLOIS Olivier PIS -EXT
-- strict thread matches above, loose matches on Subject: below --
2014-01-14 14:59 Eric F
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=52D56116.2060407@zonque.org \
--to=daniel@zonque.org \
--cc=alsa-devel@alsa-project.org \
--cc=olivier.pis.langlois@transport.alstom.com \
/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.