for people as confused as I am, "Linux Audio" here refers to some sort of libre software group centered around audio applications on linux, not the actual audio stack of linux systems.
I have never heard of NON before and beginning the story in media res while omitting any details of what the 3 antagonists asked him to do with his project makes the whole thing confusing. Until he got to talking about the LAD mailing list, which I am somewhat familiar with, I thought it was some sort of scam post.
"Please use the original title, unless it is misleading or linkbait."
https://github.com/dheera/scripts/blob/master/config/install...
if you want your audio to sound better than a snake in a swimming pool, and nobody will ever tell you that. On iOS, Android, Windows, MacOS, bluetooth headsets pretty much "just work".
I'm a Linux fan and all my computers run Linux but Bluetooth audio IS broken.
https://github.com/dheera/scripts/blob/master/jabra-stop-cha...
Also, if you didn't do what my parent post's script did, you probably have shitty audio on your Jabra.
My biggest gripe is that I can't use the microphone at the same time as the headphones, without switching to tin can mode.
And there are fixes at the protocol layer already, you just have to use nonstandard extensions. This is how airpods work.
If your going to do wireless on windows, either get a separate mic, use a corded headset, or a headset with a USB-wireless adapter unless you want it sounding like a tin can.
The headset modes haven’t appeared under Linux at all, which happens to suit me just fine, so I haven’t investigated the lack. A couple of times I’ve had issues with connecting at the BlueZ level, but putting the laptop to sleep and waking it up again has resolved it. (Just restarting bluetoothd doesn’t help.)
I was running PulseAudio for a few weeks, then I switched to PipeWire. I no longer get the Bluetooth indicator on it in waybar, but other than that the switch was fairly uneventful. One point is an improvement: it now seems to remember which devices I like to use, so that when I plug in my Yeti microphone it doesn’t switch audio output to it (it has a 3.5mm monitor port and can feed audio from the computer through that too), which it had always done under PulseAudio and I hadn’t yet gone to the trouble of figuring out how to stop it from doing that. One point in the Bluetooth device handling is potentially a slight regression: when silence should be being fed through the connection, I observe extremely quiet whine which I didn’t under PulseAudio. Not sure what’s at fault there.
An older latitude works perfectly.
I wouldn't go that far. On windows my headset shows up as two cryptically named devices, and using the wrong one or touching microphone input destroys the audio quality.
Windows 10 gets decent audio quality until you try to engage the microphone at which point it switches to a different audio driver with the quality of bad cellular phone call. It sees the headphones AND a generic “Bluetooth headset”. I’ve seen the same behaviour across Sony, Beats, and AirPods.
NixOS 21.05; with last year's release, it did default to headset mode, and the audio profile switching was hidden behind an "advanced" button, so things are improving fast.