Its 2018! Lets make our showfiles more efficient.

Here’s what you’ll need:
– One thumb drive
– One grandMA2 console on grandMA2 onPC running software version 3.3.4.3
– grandMA3D v3.3.4.3 (Optional)
– The Consoletrainer 2018 showfile (Includes our updates up through Day Twelve) so you can play along.
You can grab the software for free at http://www.malighting.com/en/support-downloads/software.html

Software Version used in series: 3.3.4.3

On our thirteenth day of 18 in 2018, we’re going to make getting the attributes we want to work with onto our encoder wheels faster.  If you’ve ever had to click around your wheels looking for where that parameter might be located, this will help.

Let’s back up our show and rename it for Day 13.  If you don’t have the showfile- take a second to download it from the link in the YouTube description, or at my website, consoletrainer.com.

For anyone who’s ever worked with media servers, you know that because they have so many more parameters than a moving light, you sometimes have to hunt through your wheelsets to find the parameter that you need.  Add that to the fact that there are SO many different styles of profile creation of media servers, and you can probably understand the frustration of having to poke around until you find that one parameter that you need.  Instead of having to wonder if the “Scale” parameter might be in Gobo or Video or Beam- how about we just make a macro that gets us there.  I use media servers as the example here, just because they have so many more parameters than your normal moving light, but you can build these macros for ANY parameter.  We’ll use our consoletrainer showfile to see how.

Lets select the Vipers and say that we want to make a macro that jumps our encoder wheels to the Prism effect. First, in our Programmer View, I’m going to scroll through the Macro window to find a nice empty bank of cells to store these in, and Re-record that View. Next, we’ll find where the prism wheels are.  I know its a BEAM parameter, so start there. I’ll click through the Attribute selection until I see Effect- as that’s what the Prism encoder is labeled.  Now, to know what I need to put into the Macro, I need to see what the last command was.  If your mouse is on the command line, you can just hit the arrow up key to see that our last command was  ATTRIBUTE “EffectIndexRotate”. That’s what we need so I’ll highlight it and Control+C to copy it. Next, I’ll Edit an empty macro cell, click “add” and paste that same command line. I’ll label it “prism” and close the editor. To see it work, click a different Preset Type, then press the Macro- there it is. That’s it.  You can repeat the process for any other parameter.