[pulseaudio-discuss] [PATCH v5 0/7] New API for Bluetooth A2DP codecs

[Pali Rohár]

On Thursday 31 January 2019 20:09:06 Tanu Kaskinen wrote:
> On Mon, 2019-01-28 at 18:01 +0100, Georg Chini wrote:
> > On 28.01.19 17:50, Tanu Kaskinen wrote:
> > > On Fri, 2019-01-25 at 16:41 +0100, Pali Rohár wrote:
> > > > On Friday 25 January 2019 17:11:00 Tanu Kaskinen wrote:
> > > > > On Fri, 2019-01-25 at 11:02 +0100, Pali Rohár wrote:
> > > > > > With profiles it is simple as it is already supported in desktop
> > > > > > environments.
> > > > > That's certainly a benefit. The problem is just that forcing the user
> > > > > to make a choice between codecs isn't very nice if the user doesn't
> > > > > know the practical difference between the provided options.
> > > > User is not forced. Bluez and remote device choose codec for him. And if
> > > > user is not happy with selection then can change it to something
> > > > different which "plays better".
> > > > 
> > > > We already have module bluetooth policy which switch between HFP and
> > > > A2DP profiles based on active VOIP application. So user already has
> > > > microphone support when calling. And after hanging call policy module
> > > > should switch back to previous A2DP profile (codec) without user
> > > > interaction.
> > > > 
> > > > So I do not think it is such catastrophic that user need to choose
> > > > something. User has already pre-selected some A2DP variant. And based on
> > > > fact that lot of headsets remember last used codec per device, it is not
> > > > such a big problem.
> > > Yeah, it seems that the need to choose the card profile isn't very
> > > common. But there can be situations where the user wants to just
> > > activate the A2DP profile. How do you communicate to the user which
> > > codec is currently active if the card profile is "off"?
> > > 
> > One question: There are codecs which support a voice back channel.
> > Would we not need at least two profiles, one for "normal" A2DP and
> > one for A2DP with back channel?
> 
> Yes, you're right, even if we don't have per-codec profiles, we'll need
> a separate bidirectional A2DP profile when that's implemented (IIRC
> it's not yet implemented by these patches).

It is implemented in this patch series (FastStream codec) and it is
working.

I will send a new version with other fixes, like that profile switching.

-- 
Pali Rohár
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20190131/4f5bf99c/attachment.sig>