Multifixtures as single fixture

  • Hi, i did a macro to make a phase but I'm stuck in this: all my single fixtures (beams and spots) are responding correctly, but my multicell fixtures aren't, how could do in order to my multi fixtures works as a single fixture and works as I expected to?

    thanks.

  • Would need more detail to know for sure, but there are a few ways to do it depending on your setup and needs and the fixture types, but in all cases the selection grid is king.


    For the below examples I have I patched 5 Color Force D72 Mode 1 fixtures with 48 cells. If you type along with the selection grid open it might make it a little more clear (except when the cells are all on top of each other)


    First, and probably easiest is to select the parent fixtures and apply the phase to them, the parent fixtures should pass the phase and values to the children (cells).


    Fixture 1 Thru 5 At 0

    Next Step

    At 100

    Phase 0 thru 360


    If you needed to select the cells you could also use the down key, this effectively puts all of the cells in on the same x-axis of the selection grid.

    Fixture 1 Thru 5

    Down

    At 0

    Next Step

    At 100

    Phase 0 thru 360


    If you had all of the cells selected linearly on the selection grid you could use MA Tricks, to make blocks of 48 cells and give them the same phase (effectively putting all of the cells on the same grid coordinate).

    1.1 thru fixture 2.1 thru fixture 3.1 thru fixture 4.1 thru fixture 5.1 thru

    At 0

    Next Step

    At 100

    Set Selection MATricks "XBlock" 48

    Phase 0 thru 360


    I'm sure There are lots of other ways I'm missing.


    Also has the MATricks always been broken from what's in the manual?

  • Also has the MATricks always been broken from what's in the manual?

    Seems that the keyword page in the manual is not up do date.

    The syntax change has been documented, however by the releasenotes only:


    https://help2.malighting.com/P…pool#toc_header_anchor_31


    For consistency the keyword for MAtricks-pool-objects was changed from MAtricksPool to merely MAtricks

    (e.g. keyword for the Group-pool-objects is Group, not GroupPool)

    the fallout being a slightly more complex syntax (for now at least) to set the properties of the MAtricks embedded in the Selection object of your programmer.