News for hackers. Stuff that matters.
Re:Opus 1.5 released: Opus gets a machine learning upgrade by out_of_protocol on Monday March 04, 2024 @01:30PM (#39594037)
Why the hell opus still not in Bluetooth? Well i know - sweet sweet license fees

(aKKtually, there IS opus codec, supported by pixel phones - google made it for VR/AR stuff. No one uses it, there are about ~1 headphone with opus support )

Re:Opus 1.5 released: Opus gets a machine learning upgrade by lxgr on Monday March 04, 2024 @01:53PM (#39594370)
As you already mention, it's already possible to use it. As for why hardware manufacturers don't actually use it, you can thank beautiful initiatives such as this: https://www.opuspool.com/ (previous HN discussion: https://news.ycombinator.com/item?id=33158475).
Re:Opus 1.5 released: Opus gets a machine learning upgrade by dogma1138 on Monday March 04, 2024 @02:10PM (#39594594)
Opus isn’t patent free, and what’s worse it’s not particularly clear who owns what. The biggest patent pool is currently OpusPool but it’s not the only one.

https://www.opuspool.com/

Re:Opus 1.5 released: Opus gets a machine learning upgrade by pgeorgi on Monday March 04, 2024 @03:13PM (#39595394)
No codec (or any other technical development, really - edit: except for 20+ years old stuff, and only if you don't add any, even "obvious" improvements) is known patent free, or clear on "who owns what."

Folks set up pools all the time, but somehow they never offer indemnification for completeness of the pool - because they can't.

See https://en.kangxin.com/html/2/218/219/220/11565.html for a few examples how the patent pool extortion scheme already went wrong in the past.

Re:Opus 1.5 released: Opus gets a machine learning upgrade by xoa on Monday March 04, 2024 @03:31PM (#39595652)
FWIW, submarine patents are long dead, so it is possible to feel assured that old enough stuff is patent free. Of course that denies a lot of important improvements, but due to diminishing returns and the ramp of tech development it's still ever more significant. A lot of key stuff is going to lose monopoly lock this decade.
Re:Opus 1.5 released: Opus gets a machine learning upgrade by pgeorgi on Monday March 04, 2024 @03:53PM (#39595920)
You're right. I could still amend the post, so I added the 20+ years caveat. Thanks!
Re:Opus 1.5 released: Opus gets a machine learning upgrade by dogma1138 on Monday March 04, 2024 @03:25PM (#39595565)
No one said that Opus is the only one suffering from licensing ambiguity, but comparing it to say AptX and its variants which do have a clear one stop shop for licensing (Qualcomm) it’s a much riskier venture especially when it comes to hardware.
Re:Opus 1.5 released: Opus gets a machine learning upgrade by pgeorgi on Monday March 04, 2024 @03:55PM (#39595960)
A drive-by patent owner can show up on anything, and if they don't want to license to you, your entire product is bust.

Even if it's AptX and Qualcomm issues you a license in exchange for money. I wouldn't even bet on being able to claw back these license costs after being ordered to destroy your AptX-equipped product after it ran into somebody else's patent.

The risk that this happens is _exactly_ the same for Opus or AptX.

Re:Opus 1.5 released: Opus gets a machine learning upgrade by tux3 on Monday March 04, 2024 @03:43PM (#39595782)
Making a patent troll is just a matter of putting up a press release and a web page.

I could claim to have a long list of patents against AptX. Anyone could.

Of course I'm not willing to disclose the list of patents at this time, but customers looking to be extorted may contact me privately.

Re:Opus 1.5 released: Opus gets a machine learning upgrade by rockdoe on Monday March 04, 2024 @06:05PM (#39597367)
FhG and Dolby did eventually put up a list of patents you are licensing from them.

It makes for some funny reading if you're familiar with the field. (This should not be construed as legal advice as to the validity of the pool)

Re:Opus 1.5 released: Opus gets a machine learning upgrade by bdowling on Monday March 04, 2024 @06:09PM (#39597403)
At least in the U.S., anyone can look up all the patents a person/entity owns. So, your fraud wouldn’t get very far.

https://assignment.uspto.gov/patent/index.html#/patent/searc...

Re:Opus 1.5 released: Opus gets a machine learning upgrade by pgeorgi on Monday March 04, 2024 @07:03PM (#39597767)
"I represent the holders of the patents in question" is simple enough. I wonder if it's fraud, if all you're putting out is an unverifiable claim on the net. The pool operators do that all the time.
Re:Opus 1.5 released: Opus gets a machine learning upgrade by bdowling on Tuesday March 05, 2024 @04:16AM (#39601074)
Someone who has no basis to bring a patent infringement claim selling a settlement of such a claim to an alleged infringer is clearly fraud.

It’s like someone selling a deed to land they don’t own, or leasing a property they don’t own to a tenant.

Re:Opus 1.5 released: Opus gets a machine learning upgrade by pgeorgi on Tuesday March 05, 2024 @05:29AM (#39601599)
The point isn't to sell a settlement. It's to publish "oh, we're totally serious that there are patents in our control. We won't tell you which ones, we don't tell you what we want from you. If you're interested, reach out to us."

Few people will even bother to try, and if so, you keep them at a distance with some random bullshit (communication can break down _sooo_ easily), but it certainly poisons the well by adding a layer of FUD to the tech you're targeting with your claims.

Standard fare of patent pool operators, and it's high time to reciprocate.

Re:Opus 1.5 released: Opus gets a machine learning upgrade by rockdoe on Monday March 04, 2024 @05:10PM (#39596832)
Opus isn’t patent free

The existence of a patent pool does not mean there are valid patent claims against it. But yes, you may be technically correct by saying "patent free" rather than "not infringing on any valid patents". That said historically Opus has had claims against it by patents that looked valid but upon closer investigation didn't actually cover what the codec does.

Just looks like FUD to me. Meanwhile, the patent pools of competing technologies definitely still don't offer indemnification they cover all patents, but have no problem paying a bunch of people to spew exactly this kind of FUD - they're the ones who tried to set up this "patent pool" to begin with!

Re:Opus 1.5 released: Opus gets a machine learning upgrade by giantrobot on Monday March 04, 2024 @02:04PM (#39594514)
The BT SIG moves kind of slow and there's a really long tail of devices. Until there's a chip with native Opus support (that's as cheap as ones with AAC etc) you wouldn't get Opus support even if it was in the spec.

Realistically for most headphones people actually buy AAC (LC and HE) is more than good enough encoding quality for the audio the headphones can produce. Even if Opus was in the spec and Opus-supporting chips were common there would still be a hojillion Bluetooth devices in the wild that wouldn't support it.

It would be cool to have Opus in A2DP but it would take a BT SIG member that was really in love with it to get it in the profile.

Re:Opus 1.5 released: Opus gets a machine learning upgrade by out_of_protocol on Monday March 04, 2024 @02:13PM (#39594647)
They chose to make totally new inferior LC3 codec though.

Also, on my system (Android phone + BTR5/BTR15 Bluetooth DAC + Sennheiser H600) all options sound realy crappy compared to plain old usb, everything else is the same. LDAC 990kbps is less crappy, by sheer brute force. I suspect it's not only codec but other co-factors as well (like mandatory DSP on phone side)

Re:Opus 1.5 released: Opus gets a machine learning upgrade by giantrobot on Monday March 04, 2024 @05:28PM (#39597001)
I've got AirPods and a Beats headset so they both support AAC and to my ear sound great. Keep in mind I went to a lot of concerts in my 20s without earplugs so my hearing isn't necessarily the greatest anymore.

AFAIK Android's AAC quality isn't that great so aptX and LDAC are the only real high quality options for Android and headphones. It's a shame as a lot of streaming is actually AAC bitstreams and can be passed directly through to headphones with no intermediate lossy re-encode.

Like I said though, to get Opus support in A2DP a BT SIG member would really have to be in love with it. Qualcomm and Sony have put forward aptX and LDAC respectively in order to get licensing money on decoders. Since no one is going to get Opus royalties there's not much incentive for anyone to push for its inclusion in A2DP.

Re:Opus 1.5 released: Opus gets a machine learning upgrade by maep on Tuesday March 05, 2024 @04:50AM (#39601314)
"Inferior" is relative. The main focus of LC3 was, as the name suggests, complexity.

This is hearsay: Bluetooth SIG considered Opus but rejected it because it was computationally too expensive. This came out of the hearing aid group, where battery life and complexity are a major restriction.

So when you compare codecs in this space, the metric you want to look at is quality vs. CPU cycles. In that regard LC3 outperforms many contemporary codecs.

Regarding sound quality it's simply a matter of setting the appropriate bitrate. So if Opus is transparent at 150 kbps, and LC3 at 250 kbps thats totally acceptable if that gives you more battery life.

Re:Opus 1.5 released: Opus gets a machine learning upgrade by out_of_protocol on Tuesday March 05, 2024 @08:21AM (#39602990)
Regarding complexity, do you have any hard numbers? Can't find anything more than handwaving
Re:Opus 1.5 released: Opus gets a machine learning upgrade by giantrobot on Tuesday March 05, 2024 @04:59PM (#39609647)
You can check out Google's version which I assume is bundled in Android: https://github.com/google/liblc3
Re:Opus 1.5 released: Opus gets a machine learning upgrade by maep on Tuesday March 05, 2024 @05:17PM (#39609868)
I remember seeing published numbers based on instrumented code, but could not find it.

I did a quick test with the Google implementation (https://github.com/google/liblc3) which is about 2x faster than Opus. To be honest, I expected a bigger difference, though it's just a superfical test.

A few things that also might be of relevance why they picked one over the other:

  - suitability for DSPs
  - vendor buy-in
  - robustness
  - protocol/framing constraints
  - control
Re:Opus 1.5 released: Opus gets a machine learning upgrade by out_of_protocol on Wednesday March 06, 2024 @05:18AM (#39614351)
Thanks for checking it, appreciated

- Well, 2x is nothing to write home about.

- DSP-compatibility probably considered but never surfaced as a reason, so hard to guess investigation results. + Pricing and availability of said DSP modules

- Robustness - well, that's one of the primary features of opus, battle tested by WebRTC, WhatsApp etc. (including packet loss concealment (PLC), Bit-Rate Redundancy (LBRR) frames)

- Algorithmic delay for opus is low, much lower than older BT codecs, so that definitely wasn't a deal breaker

- Ability to make money out of standard is definitely important thing to have

Re:Opus 1.5 released: Opus gets a machine learning upgrade by maep on Wednesday March 06, 2024 @12:45PM (#39618571)
If used in a small device like a hearing aid, a 2x factor can have a significant impact on battery life.

VoIP in general experiences full packet loss, meaing if a single bit flips the entire packet is dropped. For radio links like Bluetooth it's possible to deal with some bit flips without throwing the entire packat away.

Until 1.5 Opus PLC was in my opinion it's biggest weakness, compared to other speech codecs like G.711 or G.722. A high compression ratio causes bit flips to be much more destructive.

As for making moeny, Bluetooth codecs have no license fees.

Re:Opus 1.5 released: Opus gets a machine learning upgrade by derf_ on Thursday March 07, 2024 @06:13AM (#39627604)
> For radio links like Bluetooth it's possible to deal with some bit flips without throwing the entire packat away.

Opus was intentionally designed so that the most important bits are in the front of the packet, which can be better protected by your modulation scheme (or simple FEC on the first few bits). See slide 46 of https://people.xiph.org/~tterribe/pubs/lca2009/celt.pdf#page... for some early results on the position-dependence of quality loss due to bit errors.

It is obviously never going to be as robust as G.711, but it is not hopeless, either.