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.
pulseaudio is still the default, and the script still needs to be run to switch it over to pipewire.
The script presumably is "# /usr/sbin/pipewire-enable.sh" which activates the pipewire files in /etc/xdg/autostart/ and deactivates PulseAudio files there.
Question: Is is advisable to install on 15.0 the updated pipewire from Slackware-current? I see some problems fixed in the change logs, but there may be some requirements that are not met in 15.0.
Hasn't the slackware pipewire matured so much, it could be the other way round, ie pipewire default?
Would that cause any issues?
I've flip-flopped between pulseaudio and pipewire a few times in the last year or so. From what I can tell pipewire works as advertised and could be used full time. The only issues I've noticed were with some Wayland features broken if not using Pipewire (in Plasma and GNOME), and things like screen recording not working in GNOME unless pipewire is used. I would guess that as DEs move to wayland, pipewire will start being adopted more and more until it becomes a requirement.
I only know of Fedora and the latest Ubuntu going to pipewire as default, The rest including slackware still use pulseaudio as default for now. I dont have a problem with Slackware staying conservative and having pulseaudio default still. It's easy enough to switch to pipewire if a user wants to.
Quote:
Originally Posted by kevmccor
The script presumably is "# /usr/sbin/pipewire-enable.sh" which activates the pipewire files in /etc/xdg/autostart/ and deactivates PulseAudio files there.
Yes thats the one that we were talking about. There's also a second one to switch it back to pulseaudio.
Quote:
Originally Posted by kevmccor
Question: Is is advisable to install on 15.0 the updated pipewire from Slackware-current? I see some problems fixed in the change logs, but there may be some requirements that are not met in 15.0.
I cant say for sure because I haven't been paying too much attention to current since 15.0 came out. I'm not sure what libraries pipewire is compiled against but if those underlying libs changed in current too then installing binaries from -current might lead to unforseen issues.
If I were to try to install a newer pipewire version from current I would use the SlackBuilds from the source/ directory in current and compile them on 15.0 so they are built against that system's libraries.
The script presumably is "# /usr/sbin/pipewire-enable.sh" which activates the pipewire files in /etc/xdg/autostart/ and deactivates PulseAudio files there.
Question: Is is advisable to install on 15.0 the updated pipewire from Slackware-current? I see some problems fixed in the change logs, but there may be some requirements that are not met in 15.0.
The updated pipewire from Slackware-current http://dfw.mirror.rackspace.com/slac...ce/l/pipewire/ can be downloaded from any mirror of Slackware-current, under /source/l/pipewire. Download the files to a folder and run the slackbuild (# ./pipewire.Slackbuild then # upgradepkg /tmp/pipewire...). It seems to work fine with my Slackware-15.0. I was able to use my new headphones and the microphone with zoom-linux.
With those symlinks in place, you can remove the /etc/asound.conf file (or maybe just copy /usr/share/alsa/alsa.conf.d/99-pipewire-default.conf in its place), and pipewire becomes the default system in use with ALSA.
- Support masking of conf.d/ files. (#2629)
- Use org.freedesktop.portal.Realtime when available. This does the correct PID/TID
mappings to make realtime also work from flatpaks.
- Fix rate adjustement logic in pulse-tunnel. This would cause increasing delays and
hickups when using tunnels. (#2548)
- Add OPUS as a new vendor codec. Add OPUS-A2DP spec. PipeWire can now send and reveive
OPUS data over bluetooth.
- An AAC decoder was added so that PipeWire can now also function as an A2DP AAC receiver.
- Fix some issues where the wrong samplerate was used. (#2614)
- Fix rate match for sources. This fixes an error where follower sources would generate
many resync warnings.
- Many more bugfixes and improvements.
- Fix a regression that could cause audio crackling.
- Fix a regression in RTKit because rlimit was not set correctly.
- JAVA sound applications will now alsa work with the pulseaudio-alsa plugin.
- pw-top will now show the negotiated formats of devices and streams.
- Fix some potential crashes when starting streams.
- The ALSA plugin has had improved timing reporting and poll descriptor handling that should improve compatibility.
- Many more improvements and bugfixes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
