Oh no not systemctl --user restart pipewire.service!

I've been using "Linux audio", namely jack, Ardour, freewheeling, hydrogen e.a. for more than a decade. But you can take your shiny pipewire and shove it where the sun doesn't shine.

I understand a couple of those words!

Why is my Bluetooth stuttering

Yours too?

Pfff why not the sudo reboot now.
That's much better /s

A decade ago, all distributions switched to a new sound stack that is better by all metrics. He is saying he is old and knows the name of the old stuff, therefore new stuff bad

I have linux issues every time I have a "new" machine, and it makes sense. Linux is a volunteer/ opensource project. It isn't getting chipsets before, and building drivers in advance of hardware releases (at least it mostly isn't; I understand that some times it does).

Because of that, the newer your harder, the crappier it works. The longer your hardware has been around, in-general, my experience is that Linux becomes an "it just works experience".

Also, fuck you mediatek 7925e.

The pipewire switch happened far more recently than a decade ago, you may be thinking of pulseaudio, which had far more valid criticisms than pipewire does now.

May as well just reinstall the os at this point.

Pipewire is awesome, I can't believe they did it, they implemented all the old APIs for the other system and brought it into great harmony. But hey I'm a wayland user too

okay here me out:

Pipewire is one of the best pieces of software I used. It has a cool ass patchbay and unlike PulseAudio I've never had it crash on me. It is the best thing that happened to Linux audio

I was blown away when I connected my phone to my PC through Bluetooth and phone audio started playing through my PC. It just worked without me touching anything

I also really like how "Linux Studio Plugins" are standalone apps that you can run. I don't produce music or anything but I still use stuff like equalizers and spectrum analyzers. It is insane how flexible the "each app has inputs and outputs you can hook together" architecture is.

PulseAudio probably also had some of these features but I never used those because pulse would fall apart every time I touched it. Pipewire doesn't

Broken Linux audio is about to become old news

You're an idiot who doesn't know what you're talking about. Pipewire isn't really up for production (and by far not a decade old) and whoever decided to activate it by default might have had easy desktop use and switching to BT or mobile audio trash in mind. If it comes to latency, low complexity or reliability, pipewire is terrible. It also doesn't add anything useful that jack could not do, it only adds complexity where it's not needed.
PW is nice, if you're a newbie and want all your crappy BT shit to connect from the desktop so you can watch five tik-tok vids at the same time using you shiny "soundbar" (and have your voice comm blasting the neighbourhood), but it's a mess if you want to use realtime audio with more than two ports, MIDI and a device chain for recording or playback.

Don't matter replying, "Qwel", I put you in my special place for trolling, abusive children who do not contibute to civilization - the killfile.

That's the best thing bluetooth audio can do for you. Much better than anything it does to music.

i don't know about you but broken Linux audio has BEEN old news ever since i started using pipewire

seems to me like you're the troll. people who are advanced enough to want to use MIDI controllers and whatnot are advanced enough to just silently use the tools that work for them

I built a new 9950x3d + x870e system last year. trying to use the motherboard's wifi would kernel panic things. couldnt turn bluetooth on and off. couldn't control the RGB.

Now, WiFi works great. Bluetooth works great. OpenRGB supports the RGB. Things are great. Took time to get here, but we got here.

what is Pipeware? only install other thing, Linux is rich of alternatives (you don't have to cry for convincing to MS/Apple)

Oh. In my head both had happened in close succession

Say hello to Mr Killfile...

I do, in fact, not know what I am talking about. Is there actually some sound engineers or musicians that are having real-life issues with it ?

Sir, this is a Wendy's

Gotta be real here for a moment, the last time I had any sort of trouble with audio on Linux was back in the day when I was still fiddling about with Gentoo. But that was, what, fifteen, twenty years ago?

Try changing the audio codec in the hardware profile.

9950x3d

🤤

Just had a random occurance of pipewire not allowing me to switch my audio back to my headphones (played some music through speakers before) through the settings. Had to switch it using the terminal but then it worked. Took about 10 minutes to figure out

ewwwwww SystemD

The strong irony is that when high core count and asymmetrical multi-CCD chips started rolling out, they were having CCD pinning issues in windows. But since Linux has a scheduler that has been NUMA awareness for ages... Linux was actually just fine with these things.

Linux was actually better for bleeding edge hardware for once.

Windows habit

No, eww is eww. Systemd is systemd.

Been around since OSS and ALSA was the new kid on the block. Yet to experience these supposed sound issues.

I 'member having to use a script to do software mixing of multiple audio streams in alsa, so I could listen to a music CD while playing WOW. Otherwise whichever thing started first would grab the audio device and the other thing couldn't use it. This would've been back in like 2006-7.

It's ironic how, just like people make jokes of Linux audio even though it's been stable for years, people stil joke about Windows throwing BSODs or requiring reinstalls non-stop, even though the last BSOD I had that wasn't caused by faulty hardware or a weird one-of-a-kind driver issue was... 12 years ago? Something like that.

All i can say is, you have been a very lucky individual.

Flashbacks to having pavucontrol open, editing default.pa and watching pulse crash over and over trying to get echo cancelling working

Same, I have it running on several different laptops/desktops, it's probably a certain piece of hardware.

I'm sure it's happening to people, just not everyone.

Pro tip: putting the URL in the following character sequence will just show the image in your comment instead of the URL

![](url)

you can also add a description, mostly useful for accesibility (screen readers for e.g. sight impaired people):

![description goes here](url)

I have a strange Dual Screen Asus on Intel with mobile arc. About 10% of the time, waking from sleep will crash the taskbar, something about the video driver not being ready yet.

I just wrote a daemon to kick plasmashell in the ass if it notices the bar isn't there.

try disabling bluetooth power saving

try libspa-bluetooth if pipewire

force A2DB profile in pavucontrol or blueman

make sure you have bluez and bluez-utils?

WAYYYYLANDDDDDD SHAKES FIST IN AUTOHOTKEY

if you've been running the latest windows 11 that's very good luck

Then you didn't use your computer for much involving audio.

Pipewire has some neat tricks that i use on a daily basis but i can also make it crash on demand so idk :p.
I have a restart script in my home directory for that exact reason.

It just does not like audio going out my gpu, together with video, through my receiver and into my tv.
Receiver not on while linux was booting? Guess what, pipewire reboot.
Tv goes off because of "inactivity"? Thats a pipewire reboot

... And yet i love pipewire haha. But ye, audio issues are still a thing

Yes. The only times I've had any problem with pipewire were when pulse decided to run for some reason and disrupted everything.

Also, I can open a pipewire device, write data there, and not run into C assert faults. I can do this with oss and alsa too, of course, but AFAIK, it's impossible with pulse and all the Linux DEs ran on pure magic for a decade.

"Latest" as in "Insider"? I'm on the first Patch Ring at work, so I'm one of the five people who get the latest patches, but we're not Insiders. We had 3 BSODs last week when MediaTek fucked up their WiFi drivers and the devices crashed if connected to WiFi 7.

The previous BSOD I saw at work was 3 years ago. The tech came in, replaced the MOBO and the issue was solved.

It has a tendency to break my USB audio after updating the kernel. I just have to remember the incantation to restart it though and it seems to fix it.

Nah. I'm just gonna hope distros once the paper I'm submitting is accepted and I don't need this machine again. I think I'm going to go fedora so I can stay closer to bleeding edge on the kernel.

You must have been blessed by the hardware gods. I had several scripts bound to hotkeys to fix various issues that would occur regularly and this was only 5 or so years ago. Volume would reset, wrong sink would get selected, it would crash, it would crackle, it had bad latency but most of the time it was fine.

Here, you're not you when you're hungry