> UCM definitely helps at runtime but in an ideal world we'd still have > the nice pointy clicky tools that provide a beautiful GUI visualising > the system audio setup so people could use those when configuring the > setup for UCM. > >> Or are you talking about going beyond static UCM configurations into >> something more flexible based on the Media Controller API? > > I can see us still needing something dynamic for things like tunneled > audio streams where you're likely to have them being instantiated > dynamically (with associated control), you'd want UCM to be able to work > with this to tell the application about how these should be joined up to > the rest of the system and so on. I don't disagree, but I view tunneling as very difficult to implement when you have something like PulseAudio or AudioFlinger handling all the routing, policy and volume control. The approach based on passthrough makes things simpler in terms of links/routing/policy. Instead of tunneling you push compressed data as far as possible into the sink. The application doesn't need to know what the connections are, this can be handled at the driver/fw level -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
