Red Hat Bugzilla – Bug 283371
Make pulseaudio aware of ALSA mixing by default
Last modified: 2007-11-30 17:12:15 EST
Description of problem:
If another program is using the ALSA interface, and something tries to emit a
sound via the pulseaudio 'esd' drop-in, it throws messages like this:
E: module-alsa-sink.c: Error opening PCM device hw:0: Device or resource busy
Eventually, something overflows, and we start seeing this instead:
W: sink-input.c: Failed to create sink input: too many inputs per sink.
Version-Release number of selected component (if applicable):
Launch an xmms that's using the ALSA output plugin, and then try to output sound
Steps to Reproduce:
This worked just fine under esound, so it's a pretty big regression.
PulseAudio is not intended to be run through dmix. If alsa-plugins-pulse is
installed ALSA output goes through PA properly which is the way it should be. On
new installations this package is installed by default. I am not sure how we
could make sure that this package is installed on upgrades too.
Umm, stick a 'Requires: alsa-plugins-pulse' in the .spec?
Boo, hiss. That won't be sufficient, I just found/read
xmms's libALSA.so, if pointed at 'pulse' as the device, throws *lots* of
underruns (we're talking several a second). It makes it *totally* unlistenable.
That's even *with* 'chrt -r 5 /usr/bin/pulseaudio'.
Oh, and having to start *every* program with 'pulse' as recommended in
README-pulse is a Bad Idea - you miss one program and *everything* using Pulse
wedges up and produces no sound.
This is not ready for prime time, by a long shot.
Is this what broke nearly all my sound about two weeks ago??? (All except
tvtime for some reason) See: BZ#281711
I agree with the previous comment. Anything that causes a regression like this
is not ready for prime time.
More recent versions of the ALSA plugin install themselves as "default" in ALSA now.
The ALSA plugin in 1.0.14-3 should improve compatibility with the apps currently
getting underruns when using it.