Is Pipewire ready for daily use?

Users of Pipewire:
I would like to know if you can watch videos, pause the videos, unpause without sound problems.
Can you listen to music for an extended period, approximately 10 - 12 hours without sound problems.
After the PC resume from sleep or hibernation or after a restart, are there any issues with Pipewire.
I just want things to work without constant fiddling.
One more note: I am using the KDE desktop.
If my questions seem unreasonable, disregard this post.


I am not using KDE - but pipewire - no problems - business as usual.

But like pulseaudio - you need to watch out for your outputs - pasystray package is a great helper.

1 Like

I’m on cinnamon and switched to pipewire about two weeks ago. So far so good. Knocking on wood :wink:

1 Like

Some here on my Pinebook Pro with Plasma.

Will be switching my desktop later tonight.

1 Like

Thanks, I’ll keep that in mind.
Maybe I’ll take the plunge and see how it goes.

Thanks you all :slightly_smiling_face:

Sure, but there’s no tray icon on GNOME and KDE probably already has something for this. :wink:

1 Like

I’ve been using Pipewire for exactly 2 weeks now on Plasma + Nvidia Proprietary (no wayland). YouTube videos play and pause just fine. Since you’re on plasma, I also use KDE connect and it still play/pauses just fine. I just tested completely turning off my displays while sleeping the computer and turning them back on before waking it. Audio output was not impacted on the jacks, but display audio disappeared from the audio tray. It can be re-enabled in the configure audio devices menu without issue. I have been listening to music for several hours at a time and never encountered issues with my wired audio.


Currently, connecting and staying connected with my buds (Soundpeats H1 BT5.2 on aptX and Intel 9260 BT5.1) is a pain. Pipewire does support it, but it’s not entirely documented: Pipewire Wiki Bluetooth Configuration and Archwiki Bluetooth on Pipewire are the only real resources I’ve found that don’t involve asking. It seems the pipewire people know it though pipewire gitlab issue. Some things I’d really like aren’t implemented either. Bluetooth needs improvement for my needs. sudo systemctl restart bluetooth solves a few of my issues immediately.

tldr: Pipewire migration from Pulseaudio has been smooth. Disregard bluetooth if it’s irrelevant to you. All other features I use are at feature parity to Pulseaudio or better (don’t need configuration beyond activation/toggling).

1 Like

I’ve been testing pipewire version 0.3.27 for more than a week now. (XFCE with 5.12 kernel) No problems so far, it works much better than PulseAudio. Pipewire even fixed a very nasty issue I was having on PulseAudio: Bluetooth sound and microphone at the same time - #7 by mynewlaptop

I heard that Fedora is migrating to Pipewire. I recommend Manjaro do the same.

1 Like

Fingers crossed. Taking the plunge, will let you know how it goes after a few days.


Issue here: A buffer in Pipewire?

@nam1962 I cannot answer this.
However I am reporting that all’s well between me and Pipewire. Happy to have taken the plunge.
Thanks to all who have given me words of encouragement.

I’ve been using PipeWire since March and I have to say that it is not ready yet to replace PulseAudio. Some annoying bugs here and there (according to their bugtracker), for instance I have been affected with a broken auto-switching between speakers and headphones on jack plug in/out. Too annoying to tolerate it. I think we should let Fedora users test it further, no need for haste. As with Wayland, those who want it are free to enable it and enjoy/suffer then.
PS: I don’t think Manjaro should be a testing site for every new feature invented by RH.


How to switch fully to pipewire ?

1 Like

install the manjaro-pipewire package and reboot

1 Like

I’m suprised by this because I found pipewire to be much more stable and reliable than PulseAudio. I suspect people have become accustomed do PulseAudio’s many many quirks and have working solutions around them.

Had some issues :

sudo pacman -S manjaro-pipewire                        ✔  1m 8s  
[sudo] password for marko: 
resolving dependencies...
looking for conflicting packages...
:: manjaro-pipewire and manjaro-pulse are in conflict. Remove manjaro-pulse? [y/N] y
:: pipewire-pulse and pulseaudio are in conflict. Remove pulseaudio? [y/N] y
:: pipewire-pulse and pulseaudio-bluetooth are in conflict. Remove pulseaudio-bluetooth? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing pulseaudio breaks dependency 'pulseaudio=14.2-3' required by pulseaudio-equalizer
:: removing pulseaudio breaks dependency 'pulseaudio=14.2-3' required by pulseaudio-jack
:: removing pulseaudio breaks dependency 'pulseaudio=14.2-3' required by pulseaudio-lirc
:: removing pulseaudio breaks dependency 'pulseaudio=14.2-3' required by pulseaudio-rtp
:: removing pulseaudio breaks dependency 'pulseaudio=14.2-3' required by pulseaudio-zeroconf

These 5 packages need to be removed first:

1 Like

Switched about a month ago, and I’m more than happy. Bluetooth works incredibly reliably, always connects to my Bluetooth speaker both after reboot and resume from suspend. Also, latency is considerably lower.

How did you measure latency?

Try if you can change that in pavucontrol. If not, file them an issue here: Issues · PipeWire / pipewire · GitLab