On 30 September 2014 16:54, Pali Roh?r <pali.rohar at gmail.com> wrote: [snip] >> >> Get them to make a release with media.role set. >> >> This is a small set of applications, a lot of which already >> set this. >> > > Yes, new versions of applications could be released with > media.role set so everything will work. > > But this means that *very* pulseaudio application should set > media.role so we will know that application do *not* want to use > microphone. > > For applications which do not set media.role we know nothing. I've replied to all these in previous mails. >> > What is bad in my solution? >> >> That only VoIP applications should really be using it, and the >> only good way to know an application's voip streams is for >> them to be tagged by the application. >> >> -- Arun > > I disagree. Once I connected my bluetooth headset (which has also > microphone) I want to use only sink/source with my headset. And > not combination of output to bluetooth, input from internal mic > and so... This will only confuse other users who wants to use > bluetooth headset, but PA decide that you do not want to that... We do disagree on this. I don't think Bluetooth headsets should be used as general-purpose capture devices. If a user really wants to do so, there is a mechanism to allow a manual switch. Most users will not be using this and do not need this. I think we've gone through the previous arguments multiple times, and disagree on the last point. Unless someone else wants to chime in with a good reason to support this mechanism, this is a NAK from me. I'll probably write another patch to have the media-role work merged into module-bluetooth-policy at some point, unless someone else wants to take it up sooner. -- Arun
