[dijit]

This is me learning that pipewire is a RH project.

For context as to why it's not getting hate: the alternative is Pulseaudio (another RH project, headed by Poettering who is now at Microsoft incidentally) which was eggergiously difficult to configure, heavy and seemed to dominate any system that tried to interface with it even slightly.

The same exact concerns that people levy towards systemd and GNOME.

Pipewire is light, interfaces with programs on their terms and seems to follow the philosophy that "it's just a tool" meaning that it should not be something you have to care about as an application developer or as a user.

I have a lot of respect for that.

[isolatedsystem]

Pipewire also worked out of the box for me, and abstracts away ALSA and PulseAudio. It can even handle JACK. It's very nice.

[thomastjeffery]

I didn't even know it existed until the other day when I found out I was already using it.

I can't imagine giving better praise for a piece of software.

[andrewaylett]

Pulseaudio was adopted too early, and I think distros have learned their lesson this time around.

Honestly, it fell under "just worked" for me. One time I had been reading about PA using too much CPU, so I checked and indeed it was using a reasonable amount of processing power "just" to feed data from the media player to ALSA. So I tried turning it off, and the media player used more CPU to play audio direct to ALSA without PA than both the media player and PA running together.

[bayindirh]

I had tons of problems with PA. Jitter, noise, insensible defaults. i.e. Why upmix stereo to 5.1 just because I have the speakers, and why make disabling it an override?

I never used onboard audio, always had some higher end card with more resolution than a bog standard on board audio chip, and PA struggled to deal with them for a long time.

Also if the daemon crashed or needed a restart, it was a dance of restarting with exacting order and other details.

Pipewire is just invisible. It works the way it should and doesn't bend the system to fit in.

[andrewaylett]

Pipewire is invisible because Pulseaudio (PA) exercised a lot of sound stack features, exposing bugs (which were often attributed to PA) and prompting a lot of bug fixes. It wouldn't be nearly as good if it weren't building on PA's foundations.

Pipewire also doesn't need to bend the system to fit in, because the system is already the right shape.

(And I'm perennially annoyed that my work Mac won't upmix to 5.1. I've got the speakers, why only use two of them?)

[bayindirh]

I need to read the ALSA bugfixes because of PA to see and believe that.

On the other hand, I used multichannel audio since the last 20 years or so, on Linux, and it always worked with what I have. First with Live and Audigy, then with an Asus card.

No, pipewire is much more gentle on how it handles and takes the streams from other applications. It doesn't make an heavy-handed attempt to make it is also replacing ALSA and drivers at the same time. It's a much thinner layer and works what it should do. Most importantly it doesn't alter the streams it goes through it.

(Sorry, but upmixing a good stereo sound source to 5.1 is just butchering the sound. The resulting sound stage is an abomination of what it should be. For a musically inclined person (read: ex-orchestra player), it's just torture. It's so wrong on so many levels.)

[tristan957]

GNOME Shell uses 0.75% of my CPU and 136 MB of memory. All processes in gnome-system-moniotr that are somehow related to GNOME clock in around 400-500 MB of memory. How is that heavy?