Today I finally switched one of my Linux/KDE systems from classic PulseAudio to PipeWire — and honestly… this is the first time Linux audio suddenly made visual sense.
I opened qpwgraph and immediately saw my entire live audio topology:
microphones
browser streams
speakers
monitor channels
MIDI devices
USB capture devices
…and suddenly debugging audio became almost fun.
At first I only saw MIDI nodes and thought something was broken:
14:Midi Through
Midi-Bridge
Turns out my system was still running classic PulseAudio:
pactl info
showed:
Server Name: pulseaudio
After migrating to PipeWire, everything appeared dynamically in the graph.
Now when Firefox opens a tab or requests microphone access, I literally see the stream appear live inside the graph.
Very funny moment:
I instantly noticed:
browser audio routed to the wrong output
microphone permissions failing
applications using unexpected devices
This is the kind of visibility Linux audio was missing for years.
Installation (Debian/KDE)
execute as root
apt install pipewire pipewire-pulse wireplumber qpwgraph pavucontrol
Then disable old PulseAudio:
systemctl --user --now disable pulseaudio.service pulseaudio.socket
Enable PipeWire:
systemctl --user --now enable pipewire pipewire-pulse wireplumber
Restart user session or reboot.
Verify:
pactl info
Expected result:
Server Name: PulseAudio (on PipeWire ...)
Then launch:
qpwgraph
Screenshot
“This is where Linux suddenly becomes a modular audio laboratory.”
(Insert screenshot here)
What I really like:
graphical patching of audio streams
live visibility of browser/device routing
JACK-style workflows without pain
debugging WebRTC/microphone issues visually
OBS + browser + USB devices all in one graph
Honestly impressive how far Linux audio has evolved.
Top comments (0)