Hello alsa maintainers
On 28 August 2016 at 14:40, Javier Serrano Polo wrote:
> There should be a way for an ALSA application not to be intercepted by
> PulseAudio; for instance, by setting an environment variable. One
> example is the ALSA back end of LMMS, where the interception is buggy
> ( https://bugs.debian.org/781479 ). With this patch, setting
> PULSE_ALSA_HOOK_CONF=/dev/null disables the interception.
It seems to me that the proper way to do this is for the pulseaudio
libasound plugin to detect an environment variable, and then
func_load_if_running does nothing in that case.
Alsa maintainers, what do you think? Does it make sense to you? The
code already checks for the PULSE_INTERNAL envvar, but abusing this
variable would be ugly. Adding a similar check for a variable named
like PULSE_DISABLE_ALSA_PLUGIN or something like that should be very