Alsa plugin for pulseaudio

[gcasse@…]

An alsa application such as aplay can fail returning:
aplay: main:545: audio open error: Device or resource busy

because pulseaudio (or another alsa app) is using /dev/snd/pcmC0D0p

A solution would be to install the alsa plugin for pulseaudio [1].

Could you please add these packages?
They already exist in openembedded:
libasound-module-ctl-pulse - 1.0.14-r0 - Alsa plugin for ctl-pulse
libasound-module-pcm-pulse - 1.0.14-r0 - Alsa plugin for pcm-pulse

Note:
once the packages are installed
aplay -Dpulse file.wav
works :-), since /etc/asound.conf already defines a pulse device.

For having this behaviour by default, these lines can be added to
/home/root/.asoundrc

pcm.!default {

type pulse

}
ctl.!default {

type pulse

}

For some reason, it does not work if these lines are added to /etc/asound.conf

[abraxa@…]

I don't quite understand the purpose of this. With these plugins you'd
effectively build an ALSA->PulseAudio?->ALSA chain. To play files from console
it would be more effective to just install pulseaudio-misc and use paplay, no?

-Soeren

[gcasse@…]

Sorry if this comment comes twice (the first one has been sent by mail 11 hours
ago).

aplay is an example, the purpose is to ease the integration of a native Alsa
application.

Gilles

[abraxa@…]

Ahh, okay. Yeah, while not being the most efficient thing to do I guess it's
the only way to make non-PulseAudio?-aware apps behave.

-Soeren

[mickey@…]

Performance-wise I think a better way would be to wrap existing alsa
applications into pasuspend.

[gcasse@…]

The speech server I was aware of, works fine finally using directly an Alsa
output at 48khz (+ an .asoundrc file using dmix). Sorry for the annoyance.
Gilles