Posts by Ryan Kanarek

    The "ListRef" keyword (MA+List) works with basically any object: ListRef Appearance 10


    Seems that fixtures inside an object isn't an object reference (makes sense), so that won't work for your second example.

    The Magic workflow changed:

    • The MAgic layer was renamed to GridPos.
    • The MAgic values (now GridPos values) are now always activated automatically when entering attribute values or if calling presets. Therefore, they are automatically part of a preset when a preset will be stored.
    • With the automatic creation of the MAgic values (now GridPos values) on the GridPos layer, it is now possible to have different GridPos values for different attributes of the same fixture which expands the creativity.
    • Presets have now a MAgic property (edit the options of a preset, e.g., by executing EditOption Preset x.y). When the MAgic property is enabled, the preset will behave as a MAgic preset and distribute its values across the range of selected fixtures when calling it.
    • The Commands At MAgic and Off MAgic are obsolete now. If you change the grid position of fixtures and would like to apply the new GridPos value you can use At GridPos.

    Important: MAgic Presets must be stored as selective.

    Thanks guys. But that brings me back to the previous question again. Now that a seq is essentially its own handle, what is the point of having execs at all now?

    Presumably you might want some sort of physical interaction at some point. An exec is a generic point of physical interaction that can act on multiple different types of objects.

    What was/is the intension or reasoning behind changing playback ownership from the primary vehicle built to handle playback objects in MA3 (The Executor) to the Seq (object) When the exec is still primary the vehicle of handling playbacks of all other non seq playback objects? What is so special about the seq now, or what was wrong previously that required this to be reviewed?

    The exec is not the primary vehicle for handling playback of other non-seq objects. All objects which can be assigned to an executor still control their own playback (e.g. if you EditSetting a Group object, you'll see its Master level there, manipulatable without being assigned to an exec).

    Simplified.. IS there a plan to change or modify what we refer to as executors in Ma3, in the future?

    Certainly a plan for more flexibility in terms of playback options (e.g. different options when holding MA vs. not, perhaps the ability to assign a function on button-release, perhaps the ability to use generic command line syntax as a button function, etc.). But in terms of underlying structure? Unlikely.

    Hey Ryan, if playback is owned by the seq now and not the executor, what is the point of executors other than them just being a handle for a sequence? Is the idea to eventually scrap the "executor" handle and just refer directly to seq handles as playbacks or something?

    They are a just a handle, but they work for several different object types, not just Sequences (e.g. Groups, Masters, Macros, to name 3 more off the top of my head). And you can already apply playback or fader commands directly to sequences without them even being assigned to an executor - just specify the target sequence number instead of the exec number

    Hi, with MA2 we used to be able to flash or toggle an exec of change the level of an execs master via the mouse/touch screen/HID

    How do I do this now?
    Clicking anywhere on the exec 201 icon pulls up its edit context menu, regardless of left or right click or where those clicks are made or if the click is held/dragged, or if gestures are used like the spinning motion used to drive the rotation of virtual encoders. it seems to me that i am going crazy. OR like there is no way to physically handle basic controls of an exec using touch or any human interface, which I would think is counter intuitive to the heavy emphasis on UI gesture with the rest of the applications functionality. or maybe I'm doing something wrong?

    Tapping on the Label in the playback window acts as tapping on the label in the playback bar (i.e. opening the assign menu). Tapping on / otherwise interacting with the executor section (i.e. buttons / faders / knobs) will act on the button/fader/knob.


    Also, if I try to edit exec 201 by typing edit exec 201, the edit context opens and exec 201 flashes red as expected, but if I right click exec 201, CLF says the the syntax executed is "edit page 1.201".
    I can then say "on 201" or "off 201" and this works.
    but If try "on exec 1.201" nothing happens, while "on page 1.201" this does toggle on exec 201.
    for a command (where i want to specify the page the exec is on) I have to use on page 1.201" even though the object that I am really meaning to refer to here is an executor. This is confusing and in my opinion should change no?

    This is all working as expected. "Page 1.201" = Page 1 Exec 201. In general in grandMA3, "<object> x.y" = <object> x <child_of_object> y, and executors are children of pages (in the tree structure). If you just say "Exec 201" without specifying the page, it will be Exec 201 on the current page.


    This contrasts with grandMA2 which had lots of inconsistency in the syntax "<object> x.y.z" for which of x, y, and z was the grandparent, parent, object, child, or grandchild object.

    Select + empty exec behavior is expected.


    Master 201 At 100 = illegal object is expected. "Master" is the parent object for all selected, grand, speed, and playback masters. "FaderMaster" is the keyword to set the master fader level of a sequence. In general, perhaps have a look at this thread.