On Mon, Oct 3, 2011 at 5:04 AM, Mark Brown <broo...@sirena.org.uk> wrote:
> On Fri, Sep 30, 2011 at 08:23:46PM +0200, David Henningsson wrote: > > > First, look at the "What's next" section of the 1.0 notes [1]. That > > points out what we think are the most important shortcomings of > > PulseAudio currently, one of them is "Routing infrastructure": while > > it is possible to write your own policy modules today, we're still > > lacking a really good solution for handling device priority in > > combination with hotplugging in combination with user configurable > > overrides. > > Yeah, this is why the embedded users I'm aware of chose to do their own > thing here (often completely outside of Pulse). 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 ...) -- -baeksanchang
_______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
