pipewire...-manager(7)
π NAME π
okay so bestie, listen up β pipewire-pulse-module-device-manager is the Device manager extension. that's the whole vibe. it manages devices. it's the girlboss of your audio pipeline π
β¨
π MODULE NAME π
the icon herself:
module-device-manager
load her up and she'll be out here doing device management things like it's nothing π¦
β¨ MODULE OPTIONS β¨
these are the lil knobs you can turn, and ngl they all end in question marks because they're genuinely questions the module asks itself, which is so real of it:
do_routingβ should streams get automatically routed based on a priority list? and bestie, that priority list is unique per-role, so every role gets its own little ranking, no cap πon_hotplugβ when a new device becomes available, should we recheck streams? like a new device just pulled up, do we do a whole vibe check on everything? πΈon_rescueβ when a device becomes unavailable, should we recheck streams? she's gone π do we save the streams or just let them fend for themselves? π«Ά
fr fr that's the entire page β three options, one module, zero filler. sometimes the manual page is short and that's iconic behavior π
okay sending you off with the receipts π this was the pipewire...-manager(7) page, sittin' in the Miscellaneous Information Manual, brought to you by PipeWire 1.6.11 β mwah, love that for us β¨π
π¦ where this page comes from
- fedora 44: pipewire-pulseaudio 1.6.11-1.fc44 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms