mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2026-03-09 05:34:03 -04:00
118d8574c8
Add a port.passive = follow mode and the node.passive equivalents out-follow, in-follow, follow. This makes it possible to control how a port influences the state of the peer and how the peer influences the state of the node independently. In passive mode, the port will not make the peer runnable and will also not become runnable when the peer activates. In the follow mode, the port will not make the peer runnable but it will become runnable when the peer is active. This makes it possible to do new things like (f for follow): Source -> (f)loopback1-in|loopback1-out(f) -> Sink It will not make the source and sink run but when one of them start, all will become runnable. Or you can now better do the leak node hack that was previously used: Source -> (f)pw-record That will only start running when the source is activated by something else. With port.passive = true|false|follow there is a potential 4th case which would activate the peer but not be activated by the peer, which is not something that makes sense. |
||
|---|---|---|
| .. | ||
| index.md | ||
| libpipewire-modules.7.md | ||
| pipewire-client.conf.5.md | ||
| pipewire-filter-chain.conf.5.md | ||
| pipewire-jack.conf.5.md | ||
| pipewire-props.7.md | ||
| pipewire-pulse-modules.7.md | ||
| pipewire-pulse.conf.5.md | ||
| pipewire.conf.5.md | ||
| xref.md | ||