Meiklejohnian absolutist. free speech as in free-for-everyone.
mutuals: 
there is no lossless bluetooth audio
-
-
Replying to @donk_enby @antumbral
but i actually like what Apple has been doing with pushing AAC for Bluetooth audio instead of the Qualcomm proprietary bullshit everyone else uses
1 reply 0 retweets 1 like -
Replying to @donk_enby
right, i mean more that they talk about the custom chips and teraflops and all of that, so you'd think with that much hardware they could say "lossless audio". i'm guessing it's not lossless, but if the quality is high enough that's fine. is it even bluetooth?
1 reply 0 retweets 0 likes -
Replying to @antumbral
When connected to Apple devices, the AirPods actually use a custom Bluetooth profile where they do narrowband SBC over Bluetooth LE for voice and AAC over Bluetooth.
1 reply 0 retweets 1 like -
Replying to @donk_enby @antumbral
They can do both at the same time too, so it doesn't have the annoying problem of music falling back to SBC as soon as an app tries to use a microphone, like on Android/everything else.
1 reply 0 retweets 1 like -
-
Replying to @antumbral
Qualcomm sells aptX HD as "near lossless". It maxes out at 576kbit/s, but you can't compare bitrates across codecs like that. Opus would probably be comparable at 128kbit/s, it's just that you can't put it in a wireless headphone and expect reasonable battery life.
1 reply 0 retweets 1 like -
This Tweet is unavailable.
-
Replying to @liminalitaet @antumbral
"it does not hesitate to use CPU to give you the best quality encoding at a given bitrate" "aptX HD can encode a 48 kHz 16-bit stereo audio stream using only 10 MIPS on a modern RISC processor with signal processing extensions."
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
Replying to @liminalitaet
I don't think there is a demand for it, except for people like me. Xiph has largely continued to exist and get funding by keeping MPEG in check and not letting them become a monopoly.
2:09 PM - 8 Dec 2020
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.