Posts by Ryan Kanarek

    Use the "fader<fadertype>" keyword to set the desired level on the fadertype you want. For example, "FaderMaster Exec 201 At 0". As playback is owned by the sequence now and not the executor, you can use the same keywords directly on sequences:

    • FaderMaster Sequence 1 At 100
    • FaderTemp Sequence 1 At 50

    ...and so forth.


    Also, Exec 1.201 would be the 201st child of Exec 1. In grandMA3, x.y is always the "yth" child of object "x". Executors are children of Page objects, so if you want to specify exec 201 on page 1, you would either say "Page 1 Exec 201" or simplify with "Page 1.201".

    Snap could be done with a Step-Width of 0 and/or a Step-Transition of 0 (depending on what you wanted to have happen after that).


    So for example:

    1. Fixtures to full
    2. Change to Step 2
    3. Fixtures to zero
    4. Change back to Step 1 and set the Width to 0
      • (Optionally change the Transition to 0 and adjust the Width to find the desired time for the lights to stay at full before fading down)
    5. Adjust Speed and Phase as desired

    I'm curious for what you're using additional screenconfigs beyond Default and 3D? The general purpose for this feature is so that you can have a programming station and a previz station logged into the same user but that won't change views on the previz station (presumably away from the 3D window) when you change views on the programming station. All screenconfigs of the same userprofile still reference the same View Pool, so perhaps you're changing the views on a station or user with a different screenconfig and then seeing the result of those changes in the other user?

    This is normal, and is no different from how Input Filters or PresetFilter work on grandMA2. An Input Filter changes what you can add or modify moving forward, not what is already in the object. Otherwise what would be the point of being able to temporarily turn off PresetFilter in gMA2? Changing or applying an Input Filter to a Preset or Preset Pool in gMA3 is essentially applying a custom PresetFilter (in gMA2 terminology) to that Preset or Preset Pool.

    There's a ProgParts window you can open (bottom of the 2nd column in the "More" tab) which allows you to manage this stuff manually. And yes, there's a bug that ClearAll doesn't get rid of empty programmer parts.

    You don't use the MA3 software to link an OSC message to a particular action. Rather, the OSC message itself defines what it is triggering.

    If you use Groups, Blocks, or Wings, fixtures can overlap each other in the same grid-space. Right now, when that happens the numbers overlap each other rather than being listed (or some other possible solution). Is the numbering actually wrong or are you just seeing the numbers being overlaid on top of each other?

    Which encoders are you talking about in this case? Inner encoder of the dual encoders? Outer encoder button? Rotary knobs?


    In regards to Temp Buttons, yes they turn off the sequence when you unpress the button. What is the result that you want or were expecting to happen?

    I think I can see what you're saying. What it looks like to me is that the cue remembers from which sequence's settings it was created. Because if you take your scenario a step further and say:

    • 1 Thru At 50
    • Store Sequ 2 Cue 3 /merge
    • Look at the Tracking Sheet

    You get the opposite result (dimmer 1 is still in the programmer instead of dimmer 2). So it's remembering that cue 2 was created with World 2 as the input filter and cue 3 was created with World 3 as the input filter, even though you're now attempting to merge data into them from the sequence with the opposite input filter.