'Twas brillig, and Maystar at web.de at 22/07/11 09:54 did gyre and gimble: > Are there any tutorials explaining the complex solution for this > problem? Perhaps some day I will do this thing nice. Well the "complex" solution I had in mind isn't really possible without hacking code. It kinda ties in with how the accessability stuff will work. I intend to discuss this at the Desktop Summit with some other guys so we know how this is all going to work. Ultimately it revolves round splitting MPD into a player and a consumer. PA will run under an idle session and the idle user will run a MPD consumer (read the data from mpd, and play it out via PA). This means that when the machine is idle, MPD can play audio on it's own. When a user logs in, they idle session will be suspended (as the system now has an "active" user). It will be up to this user to run an mpd-consumer. i.e. it'll be the users choice that they want to hear the MPD audio. Different users may feel differently about it. The same essential architecture is what I envisage for accessability stuff. e.g. you configure the "idle" system to do text-to-speech stuff (so that logins etc. are accessible) but after you log in, it's up the individual users whether they want TTS stuff running or not. That way blind and sighted users could share the same system quite happily without any problems. This is all a little rough at the moment, but hopefully some more solid designs can be worked out at the Desktop Summit. We're having a PA BoF at the Desktop Summit so if you are near Berlin, feel free to pop along. Cheers Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
