https://bugzilla.novell.com/show_bug.cgi?id=886058
https://bugzilla.novell.com/show_bug.cgi?id=886058#c10
--- Comment #10 from Takashi Iwai
(In reply to comment #8)
As I mentioned, PA accesses the sound device exclusively.
So? There must be a way to make the mpd connect to other PA
So? Such a thing is a special setup we won't take it as default.
Basically mpd is designed to be exclusive.
Not really. You can configure it to use different audio outputs
Well, I meant "exclusive" as a different meaning. Nevertheless...
If you want to mix the output from mpd with others, it must be configured specially, no matter whether you use PA or not.
False. If you use alsa with dmix (which is now default on distributions using alsa) then you don't need to configure anything to mix it with anything else.
Huh? You wrote that mpd uses hw:0,0 as default. Is it already a false information? (BTW, you don't need to explain about dmix; I'm one of the authors of ALSA core stuff :)
I tried giving appropriate permissions to /var/run/user/<my-uid>/pulse and then symlink the mpd there but it ends up starting new pulseaudio anyway.
I have to get back to this later.
It doesn't work in such a way, unfortunately. Sharing the sounds among different users is usually supported by the "system mode" of PA, i.e. starting it as a daemon. But, it's known that the system mode doesn't cope with some things on desktop usages (and might be buggy in some aspects, as it's been little used). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.