Auto Stomp: Difficulties understanding it precisely

BECOME PART OF THE COMMUNITY - Sign up here

    I seem to not understand Auto Stomp somehow. From the MA documentation: If auto stomp is On, then an absolute value from a cue will stomp a phaser running from a different playback.


    Isn't that the default behaviour, anyway? Attached is a screen recording. In Seq. 1 I have a cue Circle Move. When activated, a circle phaser runs. In Seq. 3 is a static Position Top cue. In the Circle Move sequences Auto Stomp is active and the sequence settings have Off when Overridden switched off.


    According to the documentation, this should mean that the moment my Position Top cue is activated, the phaser coming from the Circle Move cue will be stomped automatically. But that's not the case. Why?


    And: Would it be correct to state that Auto Stomp only make sense combined with If Off when Overridden being not active. Otherwise, the running cue would be offed automatically, anyway, once the attributes get overwritten by another cue, so it wouldn't even require an Auto Stomp. Is this correct?


    Recording: https://rottmann.io/corectomy-…-nonrecognized-overeating

    I have watched this video and for me it shows the exact expected behavior.


    In the first example (around the 5:45 mark) Off On Overwritten has no affect because you have no relative data in the Top cue to Overwrite the Relative cue.


    Only when you add Auto Stomp is the Relative movement halted because it is stomped.

    Likewise now that the Relative sequence has no data being output to the stage it is turned off. This also makes sense.


    Only once you add extra information to the relative cue (the colour) is the combined action of the two functions seen (movement stops but sequence stays on) because the Relative sequence is still outputting to the stage.


    This all seems very logical and expected behavior to me.

    Yap. That's why I said it all makes sense, it's just partially confusing and the documentation could need a lot more clarity.


    For example, the fact, that Auto Stomp doesn't work at all with absolute values, is an omission and makes it harder to grasp.

    Autostomp is kind of irrelevant for absolute values because you are replacing the absolute phaser data with you new absolute cue data so by the usual LTP principles the phaser will be stopped. So it's not so much it doesn't work with absolute values but more that it's irrelevant with absolute values.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login