- cross-posted to:
- gadgets@lemmit.online
- cross-posted to:
- gadgets@lemmit.online
But of course we all know that the big manufacturers don’t do this not because they can’t but because they don’t want to. Planned obsolescence is still very much the name of the game, despite all the bullshit they spout about sustainability.
Some Bluetooth controllers can’t handle the bandwidth required for sound input and output at the same time unless it’s at very low quality, and if Windows suspects such a device is in use, it defaults to the low quality mode as users are more likely to be able to tolerate it than tolerate their headphones not working at all. It’s overly cautious, though, and uses the low quality mode far more than it has to.
That’s one nice thing I found about Linux, it’s pretty easy to change the codec. Just fiddle a bit until it sounds good without static or delays. This is especially important when using multiple Bluetooth devices simultaneously since the Bluetooth chip can only handle so much data.
Maybe Windows has the option, IDK, poke around a bit and see what’s available. I couldn’t find the option on my work Mac, so I ended up just using wired headphones on my work computer.
It’s super quick to swap it on Windows once you know the problem exists and know where to look. You just click the audio icon in the system tray and change the output device in the dropdown from the headset version of the device to the headphones one, and it enables all the higher-bandwidth modes. I’m not sure there’s user-accessible control over which specific codec gets used, though.
That’s basically what you get on Linux, but there’s a third option for a low energy codec.
On macOS, I wanted to use the “headset” mode to hopefully cut down just enough on bandwidth to get rid of choppy playback, but I didn’t see an option for it. I have had quality change quite a bit based on the app I’m using (I guess it sometimes gets interpreted as a headset?), so I know it can do it, I just don’t know how to control it.