Morrolinux: PipeWire and the Future of Linux Audio

The free and open source world of graphics has long been considering a shift I discussed in my video on Wayland, “the next big revolution on Linux.” That change has now happened, and most users have moved away from Xorg. But while Wayland has dominated the conversation, another shift has been taking place behind the scenes: PipeWire, a rethinking of how Linux manages audio and video.

If you’ve ever struggled with PulseAudio or JACK, you’ll appreciate what this means. PipeWire promises to unify both, delivering professional-level performance with everyday simplicity. Let’s see how it works and why it’s fast becoming the new standard across Linux systems.

The Long Road to Modern Audio

Linux sound started with OSS, the Open Sound System. It gave applications direct access to /dev/dsp and /dev/audio, but it allowed only one stream at a time: no mixing, no per-app control.

ALSA, the Advanced Linux Sound Architecture, solved part of that. It introduced libraries, multi-device support, and plugins, but remained close to the hardware. One app could still block the others.

To fix that, developers built sound servers: software layers that manage all audio streams for multiple applications.

PulseAudio, JACK, and the Split World

Two sound servers became dominant. PulseAudio focused on user experience (easy volume control, Bluetooth integration, and wide desktop support). JACK targeted professionals with low latency, patch-bay routing, and modular flexibility.

PulseAudio made things simple; JACK made them powerful. But Linux users had to choose between convenience and control. The ecosystem split in two.

What PipeWire Changes

PipeWire began in 2015 as “PulseVideo,” aiming to unify Linux’s handling of audio and video. The project has since evolved into a modular framework that blends the strengths of PulseAudio and JACK under one roof.

Think of PipeWire as a dynamic graph: each node is a client (such as Firefox, Ardour, or your webcam). Each port is an input or output. The lines connecting them define how audio and video move through the system.

Behind the scenes, a central daemon speaks a native PipeWire protocol over a Unix socket, wrapping messages from ALSA, PulseAudio, and JACK clients alike. This is why PipeWire works as a drop-in replacement: you install it, and existing apps just run.

WirePlumber: The Conductor Behind the Scenes

PipeWire’s core doesn’t decide how things connect; that’s the job of the session manager. Today, the session manager is almost always WirePlumber.

WirePlumber listens for new devices and builds the connection graph dynamically. Plug in Bluetooth headphones, and it automatically reroutes your audio output. Disconnect them, and the graph collapses back.

WirePlumber also introduces per-client permissions: a more secure model than PulseAudio’s “everything goes” approach or JACK’s open environment.

Portals and Secure Access

Because PipeWire also handles cameras and screen capture, sandboxed apps (like those packaged in Flatpak) need a way to request access safely.

Enter portals: secure bridges between applications and system resources. When Firefox asks for webcam access, it goes through the portal, which mediates between the browser and PipeWire. The same mechanism enables screen sharing under Wayland.

The result is better privacy, clearer permission management, and less guesswork when multiple applications need the same device.

Where It Stands

PipeWire is now the default on most major distributions (Fedora since version 34, Ubuntu since 22.10) and its adoption is growing.

Still, not everything is perfect. WirePlumber remains the only fully maintained session manager, and video handling still depends on each compositor’s implementation. Yet progress is steady, and the ecosystem is maturing quickly.

PipeWire represents something rare in the Linux world: a project that could genuinely unify rather than fragment.

Explore Further

Watch the full breakdown in Italian:
“Come funziona PipeWire, la prossima rivoluzione su Linux”
https://www.youtube.com/watch?v=h8ydMSqNwUg

More technical notes and demos are available at: https://kb.morrolinux.ovh/books/linux

Follow Moreno “Morrolinux” Razzoli on LinkedIn, X, or Telegram for more open source insights and tutorials.

<< Read the previous article of this series