this post was submitted on 24 Jan 2025
837 points (99.5% liked)
Programmer Humor
20829 readers
2510 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, the problem (imo) isn't lossy v lossless. It's that the supported codecs are part of the Bluetooth standard and they were developed in like the 90s.
There are far better codecs out there and we can't use them without incompatible extensions on Bluetooth.
There's a push for Opus now, it's the perfect codec for Bluetooth because it's a singular codec that fits the whole spectrum from low bandwidth speech to high quality audio, and it's fully free
Opus is great, but there is no option to make it lossless, like what WavPack (also a free-as-in-freedom codec) provides for example.
Transparency is good enough, it's intended to be a good fit for streaming, not masters for editing
Why not have the option for true lossless available so that Bluetooth can be scaled up to sound good on even the highest end of systems.
You literally can not distinguish 192 Kbps Opus from true lossless. Not even with movie theater grade speakers. You only benefit from lossless if you're editing / applying multiple effects, etc, which you will not do at the receiving end of a Bluetooth connection.