Describe the bug
Pipewire's node.passive property has changed behaviour in their master branch (currently unreleased) and its value true should become follow to retain the same behaviour in cava.
It should be a pretty simple change just this one line
|
pw_properties_set(props, PW_KEY_NODE_PASSIVE, "true"); |
But I know you are busy making changes so I didn't want to interfere with a PR. This is a future change so I'm mostly just trying to let you know in advance.
I imagine that when this change is released, there will be some time between that release and the subsequent cava release with the fix discussed here, so following is a workaround which cava users can employ in that migration period:
Just create a text file ~/.config/pipewire/pipewire.conf.d/cava_passive_fix.conf
With these contents:
node.rules = [
{ matches = [ { node.name = "cava"
node.passive = true
} ] actions = { update-props = {
node.passive = follow
} } }
]
To Reproduce
Steps to reproduce the behavior:
- Use pipewire built from git master
- Use cava with active=0
Expected behavior
Cava should become inactive (idle, then suspended) when linked to an inactive source
Additional context
Upstream bug (including discussion of cava)
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5152#note_3362157
Describe the bug
Pipewire's
node.passiveproperty has changed behaviour in their master branch (currently unreleased) and its valuetrueshould becomefollowto retain the same behaviour in cava.It should be a pretty simple change just this one line
cava/input/pipewire.c
Line 185 in 01bdbd5
But I know you are busy making changes so I didn't want to interfere with a PR. This is a future change so I'm mostly just trying to let you know in advance.
I imagine that when this change is released, there will be some time between that release and the subsequent cava release with the fix discussed here, so following is a workaround which cava users can employ in that migration period:
Just create a text file
~/.config/pipewire/pipewire.conf.d/cava_passive_fix.confWith these contents:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Cava should become inactive (idle, then suspended) when linked to an inactive source
Additional context
Upstream bug (including discussion of cava)
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5152#note_3362157