PipeWire

“Pipewire just works without needing the awfulness of pulseaudio”

“Since pipewire landed in arch all my issues with sound magically vanished.”

“If you use a fresh install and leave everything default, I'm sure it would work for you”

“sound just randomly broke (I had no idea why, debugging pipewire is a nightmare)”

“PipeWire has better reliability, lower CPU usage, and lower latency.”

“was a drop-in replacement for pulseaudio with (almost*) full compatibility and none of the stability issues”

“Important to people being happy now is that Lennart Poettering didn't write pipewire.”

“people learned from issues that pulseaudio had and then came pipewire. Everyone is happy now.”

“Tried a ton of different PipeWire settings here, couldn't find out a resolution.”

“the transition to Pipewire seems over with and It's no longer a total mess of ALSA+JACK+Pulse+PipeWire”

“The rest of the world's moved to pipewire, which also provides a jack-compatible interface.”

“Pipewire is flat-out better than pulse, while including sufficient compatibility”

“bugs in Pipewire/Wireplumber were still getting ironed out and were rendering my audio stack temporarily unusable”

“they switched from PulseAudio to PipeWire. I've had zero issues since then.”

“man pipewire leaves you completely in the dark as to what the thing even does.”

“Pipewire is shonky, I have to restart now and then on my steam deck”

“mostly audio issues with how they set up PipeWire and regressions with some releases”

“pipewire is a never ending pain in the ass full of "magic" behavior and weird bugs”

“It's baffling to me that anyone can imagine pipewire has been created from scratch without any lessons learned from pulseaudio”

“but pipewire is an order of magnitude more complex than pulseaudio.”

“PipeWire is like 10 years newer than PulseAudio. It probably had a chance to learn some lessons!”

“Persistent input to output mappings in PipeWire is impossible without third party tools or custom scripts you run on boot.”

“has made getting my audio routing all correct (e.g. for streaming) much more difficult than it is on Windows”

“up-to-date versions of Pipewire can almost mostly sometimes do the right thing, usually”

“works fine with PipeWire, without needing to tweak anything.”

“with pipewire ... haven't had any issues across Google Meet, Zoom, or Teams”

“Usually PipeWire handles these situations better than PulseAudio”

“instantly solved basically 90% of audio issues on Linux through its compatibility with Pulseaudio”

“Since Pipewire came out, I haven't had any problems with audio on Linux and I can dial the latency down to single-digit ms.”

“PipeWire speaks Jack so if built with Jack support, any Jack aware application will connect to PipeWire with no need to start Jack”

“I finally have a low-ish latency audio system (enough for mixing, if not recording)”

“PipeWire seems to solve all the audio stuff for me, zero problems since I made the switch.”

“I'm not entirely sure what this is for. Certainly it's useful for streaming music from device A to device B, but I'm not sure anybody uses it in a production setting.”

“Actually I am using PipeWire with rtkit on Debian. But somehow it does not solve my midi problems.”

“PipeWire with rtkit works incredibly stably with wildly short buffer lengths (low latency).”

“Screen recording like screen sharing works perfectly fine with PipeWire.”

“you can get zero copy window and screen contents through PipeWire thanks to dmabufs”

“pipewire still has issues properly delivering audio on my system with all core load of ~50%”

“PipeWire fixed all issues with both screen sharing and desktop audio when it was introduced years ago”

“I don't seem to have any issues with audio anymore since Pipewire became default on Ubuntu”