Been wondering for weeks why #Pipewire needed that much CPU and “lost” the sinks on occasion. Turns out that the media-session was started twice due to a leftover from my fiddlings in /etc/pipewire/pipewire.conf. Two different pids in journal should have given this away. Thanks Peter for not pulling a #DenverCoder9 here https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1969#note_1205730 😀