<div class="gmail_quote">On Mon, Oct 3, 2011 at 5:04 AM, Mark Brown <span dir="ltr"><<a href="mailto:broonie@sirena.org.uk">broonie@sirena.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">On Fri, Sep 30, 2011 at 08:23:46PM +0200, David Henningsson wrote:<br> <br> > First, look at the "What's next" section of the 1.0 notes [1]. That<br> > points out what we think are the most important shortcomings of<br> > PulseAudio currently, one of them is "Routing infrastructure": while<br> > it is possible to write your own policy modules today, we're still<br> > lacking a really good solution for handling device priority in<br> > combination with hotplugging in combination with user configurable<br> > overrides.<br> </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"> </div>Yeah, this is why the embedded users I'm aware of chose to do their own<br> thing here (often completely outside of Pulse).</blockquote><div><br></div><div>This is what WebOS is doing. Separate daemon from pulseaudio that controls routing via ALSA UCM, listens to events for hardware changes (jack insertion, bluetooth, etc ...)</div> </div><div><br></div>-- <br>-baeksanchang<br>