From: Jean-Yves Avenard <jyavenard@gmail.com>
To: Colin Guthrie <gmane@colin.guthr.ie>
Cc: alsa-devel@alsa-project.org
Subject: Re: HDA: Problem with sound becoming corrupted
Date: Thu, 10 Mar 2011 13:41:00 +1100 [thread overview]
Message-ID: <AANLkTinP1ScPzoUqGbSdWRsUUiVhHSVBKvYkMtUKorq1@mail.gmail.com> (raw)
In-Reply-To: <il858r$kce$1@dough.gmane.org>
Hi
On 10 March 2011 02:10, Colin Guthrie <gmane@colin.guthr.ie> wrote:
> 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.
I have to raise my hand on this one too... It has puzzled me for a few
months now.
I had thought it was related to the new video/audio card I'm using a
GT220 , but this is about the same time I upgraded alsa.
Every once in a while, the audio becomes slightly distorted. Voices
sounds like they are gargling with mouthwash while talking.
Interestingly, it sounds the same for AC3 or DTS passthrough, it's
slightly corrupted, but not enough to break the AC3 stream from being
usable by the amp.
However, closing the PCM device and re-opening it doesn't fix the
issue for me ; I need to reboot.
This is seen with MythTV using ALSA directly (I wrote the audio code in MythTV)
Few MythTV users have reported it, I can't explain what is causing it..
Jean-Yves
next prev parent reply other threads:[~2011-03-10 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 15:10 HDA: Problem with sound becoming corrupted Colin Guthrie
2011-03-10 2:41 ` Jean-Yves Avenard [this message]
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=AANLkTinP1ScPzoUqGbSdWRsUUiVhHSVBKvYkMtUKorq1@mail.gmail.com \
--to=jyavenard@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=gmane@colin.guthr.ie \
/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).