Hi Ralf, did you try out what is happening if you turn off "off when overwritten" and keep "auto stomp" turned on? That seems to me that it could have the right behaviour...
In my opinion this is the expected behavior. If you pull up the Top sequence with Auto Stop activated, the sequence Relative Circle turns off, because ALL of its attributes are overwritten with a Stomp: "Off when Overridden" If you merge more (color) attributes into it, it does not, because NOT ALL of its attributes are overridden. Instead of adding another attribute you could also deactivate "Off when Overridden" for preventing this sequence from being turned off by the Top sequence.
I agree that what you're describing is what we're seeing and it also makes sense. It is just not clear in the documentation and inconsistent in the implementation. I understand it's a subtle detail but those subtle details matter to intuition and cognitive overhead. In essence, Auto Stomp and Off when Overridden should probably be mutually exclusive. Stomping a Phaser while also completely turning off the Cue doesn't really make that much sense, since off-ing the Cue implicitly stops any Phaser contained in any of its Cues. Also: Even with Off when Overridden turned on for the Relative Circle Sequence, overriding all of its Attributes with the Top Cue, does not (!) off the Relative Circle Sequence. So while I agree, the implemented behavior is likely exactly what we want in many lighting situations, it is not what is described in the docs nor what the user interface indicates.
@@r2.lighting Yeah I agree. I am new, and a lot of my scenes I put on execs rather than faders to quickly activate them, and I need them to turn off when I activate a different one. I finally figured out that having both auto stomp and off when overwritten enabled achieves this.
Hi Ralf, did you try out what is happening if you turn off "off when overwritten" and keep "auto stomp" turned on?
That seems to me that it could have the right behaviour...
In my opinion this is the expected behavior.
If you pull up the Top sequence with Auto Stop activated, the sequence Relative Circle turns off, because ALL of its attributes are overwritten with a Stomp: "Off when Overridden"
If you merge more (color) attributes into it, it does not, because NOT ALL of its attributes are overridden. Instead of adding another attribute you could also deactivate "Off when Overridden" for preventing this sequence from being turned off by the Top sequence.
I agree that what you're describing is what we're seeing and it also makes sense. It is just not clear in the documentation and inconsistent in the implementation. I understand it's a subtle detail but those subtle details matter to intuition and cognitive overhead. In essence, Auto Stomp and Off when Overridden should probably be mutually exclusive. Stomping a Phaser while also completely turning off the Cue doesn't really make that much sense, since off-ing the Cue implicitly stops any Phaser contained in any of its Cues. Also: Even with Off when Overridden turned on for the Relative Circle Sequence, overriding all of its Attributes with the Top Cue, does not (!) off the Relative Circle Sequence. So while I agree, the implemented behavior is likely exactly what we want in many lighting situations, it is not what is described in the docs nor what the user interface indicates.
@@r2.lighting Yeah I agree. I am new, and a lot of my scenes I put on execs rather than faders to quickly activate them, and I need them to turn off when I activate a different one. I finally figured out that having both auto stomp and off when overwritten enabled achieves this.