Let's start it and call for help
That's how open-source projects work anyway

Some guys here will probably be glad to contribute ;-)

1 members found this post helpful.

I used pipewire for a few days. It is quite easily uninstalled, which I found to be its greatest feature.

Since there is some info for pulseaudio, see https://docs.slackware.com/pulseaudi...h&q=pulseaudio i think that the question for a similar article for pipewire, is valid.
(and yes, Slackware 15.1 is expected to ship with grub as a default with a new type of generic kernel, thus no initrd needed thus more ideas for updating the docs)

This documentation is obsolete since the inclusion of pulseaudio in Slackware 14.2 in 2016

Yes. In fact, the transition to pulseaudio as default, is mentioned there https://docs.slackware.com/howtos:multimediaulseaudio_non-default
Over the years, i have found the docs.slackware to be a very very helpful site of reference and source of info, side by side to this forum. (but of course, a wiki and a forum are different things)

A few months ago, I was trying to find a post I had made in a thread on this forum, with some information I needed in it. I just couldn't find it, I tried everything, looking through a bunch of threads and posts, but I never found it. Again a few days ago I needed to find that same info, and by a stroke of luck, I actually found it.

Both a forum and docs have their uses, which supplement each other. Quite alot of people want to make slackdocs be one of those good sources of (Slackware) GNU/Linux information, and quite alot of people have put effort into that as well. It's not a dead cause by any means, and Slackware as a distro is kind of unique in that it often offers distro agnostic methods. I'd encourage as many to contribute as possible, any day.

1 members found this post helpful.

In my view Slackware was forced to "upgrade" to pulseaudio by a combination of Bluetooth and numerous applications, especially Firefox, wishing to offload any responsibility for audio and just let Pulse "wave the conductor's wand". I used that analogous reference because it is rather typical of Lennart Poettering's admiration of Apple OSX to use containers everywhere controlled by an all-powerful server to create a hand-holding userland experience like Apple and Microsoft. In his defense, pulseaudio does that reasonably well for those to whom audio is insignificant, commonly accepting the noise and latency penalties that are inherent to onboard audio chips and pulse. Since RedHat devs were expecting the IBM buyout that would benefit rapid deployment to workstations this has worked quite well for that environment.

However pulse complicated audio performance where audio is more important than simple Workstation environments require. Pipewire has been called "Pulseaudio 2.0" for good reason. It is already substantially superior to Pulseaudio in both the workstation environment and with excellent tradeoffs that benefit serious audio work including recording and editing and by even incorporating video controls and integration opens up the market for professional film-making and editing. For the more casual desktop user Pipewire simply sounds better and handles automation better but is less resistant to the desires and needs of the more serious audiophile.

Note: The Pipewire version on Slackware Current, o.3.84, is a very substantial improvement over version 0.3.44 in Slackware 15.0. Some are calling the previous 0.3.81 essentially Pipewire RC1.0. You can see a nice breakdown changelog here

https://www.reddit.com/r/linux/comme...0_rc_released/

4 members found this post helpful.