From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: HDA: Problem with sound becoming corrupted
Date: Wed, 09 Mar 2011 15:10:18 +0000 [thread overview]
Message-ID: <il858r$kce$1@dough.gmane.org> (raw)
Hi,
I've been dealing with this issue for several months (from memory I'm
pretty sure it's affected me since 2.6.36, possibly before, but I'll
have to do some deeper digging to say for sure).
The problem is that the sound suddenly goes nuts and starts sounding
awful. It's like some buffer pointer is just a little bit out for some
reason.
I can fix the issue by closing and reopening the PCM device (as I use
PA, this is just a simple "pasuspender echo" away).
The problem is very easy to reproduce - it happens about 20+ times a day
to me - to the extent that I have added a panel launcher with the above fix.
We discussed this issue during the meeting but it seems not to be a PA
problem (my other PA devices work fine FWIW - various USB things etc,
and recording from the monitor source when the sound is odd also records
good sounds).
You can hear the sounds here (recorded via mic):
http://colin.guthr.ie/weird-sound/
And our discussion is here:
http://colin.guthr.ie/meetings/pulseaudio-meeting/2011/pulseaudio-meeting.2011-02-24-21.02.log.html#l-409
My alsa-info is here:
http://colin.guthr.ie/alsa-info.txt
This mail is really just about finding out if this is a known problem? I
know others suffer from the same problem too as I've had bug reports
confirming this.
Cheers
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mageia Contributor [http://www.mageia.org/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next reply other threads:[~2011-03-09 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 15:10 Colin Guthrie [this message]
2011-03-10 2:41 ` HDA: Problem with sound becoming corrupted Jean-Yves Avenard
2011-03-10 12:31 ` Colin Guthrie
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='il858r$kce$1@dough.gmane.org' \
--to=gmane@colin.guthr.ie \
--cc=alsa-devel@alsa-project.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;
as well as URLs for NNTP newsgroup(s).