Posts by bwerst


    I'd like this feature too. Normal use case: You created a cool look for a program element, but you're not sure if that element is going to make it into the final program, instance, night, showing. Example: Tonight's program is going to skip verse 3. You know it in advance and would like to be able to just keep hitting Go+ without worrying about needing to jump to a specific cue number. However, the next night verse 3 will get used so re-enable the cue(s).

    Hopefully disabled cues will be easier to identify and toggle then finding and removing cmd macros that skip ahead to a later cue numbers.

    I can see use cases for having tracking excluded and cases for forwarding.

    Thank you!

    That required flipping the keypress order, but it worked great!

    1) Press Macro

    2) Press desired Command column field.

    3) Enter speed value in input dialog box

    4) Press enter and it's done.

    Thank you!

    So how would you do this for a selected field / cue?

    For instance I'm trying to create a macro to help setting a speed master on the first cue of a song.


    SetUserVariable NewBPM = ("Enter Speed Master BPM")

    SetUserVariable BpmCmd = "Master 3.1 at BPM "$"NewBPM"

    Set Property "command" $BpmCmd

    Two issues:

    1) The string concatenation isn't working correctly.

    2) Illegal Property "command"

    Desired workflow.

    1) Press the desired Command column field on the desired cue.

    2) Press the macro preset.

    3) Type a speed value. (example:123)

    4) Press Enter and done.

    Cue Command column should then contain:

    Master 3.1 at BPM 123


    I like that edit plugin has a 'SyntaxError' column, but how do I find out what error and where. Is there a log file for lua scripts?

    What is the debugging workflow?

    I exported the MessageBox lua template to a lua file and edited in Visual Studio Code which helps with some of the formatting. I then had to do a copy paste into an empty plugin editor, because I wasn't sure how to import a lua file into plugin even though the .lua file was placed in c:\ProgramData\MALightingTechnology\gma3_library\datapools\plugins.

    What's the best way to create a debugging / testing environment?


    I like to create screens that show a layout and then a single row of the layouts pool to create expand our views selection. An issue is that layouts pool seems to effect all layouts on any screen. When you select a layout from the pool all layouts on all screens change. Is there a way to make the layout pool only set/select layouts on the same screen?

    Ideally in the attached photo the two layouts would operate independently, but currently that are synchronized.


    We have a Windows 7 desktop onPC system with Command Wing and Fader wing acting as a backup console to a full size during programs and then remote server during the week. If we lock the desk overnight the next morning the computer still shows the Desk Locked screens, but is completely unresponsive. We basically have to reboot the machine. Desk Lock generally works fine during the day, but haven't really tested if the computer is idle for many hours.

    Most of the Windows power saving features have been turned off, but this seems likely conflict.

    We'd like to use the full size desk while programming and service time, but otherwise shut it off and leave the onPC computer running 24x7. The hope is we can use an iPad on stage connecting to the onPC computer during the week while making rigging changes or doing small things.

    What's the best practice? Can we leave onPC running 24x7? Should we use MA's Desk Lock or Windows Lock User? We have a full size console and command wing, but no NPUs.

    Hi Andreas,

    Thanks for the response.

    I can understand creating a separate GUI interface for different user types. Further, I can see that benefiting from changes to the physical interface. I am very saddened however by having a completely incompatible back line. We are an environment that would benefit greatly from an optimized interface for non-full time lighting designers in some venues, but not others. As a facility however we would like to standardize our equipment. From a systems perspective I would prefer interchangeable nodes and consoles that can talk to each other.

    I was really hoping the new MA console would be a great fit for our smaller venues at a proportionally lower price point. I was really gungho on GrandMA all the way. Now however, I'm going to be taking serious looks at competitors products now. Going with a competitor is now no more difficult perhaps even easier and more affordable without paying the MA premium.


    Will a series comparison guide be released soon? I was really looking forward to the launch of the new series because it might fit our venues better, but I'm really concerned by the incompatibility with other MA Product lines mentioned in the forum.

    We have two venues still running Full-size MA1 consoles, and two running onPC command wings. We have several smaller venues we would like to upgrade to MA consoles, but they are too small to justify the cost of MA2 light. We would however like the capability to move consoles between rooms for rare special occasions. Also, one of our big reasons wanting to switch the smaller venues to MA is standardization. Dot2 looks similar, but different which might not help on the standardization front.

    Anyway, will you be releasing a guide which will help determine which console family will be most appropriate in various scenarios? If so, when?