| 1 |
On 04/18/2013 03:32 PM, Alan Mackenzie wrote: |
| 2 |
|
| 3 |
[snip] |
| 4 |
|
| 5 |
> So, I grasped the nettle, put in a negative pulseaudio use flag, unmerged |
| 6 |
> pa and alsa-plugins, then rebuilt the 14 packages which needed it. |
| 7 |
> |
| 8 |
> Surprisingly, everything still works. I now get those last seconds from |
| 9 |
> my news streams. :-) |
| 10 |
> |
| 11 |
> So, yes, I can recomment the removal of pulseaudio, unless anybody's got |
| 12 |
> some particular need for it. |
| 13 |
|
| 14 |
IME, there is one application that all but forces the use of PulseAudio: |
| 15 |
Flash. Once Flash grabs onto an ALSA device, it doesn't let go, so you |
| 16 |
*must* route it through PA if you would like to reliably use it with |
| 17 |
anything else. |
| 18 |
|
| 19 |
My particular discovery was that if I launched WoW under WINE, and then |
| 20 |
launched a browser, audio in WoW worked fine. If I launched the browser |
| 21 |
first (which resulted in a flash applet being loaded in GMail for the |
| 22 |
purpose of audio notifications for google talk), Flash grabbed the ALSA |
| 23 |
device and no WINE application could get at it. Routing both through |
| 24 |
PulseAudio solved the problem. |
| 25 |
|
| 26 |
The other reason I still use PA is X11...I like to use uxterm |
| 27 |
extensively within X, and the only way to get the X11 bell working |
| 28 |
appears to be via PA. So that's what I do. (Googling the history of that |
| 29 |
bit of functionality was infuriating; that was the first time Lennart |
| 30 |
pissed me off. Before someone finally acquiesced and added the |
| 31 |
functionality to PA, he fought it, saying it wasn't PA's job.) |
Archives