You are not logged in.
@hhh raised this idea, here and following posts: https://forums.bunsenlabs.org/viewtopic … 50#p137550
Pipewire now seems to have settled in, and have some advantages over PA, eg this comparison: https://itsfoss.com/pipewire-vs-pulseaudio/
BL is supposed to have a simple interface on top of an efficient modern base, so Pipewire looks like a good candidate for including.
Any opinions?
Has anyone hit nasty problems with PW suggesting it would be better to stay with PA for another release?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
No problems here. PipeWire/Wireplumber works as advertised. It's brilliant.
I don't care what you do at home. Would you care to explain?
Offline
I've no reason to prefer one over the other.
As long as when I fire up something that is supposed to output sound sound comes out the speakers at an acceptable level & quality, and my standards aren't that high for what's acceptable, I really don't care.
That being said, I've not tried pipewire, since pulse ain't broke I've had no occasion to fix it, so haven't tried to on general principles.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
That being said, I've not tried pipewire, since pulse ain't broke I've had no occasion to fix it, so haven't tried to on general principles.
There's literally no reason to switch at this point other than it's more forward compatible and it will work the same as far as you will be able to tell.
If you use Linux for anything audio/visual beyond just viewing/listening, you'll appreciate the flexibility combined with unification of the available sound daemons (ALSA, PulseAudio, Jack, GStreamer) that PipeWire with WirePlumber provides.
I don't care what you do at home. Would you care to explain?
Offline
Sure, no problems here either, so sounds like a good suggestion to me.
Offline
+1 here. Slackware switched over in -current soon after 15.0 (2 years ago?) and many are back porting it there. Works well and less prone to crashing it seems than pulseaudio.
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
PW working fine here and working as expected.
Real Men Use Linux
Offline
Pipewire s working fine on some rare other distros that I use, so I would bet that it would be a good choice for BL.
Last edited by altman (2024-08-28 12:53:49)
My Linux installs are as in my music; it s on Metal
Offline
Sounds pretty unanimous for Pipewire!
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
An example of the advantage of PipeWire...
Ardour is using jackd because I set it up that way (it's the audio defacto standard on linux, low latency, bro), Pithos (a Last.FM client) is using PulseAudio, and I'm recording the Pithos stream into Ardour and resampling it from 44.1 to 48K...
It'll still sound like a 64 bit sampled stream, the source, but cool nonetheless.
I don't care what you do at home. Would you care to explain?
Offline
Alright, I've been running pipewire
on this trixie/carbon installation nearly a year now and just found my old el-cheapo BT adaptor.
I installed the bluetooth
meta package and the suggests and also blueman
but I could not connect my bluetooth Sony WH-CH510 headset.
Error message:
connection failed: no audio endpoints registered
Recommended depends for blueman
are pulseaudio-module-bluetooth
or libspa-0.2-bluetooth
. Apt chose the wrong one
I found this Unix & Linux Stack Exchange post that fixed the issue. Very simple solution and if it hadn't have been early morning after a long day at work and a few beers last night I may have thought of that myself.
sudo apt install libspa-0.2-bluetooth && sudo apt purge pulseaudio-module-bluetooth
Reboot and enjoy!
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
^Thanks for finding that!
Maybe we will have to release both pipewire and pulse versions of bunsen-meta-bluetooth, depending on libspa-0.2-bluetooth or pulseaudio-module-bluetooth respectively? And perhaps declaring a Breaks on the opposite library?
(It might have been the bunsen-meta-bluetooth direct dependency on pulseaudio-module-bluetooth that forced apt's hand when choosing which recommend of blueman to install.)
EDIT
@micko01 since you have a system using bluetooth, I wonder if you could check this out?
ie:
Uninstall bunsen-meta-bluetooth and libspa-0.2-bluetooth, confirm that (of course) your bluetooth Sony WH-CH510 headset doesn't work.
Instead of bunsen-meta-bluetooth, instead install the deps separately, leaving out pulseaudio-module-bluetooth:
bluez, blueman, bluez-cups, bluez-meshd, bluez-obexd, bluez-tools
Check whether either of libspa-0.2-bluetooth or pulseaudio-module-bluetooth has been pulled in by blueman's Recommends, and whether the headset still doesn't work.
Install libspa-0.2-bluetooth check what works, or not.
Finally purge pulseaudio-module-bluetooth if it's installed, and that everything is OK again.
Many thanks!
Last edited by johnraff (2025-04-20 05:27:02)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
^there might be a problem with your request to check..
First, the system I refer to above started out as an xfce system from the net install and has only fairly recently been morphed into a frankenstein carbon system.
Second, on my new to me laptop I did start it out as a Boron install and updated to trixie/Carbon. When I realised we are going to use pipewire
in Carbon I promptly installed it and the libspa-0.2-bluetooth
package and removed the pulseaudio-module-bluetooth
which also removed bunsen-meta-bluetooth
. However, since this started out as bunsenlabs it may work in that scenario.
I should get some time Tuesday to see what happens.
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
^No problem if you can't.
I was just wondering what would happen if we dropped both audio dependencies from bunsen-meta-bluetooth, leaving it to apt to choose which of libspa-0.2-bluetooth package and pulseaudio-module-bluetooth to install from blueman's recommends, on a system set up to use pipewire.
But anyway I think we should firmly enforce libspa-0.2-bluetooth as a dependency of the hypothetical bunsen-meta-bluetooth-pipewire along with a Breaks on pulseaudio-module-bluetooth to make sure that gets removed. It's a pity the two can't co-exist, but the wiki says to purge pulseaudio-module-bluetooth if using pipewire so I suppose there's a reason...
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Just a mention that both pipewire and bluez packages and related packages had upgrades today for me on trixie.
-edit- Here is the list from my carbon installation...
alsa-ucm-conf libatopology2t64 liburcu8t64 pipewire-bin
alsa-utils libpam-wtmpdb libwtmpdb0 pipewire-pulse
distro-info-data libpipewire-0.3-0t64 libxnnpack0.20241108 wtmpdb
htop libpipewire-0.3-modules pipewire
libasound2-data libspa-0.2-bluetooth pipewire-alsa
libasound2t64 libspa-0.2-modules pipewire-audio
I don't care what you do at home. Would you care to explain?
Offline