5 ms·
re #1: This is basically because it's written into the standard that everyone implements. There are non-standardized extensions to get around this that nobody i
by AlotOfReading 5y ago
re #1: This is basically because it's written into the standard that everyone implements. There are non-standardized extensions to get around this that nobody implements because they're non-standard and a perpetual "This will be fixed by the next standard!". There are also codecs that mitigate the issue by solving the underlying bandwidth problem, but nobody implements those because there's licensing and thus it's not universal. All of this is made worse by the fact that there's really only a few vendors out there. Almost everyone buys the same stuff, which makes the same tradeoffs and the result is that everything sucks in basically the same ways.
- symlinkk 5y agoWhich is why people pay extra for Apple products, because they don’t make excuses like “this sucks because of the Bluetooth standard”, they build something that works even if it’s incompatible with non-Apple systems.
- AlotOfReading 5y agoFunny you should say that because one of the issues with Catalina was MacOS forcing all headsets, airpods included, to use the terrible default codec I was explaining. Moreover, this then forces all other audio data on the system down to the same terrible quality [1]. The official response was that this was "expected behavior". This is probably also the explanation for annoyance #3 in the article. [1] https://apple.stackexchange.com/questions/282705/airpods-extremely-poor-mic-quality-on-mac https://apple.stackexchange.com/questions/282705/airpods-ext...
- spopejoy 5y ago#1 was explicitly mentioned in TFA, so not sure why this is an oppy to say airpods fixes common bluetooth problems, instead it seems Apple is equally burdened by them??