>GStreamer is intended to be a swiss army knife of multimedia, PipeWire is meant to be much lower level, more like what alsa-lib, JACK or libv4l2 provides.

https://github.com/PipeWire/pipewire/wiki/FAQ#is-pipewire-ju...

>PipeWire is a project that aims to greatly improve handling of audio and video under Linux. It aims to support the usecases currently handled by both PulseAudio and Jack and at the same time provide same level of powerful handling of Video input and output. It also introduces a security model that makes interacting with audio and video devices from containerized applications easy, with supporting Flatpak applications being the primary goal. Alongside Wayland and Flatpak we expect PipeWire to provide a core building block for the future of Linux application development.

https://pipewire.org/

I'd be happy if Pipewire doesn't constantly burn CPU the way Pulseaudio likes to, even when no sound is playing. It always annoys me to see Pulseaudio in top, burning 5-10% of the CPU with thousands of hours of CPU time built up.

I've not seen this in the decade of running it on dozens of machines. So chances are there is a bug somewhere related to your hardware or mixer configuration.

Maybe, but nothing I've ever tried has worked and I'm not the only one:

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/20...

https://ubuntuforums.org/showthread.php?t=2215353

I don't see anyone tracking down what PCM format was written to pulse vs what format the pulse daemon had to write to the driver to determine if format conversion was necessary. Needless to say, the gstreamer->pulse support has changed greatly since 2008.

But as it were, profiling my system (Fedora 30) with Sysprof to look at where time is spent:

  - Roughly about 2% CPU amortized across all cores at idle, but playing an MP3 in rythmbox (so includes shell, rhythmbox, a webbrowser, etc)
  - Of that 2%, 7% (so .14%) of that time was spent in the pulse daemon
  - .04% (2% of 2%) was spent in libspeexdsp.so and all other samples were negligible

If you're still having problems today on your system, I highly suggest running sysprof (or perf even) to get a quick high-level overview of where time is spent.

It's practically one comment each year in the last five years, doesn't look like a widespread problem.

I've had the issue (Ubuntu with VM). I think I switched to ALSA, or just disabled sound. On Linux when I "fix" a problem I very rarely write a comment on a forum...