1. 11
  1. 5

    From what I understand, PipeWire is a ‘frontend’ to ALSA, Pulseaudio, Jack. If that’s right, them I’m really wary of adding yet another layer of abstraction to audio setup on Linux, where Pulseaudio already tries (sometimes unsuccessfully) to abstract ALSA, etc. Debugging when configurations go wrong is already a frustrating experience without adding yet another layer of complexity on top of it all. I hope I’m wrong.

    1. 3

      From what I understand, PipeWire is a ‘frontend’ to ALSA, Pulseaudio, Jack.

      I don’t think so:

      PipeWire sits right on top of the kernel drivers (or as close as possible). You can think of it as a multimedia routing layer on top of the drivers that applications and libraries can use.

      https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ

      PipeWire implements ALSA, PulseAudio and Jack APIs so that applications that use these APIs can use PipeWire:

      https://gitlab.freedesktop.org/pipewire/pipewire/-/tree/master/pipewire-alsa

      https://gitlab.freedesktop.org/pipewire/pipewire/-/tree/master/pipewire-pulseaudio

      https://gitlab.freedesktop.org/pipewire/pipewire/-/tree/master/pipewire-jack