14 May
2016
14 May
'16
12:59 a.m.
On Fri, 13 May 2016 23:01:19 +0000, Ian Stewart wrote:
In inserting PulseAudio, then your applications have to be aware that PulseAudio has been inserted, and so they need to be told not to try sending their audio to ALSA but to send it to PulseAudio. (...Or maybe they do still go to ALSA and ALSA turns it around and sends it to PulseAudio which then sends it back to ALSA?)
I believe that PulseAudio is transparent to applications written to work with ALSA. Basically, PulseAudio redirects all calls to the ALSA client library to itself, which then makes the calls to the “real” ALSA...