3 ms·
Same. The annoying thing that used to happen with bluetooth headsets, where macos suddenly decides to use them for input as well as output and the audio quality
by andrelaszlo 3y ago
Same. The annoying thing that used to happen with bluetooth headsets, where macos suddenly decides to use them for input as well as output and the audio quality drops noticeably (full duplex, bitrate, blabla), now happens even when the microphone isn't selected.
It really sucks. I'm not using a regular bluetooth headset, these are my hearing aids and my only way to get decent sound in meetings. Switching to mac last year was a mistake.
- bzzzt 3y agoAny application or website can select the default microphone or a specific audio device which can cause that bluetooth issue. And lots of applications are enabling the microphone even if they don't need it. I don't think switching away from mac would solve that.
- andrelaszlo 3y agoThe default microphone is set to another microphone. I can assure you that I didn't have this issue in Linux. :) There were other issues, of course, but they were at least solvable.
- bzzzt 3y agoMost conferencing applications or sites use a separate 'preferred' microphone and select that one.
- andrelaszlo 3y agoI'll look into if it has something to do with that. Thanks for the tip
- Adverblessly 3y agoOn KDE at least the Bluetooth widget lets you pick which audio profile to use, so if for some reason it decides to switch to a duplex profile you can just switch it back, though I can't remember the last time I was forced to do that.