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
pulseaudio-discuss mailing list