Hi Tanu, On Mon, Jan 16, 2012 at 8:22 PM, Tanu Kaskinen <ta...@iki.fi> wrote:
> > Do you think it would be a lot of work to move this logic to a separate > module? As discussed before[1], I'd prefer there to be > "module-bluetooth-policy" that would take care of choosing profiles > automatically etc. Autoloading module-loopback could be the first > feature of that module. > Doing a separate module has been the first thing I tried. But there are several reasons which made me try differently : * I needed finer control by being into module-bluetooth-device than hooks : when a sink is being removed it is not possible to remove the sink inputs that were previously affected to it because the sink input has started moving and this triggers an assertion. I had to unload module-loopback before the sink inputs would start moving. * I wanted to avoid having loopback enabled for unwanted modules that could cause uncontrolled side effects. * IIRC Some specific other modules (USB) could benefit of similar behavior. * The code isn't too big. Maybe I'm trying to get complicated in that I'd rather explicitly remove the loopback instead of letting it die. So that's not a big bunch of work to do a module, but I'm open ideas to fix the issues encountered before that. It's an RFC after all ;) Regards, Frédéric
_______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
