Hi Pasi, On Fri, Dec 28, 2018 at 4:46 PM Pasi Kärkkäinen <pasik@xxxxxx> wrote: > > Hi Luiz, > > On Tue, Dec 18, 2018 at 01:02:39PM -0300, Luiz Augusto von Dentz wrote: > > Hi Pali, > > > > On Sat, Dec 15, 2018 at 5:29 PM Pali Rohár <pali.rohar@xxxxxxxxx> wrote: > > > > > > On Wednesday 11 July 2018 16:45:01 Pali Rohár wrote: > > > > On Wednesday 11 July 2018 16:27:07 Luiz Augusto von Dentz wrote: > > > > > One way to solve all of these is that we would expose the remote > > > > > endpoints using MediaEndpoint1 > > > > > > > > So client application (like pulseadio) would see list of remote > > > > endpoints (one for each codec) and choose one for connection? > > > > > > > > Looks like this should solve this problem. > > > > > > Are there any progress on such API in bluez? > > > > > > On pulseaudio mailing list other people proposed patches for other A2DP > > > codecs and basically bluez API for choosing A2DP codec is still missing > > > part... > > > > Im currenlty on vacation but will try to find time for that, that said > > that shouldn't stop us to include support for other codecs, the last > > set seems to have some sort of priority for ordering the registration > > of the codecs. > > > > Let us know when you have something to see/try! > I'm happy to do testing of the patches. > > People are currently eager to get support for multiple BT audio codecs working and merged upstream :) Note that it is very unlikely that this API would allow multiple codecs at the same time, headsets normally only allow one configuration at time. Making it possible to switch codecs is more of a workaround for headsets that don't honor the codec priority since they normally codec back, although some model no longer configure a stream just wait the source. Regarding the API I still didn't have time to start it, so it will take a little longer than I antecipated. -- Luiz Augusto von Dentz
