Pulseaudio. For a long time my Sony headphones had no working mic. Then one magical update, I had full HSP as well as A2DP sink. It was amazing - I could take teams calls without having to change headsets!
Then one not-so magical update, poof it just went. I tried to scour the bug list in pulseaudio to find anyone who had experienced the same but found the bugtracker impossible to navigate without a login account.
So now I wait, and update, and pray for an update that restores this feature.
Just use a decently recent distro or update to pipewire (and recent kernel). Pulseaudio is basically not where the good things are done anymore. It’s been more than a year or 2 already that the sony phones have microphone working properly.
It is a hard moving bunch of pieces that needed to be in place. The user libraries (pulseaudio or pipewire) the bluez stack and the kernel. For a while things were almost working on the first parts but there were problems on the kernel side then the kernel received patches and it finally was able to support the good audio codec.
(I hate saying this, but) I’m on arch, and using pretty up-to-date versions of pulse and wireplumber, but no dice. I’ve tried the LTS kernel, still no dice. I think it’s a regression that has somehow largely gone unnoticed, because I cannot find any bug reports about it, despite the headphones being quite popular
That could be a combination of something only you have or really just a bug unreported. I would recommend trying to open a bug report and maybe more people can chime in and help.
I’ve personally had a bunch of regressions and problems with some versions, but it’s been fixed for my specific devices. Got 2 codecs for input/mic I can choose and the others for sound output including ldac working nicely.
It’s hard to make a bug report, since I can’t find the specific version that caused the regression, and it’s hard to downgrade that single package to do a binary search to find the regression without altering all the system packages. It’s a kind of “damned-if-you-do” catch-11 situation
The answer is PipeWire. It’s a drop-in replacement for PulseAudio that works.
I think that’s just branding. I use the pipewire / wireplumber stack for a while and have not noticed any big gains over vanilla pulse
Seems like you had unusual luck with pulseaudio. I had so many problems with it, I was considering switching back to Windows for some tasks.
I manually disabled HSP in pulseaudio. I’d rather use an external mic than subject myself to the atrocious audio quality of HSP.
But it’s a profile you can switch away from quite nicely using
pavucontrol
Anecdotally, I’ve had way more audio issues in Windows than I’ve had in Linux.
Linux audio setups don’t always work out-of-the-box, and sometimes require a bit more configuration, but once you get them set up the way you like, they stay that way.
Windows audio configuration is flaky as hell. It’s constantly changing with updates, and I’ve had so many issues with drivers just silently failing. It seems to have the most trouble with discrete sound cards and USB audio interfaces. I can’t tell you how many Discord and Teams calls I’ve had in Windows where the first 5 minutes is re-configuring audio settings that didn’t stick. This is basically a non-issue in my Linux setups.
macOS audio is probably the best combination of easy to configure and it works consistently. The biggest downside is that you need a lot of 3rd party software to do anything more advanced than setting a single device and volume for the entire system.
Note: I primarily use pipewire now. I used to have more problems back when I used pulseaudio.
I have no idea why Pulse is so bad. During my last foray into Linux, I created a shortcut for killing and restarting Pulse and pinned it to the dock. I also replaced all my game shortcuts with scripts that reinitialized pulse, then ran the game, then reinitialized pulse again when the game was closed.
Like, yeah. When you have everything working as it should, Linux runs smoothly and there are no more complications. But it’s a real pain in the ass that initial configuration, especially for newbies like me a couple of years ago.
I’m new to Linux and I was troubleshooting some audio issues and yeah I ended up uninstalling GNOME. Oops.
I once tried to uninstall every package to do with Wine but
sudo apt remove wine*wrecked the system past the point a high schooler could recover it
I’ve never had Linux sound issues I got no idea what u guys are always on about.
I think a netbook I had in 2014 was the last time I had any audio problems.
Has c/linuxmemes become c/excusestokeepusingwindows?
Hell ya. I’m resurrecting a netbook right this moment. Pretty stoked about it.
Gotta distrohop more my dude. Reinstall your OS every week.
Nar I was on arch now on QubesOS am happy where I’m at
i don’t have sound on Windows, so Linux will bot be hard to accomodate to then
After Windows 10 drops support, the only proprietary system left will be my Mac which I use for music. I’ll be damned if I’m going to try and get Ableton Live running in Wine with low latency. I really wish it wasn’t like that’s though.
sndio(8) moment.
(With one HDMI-related exception, I have had no trouble with ALSA, JACK, OSS, PulseAudio, or Pipewire)
We all live underground
deleted by creator
