Using Pipewire instead of Pulseaudio in Slackware 15
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
SBo is the abbreviation for SlackBuilds.org but I don't see pipewire on there, just something that uses pipewire... what exactly do you mean? Is someone going to write this up on docs.slackware.com ?
Neither me or ZhaoLin1457 (from what I known) have uploaded ever something related to PipeWire in the SBo - probably some typo of OP.
I for one, I believe that it's moot to nitpick about what was discussed at the beginning of this thread...
Heck, it was a Work In Progress and experiments done long before Slackware 15.0 was released.
You know, this thread has 30 pages with a reason.
Meanwhile, there is an official way to handle the switching between PulseAudio and PipeWire, and it was included since Slackware 15.0 and I for one I believe that makes no sense to have something related to PipeWire setup in the SBo, because PipeWire is part of Slackware.
Last edited by LuckyCyborg; 04-22-2023 at 06:34 AM.
I also use this abbreviation sometimes. It simply means SlackBuild
I know it can be confusing, but it's easy to make the correction by yourself to understand the meaning
Saw that.
Good of you to take the time to reply.
My mind is getting a little fuzzy in my old age, but that change log entry doesn't answer the question.
Thanks, again.
It is a different implementation of it that doesn't use lua, and is incorporated in the pipewire package!
What benefit would I get from switching to Pipewire? My hearing is terrible, I wear hearing aids. I am not an audiophile. I do not use Wayland. I am thinking that eventually this will become standard in Slackware and should just wait it out.
What benefit would I get from switching to Pipewire? My hearing is terrible, I wear hearing aids. I am not an audiophile. I do not use Wayland. I am thinking that eventually this will become standard in Slackware and should just wait it out.
After all, compared with the PulseAudio, the PipeWire works much better with the Bluetooth audio devices.
In fact, this is the main reason WHY personally I have switched to using PipeWire (also) as audio server.
Initially, at least I for one, I tried to bring up the PipeWire daemons for the video side only, as support for Wayland/Plasma5.
And I used it this way long time. But in the end, the PipeWire convinced me regarding its performances also as audio server.
PS. I am NOT an audiophile, too...
My typical speakers are that kind bought with $5 the pair, and powered via USB. And the most advanced audio devices I have are Bluetooth headphones, not necessary chosen for their HiFi performances.
For me it's all good if the sound is clear with NO squeaks, barks, barfs and other things like this.
Last edited by LuckyCyborg; 04-23-2023 at 03:15 AM.
After all, compared with the PulseAudio, the PipeWire works much better with the Bluetooth audio devices.
In fact, this is the main reason WHY personally I have switched to using PipeWire (also) as audio server.
Initially, at least I for one, I tried to bring up the PipeWire daemons for the video side only, as support for Wayland/Plasma5.
And I used it this way long time. But in the end, the PipeWire convinced me regarding its performances also as audio server.
PS. I am NOT an audiophile, too...
My typical speakers are that kind bought with $5 the pair, and powered via USB. And the most advanced audio devices I have are Bluetooth headphones, not necessary chosen for their HiFi performances.
For me it's all good if the sound is clear with NO squeaks, barks, barfs and other things like this.
HeHe, my speakers are cheap ones too, plugged in to the audio jack on the motherboard. No Bluetooth though, my desktop doesn't have that capability. Thanks for you input!
HeHe, my speakers are cheap ones too, plugged in to the audio jack on the motherboard. No Bluetooth though, my desktop doesn't have that capability. Thanks for you input!
BTW, you can add the Bluetooth support to any computer, because there are very cheap USB dongles for Bluetooth. And at least in my country, their price starts with approx. $1.
Honestly, this is the way I do the bluetooth-ification of my computers, unless I chose to use USB dongles which sports both WiFi and Bluetooth. The really low end (and really cheaper) ones, with WiFi N at 150Mbps and Bluetooth 4.0 are sold for approx. $5 here.
Last edited by LuckyCyborg; 04-23-2023 at 04:15 AM.
BTW, you can add the Bluetooth support to any computer, because there are very cheap USB dongles for Bluetooth. And at least in my country, their price starts with approx. $1.
Honestly, this is the way I do the bluetooth-ification of my computers, unless I chose to use USB dongles which sports both WiFi and Bluetooth. The really low end (and really cheaper) ones, with WiFi N at 150Mbps and Bluetooth 4.0 are sold for approx. $5 here.
That's an idea I hadn't thought of. Will have to check it out. Thanks.
Well, after using Pipewire for about a week, the good news is that the disable script provides instructions for shutting down pipewire and getting back to "normal" after a reboot. PulseAudio is more reliable, despite its sputtering and poettering.
Well, after using Pipewire for about a week, the good news is that the disable script provides instructions for shutting down pipewire and getting back to "normal" after a reboot. PulseAudio is more reliable, despite its sputtering and poettering.
I use Pipewire since Zhaolin & LuckyCyborg provide the "how-to" and its inclusion in Slackware
I use Wireplumber for more than a year
With 5 or 6 bluetooth sound devices and in a Full wayland session
Without any noticeable issue
Please, do not confuse "works better here" with "more reliable"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.