Skip to main content

Notice

If you are using a Hotmail or Outlook email address, please change it now, as Microsoft is rejecting all email from our service outright.
Topic: A Bluetooth Sig Member Is Prototyping Opus-Based Bluetooth A2DP Codec (2019) (Read 446 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

A Bluetooth Sig Member Is Prototyping Opus-Based Bluetooth A2DP Codec (2019)

From: https://esp32.com/viewtopic.php?t=11900
Quote from: aaronmhamilton
I've been prototyping a codec mode for A2DP (Bluetooth audio), and I am most of the way toward a working Android-based source implementation; I would like to prototype the sink on my ESP32s. The version of Bluedroid in esp-idf (and by extension, esp-adf) is based on a very old one, and has not even one vendor codec implementation, and predates a lot of cleanup since Google took more control of it (their current version resides at <https://android.googlesource.com/platform/system/bt/>).

Given that I am also implementing the sink side of the codec in the Android version, I'm thinking I could maybe rebase the esp-idf version of bluedroid on the current Google sources, however much work that may be. I'm wondering if such a change is likely to be welcome in the upstream esp-idf.

I'm currently implementing it as a vendor codec, as I am a member of the Bluetooth SIG (company ID 0x0750); but I think they may not be too resistant to making it a core A2DP codec if I make a good case for it (and show a few compatible implementations at a testing event). I think Opus is well-suited to a wide range of A2DP applications(aside from decoder complexity, which may still not be a big deal), so I'm excited to see how it all works out.

I look forward to hearing what y'all have to say about this.

Cheers. :- )

More discussion: https://news.ycombinator.com/item?id=24957872

Re: A Bluetooth Sig Member Is Prototyping Opus-Based Bluetooth A2DP Codec (2019)

Reply #1
More discussion: https://news.ycombinator.com/item?id=24957872

Ha, doesn't seem like there is any more discussion there. In my opinion, this
is very good news. Hopefully headphone makers and phone makers will adopt.
Although, I wonder what the bluetooth situation is like in cars? Do fancy cars
like the Teslas and Ferraris have support for advanced bluetooth codecs? I'm
not sure what codec my car supports and I can't find any information on it
online.

Re: A Bluetooth Sig Member Is Prototyping Opus-Based Bluetooth A2DP Codec (2019)

Reply #2
Ha, doesn't seem like there is any more discussion there. In my opinion, this is very good news. Hopefully headphone makers and phone makers will adopt. Although, I wonder what the bluetooth situation is like in cars? Do fancy cars like the Teslas and Ferraris have support for advanced bluetooth codecs? I'm not sure what codec my car supports and I can't find any information on it online.

It probably possible to find out by enabling developer options on a more recent Android phone or tablet when using a car stereo?  It's not like there isn't an aftermarket for car stereos either.

Re: A Bluetooth Sig Member Is Prototyping Opus-Based Bluetooth A2DP Codec (2019)

Reply #3
Bluetooth SIG already announced LC3 since then. Now we wait when hardware supports it.

 
SimplePortal 1.0.0 RC1 © 2008-2020