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 :) Thanks, -- Pasi
