On Sat, Mar 15, 2014 at 19:07:15 +0100, Max Kellermann wrote: > That's not a valid argument. If the user tells MPD to use a specific > sink and then removes that sink, then MPD can't possibly fulfill the > user's wish. That's a user error, and we don't need a programmatic > solution for that. > > But if the user tells MPD to use a specific sink, and the next day > finds that MPD wants to connect to a very different sink that doesn't > exist anymore, different from the one he configured in mpd, he will be > disappointed and wondering what the hell MPD is doing. > > This whole idea leaves me with a bad taste.
What about users with bluetooth headsets? They'd move all streams to it while they're using it then when they disconnect it, the sink disappears. Presumably, if an application is restarted while it is in use, having to move the stream shouldn't be necessary (otherwise things like notification sounds would always go to the wrong sink). Is there a way to tell MPD to just have the pulseaudio server DTRT rather than using explicit sink names? --Ben _______________________________________________ mpd-devel mailing list [email protected] http://mailman.blarg.de/listinfo/mpd-devel
