I get the exact opposite experience, which is the reason why I switch from PulseAudio to Pipewire.
In my experience using pipewire, the audio is fixed and I canāt control the volume. I am however not experiencing cracking with my headphones plugged in. But in my case, I rather be able to use the volume.
You can use āpavucontrolā to adjust the volume it still works with pipewire
Pipewire make my sound so bad and I hear noise and crackling from it, It also gives me the following errors :
systemctl --user status pipewire.service
ā pipewire.service - Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2021-05-25 13:46:31 +01; 20min ago
TriggeredBy: ā pipewire.socket
Main PID: 1486 (pipewire)
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewire.service
āā1486 /usr/bin/pipewire
May 25 14:04:37 manjaro-med pipewire[1486]: (speech-dispatcher-espeak-ng-58) client too slow! rate:256/48000 pos:49883392 status:triggered
May 25 14:05:14 manjaro-med pipewire[1486]: alsa-pcm front:0: snd_pcm_status error: Broken pipe
May 25 14:05:14 manjaro-med pipewire[1486]: (speech-dispatcher-dummy-52) client too slow! rate:256/48000 pos:51658752 status:awake
May 25 14:05:14 manjaro-med pipewire[1486]: (speech-dispatcher-espeak-ng-58) client too slow! rate:256/48000 pos:51658752 status:triggered
May 25 14:06:03 manjaro-med pipewire[1486]: alsa-pcm front:0: snd_pcm_status error: Broken pipe
May 25 14:06:03 manjaro-med pipewire[1486]: (speech-dispatcher-dummy-52) client too slow! rate:256/48000 pos:54008576 status:awake
May 25 14:06:03 manjaro-med pipewire[1486]: (speech-dispatcher-espeak-ng-58) client too slow! rate:256/48000 pos:54008576 status:triggered
May 25 14:06:40 manjaro-med pipewire[1486]: alsa-pcm front:0: snd_pcm_status error: Broken pipe
May 25 14:06:40 manjaro-med pipewire[1486]: (speech-dispatcher-dummy-52) client too slow! rate:256/48000 pos:55783680 status:awake
May 25 14:06:40 manjaro-med pipewire[1486]: (speech-dispatcher-espeak-ng-58) client too slow! rate:256/48000 pos:55783680 status:triggered
systemctl --user status pipewire-pulse.service
ā pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2021-05-25 13:47:17 +01; 2h 1min ago
TriggeredBy: ā pipewire-pulse.socket
Main PID: 1748 (pipewire-pulse)
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewire-pulse.service
āā1748 /usr/bin/pipewire-pulse
May 25 15:24:19 manjaro-med pipewire-pulse[1748]: (speech-dispatcher-dummy-10) client missed 1 wakeups
May 25 15:24:19 manjaro-med pipewire-pulse[1748]: (speech-dispatcher-espeak-ng-13) client missed 1 wakeups
May 25 15:38:49 manjaro-med pipewire-pulse[1748]: (speech-dispatcher-dummy-10) client missed 1 wakeups
May 25 15:38:49 manjaro-med pipewire-pulse[1748]: (speech-dispatcher-espeak-ng-13) client missed 1 wakeups
May 25 15:42:37 manjaro-med pipewire-pulse[1748]: pulse-server 0x5642c0265870: [libphonon-probe] ERROR command:87 (EXTENSION) tag:2 error:19 (Operation not supported)
May 25 15:42:39 manjaro-med pipewire-pulse[1748]: pulse-server 0x5642bfe5f300: [xdg-desktop-portal-kde] ERROR command:87 (EXTENSION) tag:5 error:19 (Operation not supported)
May 25 15:42:39 manjaro-med pipewire-pulse[1748]: pulse-server 0x5642bfe5f300: [xdg-desktop-portal-kde] ERROR command:87 (EXTENSION) tag:6 error:19 (Operation not supported)
May 25 15:45:35 manjaro-med pipewire-pulse[1748]: pulse-server 0x5642c0258720: [Firefox] UNDERFLOW channel:0 offset:11569152 underrun:2048
May 25 15:45:44 manjaro-med pipewire-pulse[1748]: (Firefox-27) client missed 1 wakeups
May 25 15:46:02 manjaro-med pipewire-pulse[1748]: pulse-server 0x5642c0258720: [Firefox] UNDERFLOW channel:1 offset:11497472 underrun:2048
At the moment, I am not at all interested in PIpewire, mainly because I have a Jack/Alsa/Pulse setup that works reliably for audio production without breaking internet streaming for those days when Iām not mixing sound.
At the moment, the Pipewire configuration on Manjaro breaks my Jack setup, so I have disabled the pipewire systemd service.
It is not at all clear to me that Pipewire is currently able to replace Jack, much less improve upon it. Jack has been around long enough that most of the kinks have been worked out, and the few that havenāt have published workarounds.
If Pipewire truly becomes a ādrop-inā replacement for both Pulse and Jack, I might consider switching over, but I would prefer that it remain opt-in rather than opt-out, since what I have works and I have no interest in changing it for the sake of change.
New Pipewire release is out in Manjaro unstable now
Losing an equalizer would be a disaster for people like me, seriously defective hearing. Like being submerged.
Losing what equalizer?
You wonāt lose any equalizer with Pipewire. In fact, you will get more than just an equalizer. Meet PulseEffects:
You may be interested in the changes in PipeWire 0.3.31. The release notes say āJACK has seen massive stability improvementsā, among other JACK improvements.
i looked around trying to understand what is Pipewire; and what i gathered is that itās like wayland to xorg,
but apart from it being more advanced and have support for professionals applications(and better latency?), why would i personally want Pipewire?;
i didnāt see any mentions of it having a better sound quality,and all i do is in this regard is watching videos and listening to music and the sound seems fine to me, so?
See: Pipewire as default in Manjaro in the near future? - #20 by mynewlaptop
Pipewire is a huge boon for those who use bluetooth headsets. I donāt know if Wayland can similarly claim to improve user experience.
It also fixed a headphones (dis)connect problem for me. Nice. Now I can call it usable enough.
Cool. I may check it out on a separate partition onā¦ some computer or other. I am still happy with my setup, though, and am more interested in making musicāor something like musicāthan in configuring a new system right now.
I am edging away from iOS/MacOS music production out of exasperation with Appleās addiction to changing things so that nothing works unless one gives them lots of money for new hardware to run the newest iteration of their OSās. I assume that profit isnāt the motivating factor behind pipewire, and if it can improve on the somewhat cobbled-together alsa/jack/pulse environment many of us find ourselves in currently, it may turn out to be quite useful for new installs.
But Iām not inclined to switch just to switch; I am in fact weary of the constant stream of Better Things that are often just different things that donāt get along well with the things that were already there and working fine.
So Iād still prefer that it not be enabled by default in a future update. Thatās all, really.
uninstalling pulseaudio
and installing manjaro-pipewire
fixed my bluetooth headset from sound popping/crackling
Totally different from: Pipewire as default in Manjaro in the near future? - #24 by medmedin
Iām really impressed by the speed of pipewire development. In contrast PulseAudio seems to have slowed to a crawl. If you have a sound issue, itās very likely that the fix will appear in pipewire before pulseaudio.
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.