From: Adam Nielsen <a.nielsen@shikadi.net>
To: alsa-devel@alsa-project.org
Subject: snd-hda-intel+dmix: Disabling power save doesn't work
Date: Mon, 07 May 2012 12:19:37 +1000 [thread overview]
Message-ID: <jo7bfq$oeu$1@dough.gmane.org> (raw)
Hi all,
I'm trying to hunt down a bug in either dmix or the snd-hda-intel module and
I'm hoping someone can give me some pointers.
When I am playing audio and I pause playback, the codec goes into power save
and stops generating a SPDIF signal. My amplifier then displays a 'signal
lost' message. This is quite annoying as it takes a few seconds to sync when
the signal returns (during which time I can't hear the audio being played), so
I set "powersave=0" to disable this behaviour.
This works as expected when stopping playback, but if I only *pause* playback
then the signal drops almost exactly one second later, no matter what
"powersave" is set to. So of course then resuming playback means I lose a
couple of seconds of audio while the amplifier re-syncs to the SPDIF signal.
Setting powersave to other values only affects the time before going into
powersave mode after playback has stopped. It has no effect on whether power
saving is activated while paused.
The problem happens with any audio program (e.g. mplayer and xmms2.) Setting
"powersave=0" means the SPDIF signal keeps going when stopping playback, but
it still drops after one second when pausing playback.
It doesn't happen if I use hw:0,1 as the output device (the SPDIF signal keeps
going, even when paused) but as soon as I change the output device to dmix
then the signal drops whenever the audio is paused.
Is there any way to stop this behaviour and make dmix honour the module setting?
Thanks,
Adam.
next reply other threads:[~2012-05-07 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 2:19 Adam Nielsen [this message]
2012-05-08 5:37 ` snd-hda-intel+dmix: Disabling power save doesn't work Takashi Iwai
2012-05-08 10:19 ` Adam Nielsen
2012-05-08 10:31 ` Takashi Iwai
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='jo7bfq$oeu$1@dough.gmane.org' \
--to=a.nielsen@shikadi.net \
--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 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.