| 1 |
Am 18.04.2013 21:48, schrieb Michael Mol: |
| 2 |
> On 04/18/2013 03:32 PM, Alan Mackenzie wrote: |
| 3 |
> |
| 4 |
> [snip] |
| 5 |
> |
| 6 |
>> So, I grasped the nettle, put in a negative pulseaudio use flag, unmerged |
| 7 |
>> pa and alsa-plugins, then rebuilt the 14 packages which needed it. |
| 8 |
>> |
| 9 |
>> Surprisingly, everything still works. I now get those last seconds from |
| 10 |
>> my news streams. :-) |
| 11 |
>> |
| 12 |
>> So, yes, I can recomment the removal of pulseaudio, unless anybody's got |
| 13 |
>> some particular need for it. |
| 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 |
/I can have as many flash instances as I want and still listen to stuff |
| 27 |
being played in vlc. Without pulseaudio crap. |
| 28 |
|
| 29 |
Maybe wine just sucks?/ |
Archives