Is your feature request related to a problem? Please describe.
I have a scene set up which powers on my
- Audio Interface
- Sound Mixer
- Loudspeakers
in this exact order with delays, to avoid the loudspeakers from playing a loud sound when the mixer turns on:
When I turn off the scene, the order remains the same, which causes a THONK! to be played when the interface/mixer turn off, since the loudspeakers are still powered on (and will be for a few more seconds)
Describe the solution you'd like
I would like to have an additional switch per scene that allows me to reverse the order of state updates if ticked.
This switch should only be visible in case the existing Set value if false is enabled.
Describe alternatives you've considered
None; So far I just accepted that I hurt my loudspeakers a little when turning them off.
I guess one could build a dedicated scene for turning off the devices, but then one would have to maintain two different scenes that control the same devices.
Additional context
I would be happy to raise a PR to introduce this feature, including unit tests to verify existing behaviour is not changed.
Last time (It's been a while!) I looked at the code I remember the scene progression is implemented via recursion, which might be non-trivial to reverse.
Cheers
Olli
Is your feature request related to a problem? Please describe.
I have a scene set up which powers on my
in this exact order with delays, to avoid the loudspeakers from playing a loud sound when the mixer turns on:
When I turn off the scene, the order remains the same, which causes a THONK! to be played when the interface/mixer turn off, since the loudspeakers are still powered on (and will be for a few more seconds)
Describe the solution you'd like
I would like to have an additional switch per scene that allows me to reverse the order of state updates if ticked.
This switch should only be visible in case the existing
Set value if falseis enabled.Describe alternatives you've considered
None; So far I just accepted that I hurt my loudspeakers a little when turning them off.
I guess one could build a dedicated scene for turning off the devices, but then one would have to maintain two different scenes that control the same devices.
Additional context
I would be happy to raise a PR to introduce this feature, including unit tests to verify existing behaviour is not changed.
Last time (It's been a while!) I looked at the code I remember the scene progression is implemented via recursion, which might be non-trivial to reverse.
Cheers
Olli