Posts by robgarcia


    With the help of my distributor, I believe we've narrowed it down to a Windows 11 network issue.

    I have no problems getting everything to connect using the scenario above on a windows 10 machine.


    In a perfect world, I'd love to have the time and energy to dig in and learn LUA and plugin coding.

    In the meantime, I have a few things that I'm in need of plugin wise that I'd like to pay to have developed.

    If there is anyone interested, please contact me at robgarciatech <at> gmail <dot> com and I can explain further what I'm looking for.

    If this type of post/request is not OK for this forum, feel free to delete.



    Correct, that is how I have it. Capture running on my laptop with the viz-key connected.

    Back on my desktop, I NEVER see the Viz-Key show up in the Network settings window.

    The only reason I ended up starting MA-3 on the laptop was to see if I could get the key to show up there.


    Not sure what I'm doing wrong...

    Here is my setup.

    Laptop (where I want to connect my viz-key + Capture to run) has an MA-Net IP address of

    Desktop where I want to run MA3 and program from has an MA-Net IP address of

    I can get both machines running in session with NO issues. But - I can't seem to get the Vis+Dongle line to ever show up under "NetworkNode" in Network settings.

    Back on the laptop however, if I run MA3, change the MA-Net Ip to the wifi adaptop (which is currently disabled) then it does show up. It's like the viz-key has binded itself to a certain IP.


    I have multi-instance fixtures where I "default" the parent fixture to 100.

    I understand in reading the release notes that IfOutput selects only fixtures that have non default values.

    But why doesn't it select instances of the fixtures that I have stored in a sequence with a dimmer value above zero?

    If I just use "IfOutput" it brings any single instance fixtures above zero into my programmer, but ignores any children on multi-instance fixtures that are above zero.

    If I use "ifoutput sequence 6" then I get everything I'd expect.


    I’ve taken the basic concept of the MA Startshow color picker and tweaked it a bit to suit my needs by adding additional colors and more than 6 lines etc.

    Looking for a clever way to punch up colors in each line and have that combination able to be recalled in some way.


    Best I can think of is setting a variable on every color sequence and make a macro that reads all those variables and stores them in some way. But with 15 colors across 10 lines/groups, it seems pretty cumbersome.

    Maybe a better way?


    Perfect, thanks. Was missing "call."

    Tried just "Macro" and "Go macro"

    No longer need the preceding "1." anymore either, just "macro_number.macro_line"

    If I copy DataPool 1 at 10 - go into DataPool 10, all groups, presets etc. in sequences reference DataPool 1.

    If I copy DataPool 10 at 15 - go into DataPool 15, all groups, preset etc. in sequences STILL reference DataPool 1.

    If I go back to DataPool 1, and do an operation like: delete group thru. Go back into DataPool 10 or 15, any recipe line that referenced a group is now blank.


    Playing around some with copying DataPools and noticed that even if I copy a complete DataPool:

    copy DataPool 1 at 10

    In the new DataPool, when I go into a sequence and look at the recipe, it's references back to Objects and presets in DataPool 1 instead of the new one.

    Not saying this isn't intended behavior - just trying to understand why.

    Let's say I'm preparing for a show in a new venue, was hoping I could create a new stage with patch etc., then copy either part or all of my Default DataPool to a new one and be off and running. In my new DataPool, update my groups and presets etc. But, if all of my recipes in all of my sequences are referencing objects and presets from DataPool 1, that makes things tough.

    Hope that rambling makes sense...


    2 macros for exporting/importing items while maintaining gaps/spacing in the pool.


    SetGlobalVar "RG_Exp_Type" ("Export What?")
    SetGlobalVar "RG_Exp_Range" ("What Range?")
    SetGlobalVar "RG_Exp_Name" ("Export Name?")
    SetGlobalVar "RG_Exp_Name" $"RG_Exp_Name"".xml"
    Export $RG_Exp_Type $RG_Exp_Range $"RG_Exp_Name" /Gaps "Yes"
    DelGlobalVar "RG_Exp_Type"
    DelGlobalVar "RG_Exp_Range"
    DelGlobalVar "RG_Exp_Name"


    SetGlobalVar "RG_Imp_File" ("File Name")
    SetGlobalVar "RG_Imp_File" $"RG_Imp_File"".xml"
    SetGlobalVar "RG_Imp_Type" ("Import Type IE: group")
    SetGlobalVar "RG_Imp_Number" ("Import Starting At What Number?")
    Import Library $"RG_Imp_File" At $RG_Imp_Type $RG_Imp_Number /Gaps "Yes"
    DelGlobalVar "RG_Imp_File"
    DelGlobalVar "RG_Imp_Number"
    DelGlobalVar "RG_Imp_Type"

    Would be a fun little plugin to make if I knew my way around LUA.


    Sharing 2 simple, but handy macros for either storing or removing fixture values as defaults.

    My macros use all pool 25 with a preset named "Default." Change to your needs. Make a fixture selection, attribute adjustments and run macro...

    Store Default:

    off featuregroup dimmer
    Store preset 25."Default" /merge
    at preset 25."Default"
    store default /merge

    Remove Default:

    store preset 25."Default" /remove
    store default /remove