> http://gmpc.wikia.com/wiki/MPD_INSTALL_USER_SERVICE_UBUNTU seems to be
> the best way to run mpd on systems with pulseaudio.
My use case is a machine where we usually have 3 users logged in at the
same time (on different virtual terminals), so that's not a good solution.
> Another option is setting up the system wide pulseaudio daemon (and
> it's possible to use mpdris to control/monitor an MPD instance running
> remotely, which still applies even without any hoop-jumping).
The pulseaudio's "why you shouldn't use system wide PA" seems to apply
to my case, so I'd rather not go there either.
> (Yet another possibility which I didn't think of before is setting up
> pulseaudio cookies for the mpd user and any real users that might need
> sound at the same time as mpd)
That's still basically a system-wide setup, then (where you share
a single PA instance between different users).
Basically, from reading PA's documentation, I think the ideal setup for
me would have one PA process per user, and and then combine the result
via some kind of additional layer (ALSA dmix or somesuch, I don't know,
nor would I know how to set up such a thing).
Stefan
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Musicpd-dev-team mailing list
Musicpd-dev-team@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
