Macro for activating/highlighting current absolute or relative values only.

BECOME PART OF THE COMMUNITY - Sign up here
  • Goal: being able to save current "static" values to an executor while having phasers running.

    Reason: For busking liveshows, Having an executor running as a "deafult"


    Simple example:

    Running = relative Pan/Tilt phasers.

    Static = absolute position.


    Methods tried:


    -Series of selecting and toggling encoder pages.

    Like this

    1: clearactive (for starting the same every time)

    2: clearselection (for starting the same every time)

    3: group ###

    4: relative

    5: select encoderpage 2

    6: toggle encoderpage 2

    7: toggle encoderpage 2

    8: toggle encoderpage 2

    9: store sequence ### /merge


    This doesn't work reliably and wont toggle attributes previously activated by a preset, and for some reason will give no outputs at all from time to time,

    This also works different from manually giving the inputs through a touchscreen.


    -Attribute toggling

    Like this

    1: clearactive (for starting the same every time)

    2: clearselection (for starting the same every time)

    3: group ###

    4: on Absolute attribute 2

    5: on Absolute attribute 3

    6: store sequence ### /merge


    This one got me excited, until I tried it. Turns out if no preset to associated attribute is activated, then this will sometimes send attributes to deafult, and will sometimes activate the entire attribute group. Its the same with the "toggle" Keyword.


    Help would be greatly appreciated!

  • Instead of having an executor as "default", you could merely use the actual Default as store destination, as this store destination automatically only takes the static absolute values



    Group xxx

    On FeatureGroup 2

    Store Default /Merge

  • Thanks for the response! That's a great point, and I will be using that in the future!


    Unfortunately, "on featuregroup #" will start an entirely new phaser with default speed, if you have a running phaser going.

  • You are right, if the phaser is running from a playback with a different masterspeed than the programmerspeed, then activating the phaser will alter the outputspeed.


    Assuming your programmer originally is empty, maybe using Blind could workaround the issue:


    Group xxx

    Blind On

    On FeatureGroup 2

    Store Default /Merge

    Off FeatureGroup 2

    Blind Off