On Sunday 22 July 2018 10:45:57 Pali Rohár wrote: > On Friday 20 July 2018 14:30:56 Luiz Augusto von Dentz wrote: > > Hi Pali, > > > > On Wed, Jul 11, 2018 at 11:07 AM, Pali Rohár <pali.rohar at gmail.com> wrote: > > > On Monday 09 July 2018 17:56:16 Pali Rohár wrote: > > >> On Monday 09 July 2018 18:48:10 Luiz Augusto von Dentz wrote: > > >> > > 2) How should codec switching from pulseaudio API and pactl/pavucontrol > > >> > > looks like? > > >> > > > >> > Usually we don't force reconfiguration but perhaps we should, note > > >> > though that we may end up with audio glitches since we have to > > >> > disconnect A2DP stream to be able to reconfigure it with another > > >> > codec. > > >> > > >> Glitches are already there if you switch from A2DP profile to HSP in > > >> pavucontrol. So I do not see any problem if glitches happen also when > > >> switching between A2DP (SBC) and A2DP (aptX). > > >> > > >> > We would probably have to expose each endpoint so you could > > >> > peek and choose what the codec to use. > > >> > > >> Yes. I think this is required when pulseaudio is going to support more > > >> then one codec. > > > > > > So when this will happen? As for now this is blocker for proper support > > > of multiple codecs in pulseaudio. > > > > > > We need some dbus method call which will tell bluez which endpoint > > > (registered by pulseaudio) should be used now for particular bluetooth > > > A2DP device. > > > > I can give you some pointers on how to expose the endpoints with > > MediaEndpoint interface. > > Ok. Until that, I sent a new version of aptX patch which let codec selection to bluez. -- 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/20180728/abe0dbfd/attachment.sig>
