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.
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.
My wife had some Logitech headphones that for some godforsaken reason were operating in some voice only ultra low bitrate by default. I mean, they weren’t fantastic even after I fixed that, but the quality was unbelievably low, like somebody making a phone call from the moon, and how she’d put up with it for nearly a year I’d no idea. I only found out after I noticed her swapping between a wired set for general use and wireless for Discord.
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.