Hello!
I wanted to ask if Oticon opn s supports the LC3 codec? I’ve heard that Oticon intent supports this for sure. Does it turn out that the Oticon intent reproduces streaming audio much better and better than the oticon opn s?
And I still can’t find information about which codec the Oticon opn s uses, because the manufacturer just keeps silent about it and says that they support the Dolby Audio format.
No to the OPNS aids. I have the INTENT1 aids and they do use le audio and the connectivity and streaming is great with my Samsung S23 phone.
Yeah they’re to old to support anything of substance,as mentioned LE Audio is the way forward.
-
OPN / OPN S / Xceed → Apple only, Mfi = made for iPhone/iPad
-
More / Real → Mfi + ASHA
-
Intent → Mfi +ASHA + BLE-Audio
BLE-Audio uses the LC3 code
Mfi & ASHA uses ? unknown codecs
1 Like
The default codec for bluetooth is SBC , which is the best you’ll get out of HAs that don’t support LEA, which uses LC3.
3 Likes
Hearing Aids connecting through ASHA use G.722 codec (Hearing aid audio support using Bluetooth LE | Android Open Source Project), while devices (like Phonak or Oticon Connect Clip) using classic bluetooth use SBC. Not sure about MFI though, something proprietary probably.
2 Likes
From the Apple support site “AirPods, AirPods Pro, AirPods Max, and Beats wireless headphones use Apple AAC Bluetooth Codec to ensure excellent audio quality.” So if using Airpods Pro 2 with hearing assistance enabled I assume it will use AAC from an iPhone.
They also say “AirPods 4, AirPods 4 with Active Noise Cancellation**,** and AirPods Pro 2 with USB-C Charging Case provide Lossless Audio with ultra-low latency when paired with an Apple Vision Pro.”
So I assume the Airpods Pro 2’s (with USB Type C charging case - which is what I have) can do lossless over an LE Codec - but not with an iPhone just with the Apple Vision Pro,
Hey Bruno, thanks for that. I always just checked my pixel phone ,but was actually using the ConnectClip, so I got SBC in Developer Options. When I use ASHA the codec setting in Developer Options is greyed out, so I thought it was default.