Comments

You must log in or register to comment.

voyagerfan5761 t1_jcmm05x wrote

Drop the license fee for receiving devices too, you greedy kings.

31

lightrush t1_jco0q2r wrote

Qualcomm? Never.

12

smalg2 t1_jco9geg wrote

Exactly. To be honest I suspect they only made their encoders free to use on Android because they figured it would increase their market penetration (more aptX support on Android means more aptX-compatible headsets sold) which in turn would allow them to make even more money on decoder licensing fees (for headsets) than they would have otherwise (since fees have a "per-device" component). This move isn't for the greater good, it's for money, which truth be told they make a pretty good job at extracting from a technology that dates back to the 1980s.

Which is a shame because SBC is objectively a better codec than aptX. I'm not even kidding. Ever heard of SBC XQ? It's a higher-bitrate version of SBC (same codec, better settings) just like aptX HD is simply aptX with a higher bitrate. Funny thing is, the Bluetooth specification only suggests encoder settings up to 328kbps for SBC, so until recently no encoder ever bothered to go higher. But it turns out most headsets can decode SBC up to 730kbps. The people who discovered this came up with higher-bitrate encoder profiles, and named them SBC XQ.

And not only is SBC supported by every Bluetooth headset ever made because this is mandated by the Bluetooth specification (and aptX isn't), but unlike aptX, SBC uses psychoacoustic modeling, which gives it a better perceived sound quality than aptX for the same bitrate. The result is SBC XQ can beat aptX HD in terms of sound quality while using a comparable bitrate, and works with almost every headset in existence, even older ones. Universal support, better quality/efficiency, and no additional fees required: aptX has literally no reason to exist other than filling Qualcomm's pockets. SBC XQ has already been implemented on Linux (via Pipewire) and LineageOS-based Android ROMs, let's hope it will come to mainstream Android (AOSP) soon.

21

Wolverineghost1234 t1_jcoqngp wrote

Why so negative about aptx ? Do you think Sony, Sennheiser will sell lots of their devices without? What di they tell their customers then? AAC for instance is better than Aptx?

1

Shirubax t1_jcp54i6 wrote

Last I checked Sony didn't support aptx, at the very least they are pushing their own codec.

5

Wolverineghost1234 t1_jcp5q7l wrote

That's right. But take other brands they all have Aptx, aptx hd or LL. If it isn't about the codecs but more on hardware why dare lots of brands not to choose for AAC. They say AAC is not reliable on android..they say but is it true?.

1

Shirubax t1_jcpph0m wrote

I don't think it's true, at least not on my xperia phone. You can lock the codec in the developer settings to force a certain one, and I've tried aac before without issues.

2

S0_B00sted t1_jcu1m9x wrote

LDAC is a superior codec anyway. aptX can't even recreate a sine wave without garbling it.

1

smalg2 t1_jcr68oa wrote

> Do you think Sony, Sennheiser will sell lots of their devices without?

Probably not, and I suspect that was kind of the point. We could simply have increased SBC's bitrate and enjoyed high quality music with our existing SBC gear, the end. But instead, a company saw the money-making potential of this situation, bought the rights to an audio codec designed in the 80s, and pushed for it to be used with Bluetooth by marketing it as "HD audio" (which it wasn't really, at least for the original non-HD aptX). Headset makers got to sell more headsets ("Oh you want to use this fancy new codec? A shame it doesn't work with your current headset, you'll need to buy a new one. Too bad!" - sad Pikachu face) creating more electronic waste in the process, Qualcomm got to collect licensing fees from millions of encoders and decoders around the world, and consumers obviously got to pay for all this (who else?) Other companies saw this and joined the game with their own codecs, and the Bluetooth audio landscape is now this huge mess we all know, with a plethora of codecs competing against each other, and an endless list of platform-specific incompatibilities and limitations. All this when the solution was right there from the start: SBC...

I'm not saying SBC doesn't have room for improvement, especially regarding latency, but it was designed to be capable of much more than what we ended up using it for. It was supposed to support adaptive bitrate for example, but AFAIK this was never implemented correctly.

So yes my opinion of aptX is pretty negative, because IMO this is a typical case of consumers getting abused to make corporations even more money, when there were some much more elegant (but less lucrative) solutions available. Bluetooth audio could have been so much better... Oh well, rant over.

3

giant3 t1_jcu623p wrote

> negative about aptx

It is based on truth. This AptX vs Others test shows that standard AptX and SBC @ 328 kbps have only a 0.6 dB difference in distortion. AptX HD is better, but it is using 529 kbps. SBC or SBC XQ at that bit rate would perform similarly.

> AAC for instance is better than Aptx?

Absolutely. Any day of the week. The only codec that can beat AAC is Opus. There is extensive scientific literature on audio codecs. People have spent their entire career on audio codecs and their day job is evaluating the codecs both subjectively and objectively.

AAC & Opus are superior to every other lossy codec out there.

2

Wolverineghost1234 t1_jcucp4g wrote

Thank you very much for you're reaction. I think I'm going the choose for the Jabra Elite 7 pro..

1

giant3 t1_jcurfcn wrote

> Jabra Elite 7 pro

They are not worth the money as their ANC is garbage though their sound quality is on target.

1

Wolverineghost1234 t1_jcuw6zs wrote

I already ordered. Sound is More important to me the ANC. Thanks for your reply.😊👍👍

1

vext01 t1_jclz12e wrote

About time!

15

Happy_Phantom t1_jcm84cq wrote

So a digital audio player or source doesn't need a license to transmit, but the receiver (headphone or TWS IEM) still has to license it?

13

smalg2 t1_jcmh9of wrote

Not exactly, this change only concerns Android:

> In a statement to Rahman, Qualcomm confirmed Android OEMs don’t need to pay the company for licensing to access aptX and aptX HD encoders. They are now a part of the AOSP Apache license, and free to use. [...] This means any developer creating a custom Android-based ROM can now add support for Qualcomm aptX or aptX HD without ripping them from a licensed build.

But also:

> "As per our usual business processes, the licensing of aptX [will remain] unchanged apart from contributing the aptX and aptX HD encoders to AOSP."

So licensing fees are still required to use Qualcomm's aptX and aptX HD encoders outside of Android.

15

Happy_Phantom t1_jcn467t wrote

That's too bad, then, for lower-priced DAPs that feature HiByOS, Mango OS, or mTouch.

8

blorg t1_jcu8mja wrote

HiByOS is based on Android.

1

kazuviking t1_jcn0ujh wrote

Like that ever stopped the chinese before.

5

WarHead75 t1_jcmufd7 wrote

I have a confession. I have never paid to use Aptx nor asked for permission to use McDonald’s WiFi

4

BullfrogOk9627 t1_jcniioa wrote

I think this would only be an impactful issue to developers. Unless you're over there going bill Nye on your personal equipment and even then the likelihood of anyone giving a crap would be like fox kicking down your door because you recorded that football game to a VHS through your VCR and you only obtained the express written consent to do so from the NFl and your local priest but failed to receive letter to consent from the blob that is Fox. And it's fox so they can straw suck butt toots ya know?

3

halotechnology t1_jcn5r4l wrote

What about apex adaptive ? This one is annoying levels pixels don't have it .

2

Schneider92 t1_jco49ex wrote

I wish Huawei will go back and add aptx to their recent phones now that they no longer need a license, but I doubt it.

1

iWazzmatazz t1_jcoep7o wrote

Does any one know if Windows support codecs other than SBC and how to verify which one is used when playing over BT headphones?

1

Electrical-Monitor27 t1_jcotgx0 wrote

Windows supports and uses aptx by default on the newer builds

2

CultofCedar t1_jcs2ahi wrote

I think it was defaulting to AAC for me when I tried on my new set up booting into Windows. I was looking for a way to switch it since it was easy on SteamOS/Linux to switch to AptX LL.

1

hextanerf t1_jcpxthb wrote

There's a dell Bluetooth audio driver that unlocked aptX on windows 8 and above. There's also an experimental LDAC driver made by the same people who developed Bluetooth tweaker. You'll need to manually delete ACVRP driver in device manager to get remote control to work, though

2