Happy Tuesday!  I looked up the definition of the word macro.  Merriam-Webster states, “Being large, thick, or exceptionally prominent.”  I thought, uhh…, that’s not quite right.  Then it hit me, oh yea wrong part of speech.  I’m looking for the thing, or noun version of macro.  M-W states, “A single computer instruction that stands for a sequence of operations.”  In other words, a single button press that recalls a string of commands.

I remember sitting in my high school auditorium looking at their ETC Insight and not having the foggiest clue on what I am supposed to do with a macro.  I understood and knew how to use subs, cues, patching (they called it soft patching), but not macros.  I read the manual and it shed some light on how to make a macro, but it stopped there.  I wanted to write about how I use macros and open discussion on how other programmers use them. 

First, on a GrandMA I use macros quite often for changing my views.  The 5 buttons to the right of each touch screen can be assigned as either a view or a macro.  On the full size which has three touchscreens, there is a lot of real estate and for most shows using only the views works fine.  For larger shows, or particularly on the GrandMA Light (or smaller versions), I need to be more organized and compact.  Rather than assigning views to the buttons, I assign macros to the buttons.  I use them to delete the view button, recall a new view, and assign a new macro to the button.  Since macros are executed much faster than the operator can, this allows a since view/macro button to work as a double push, instantaneously.  For example, the first push gives the fixture sheet.  The second push gives the channel sheet.  Another push will circle us back to the fixture sheet. 

Next, I like to use macros to access the control functions for different fixtures.  Particularly, the hard to remember ones.  For example, how do I re-home a Cyberlight?  First, set your intensity channel at full, then set your control channel at full, then your intensity at 0, then within 3 seconds, set the control channel on what you want.  On a Hog 2, this may take 3 or 4 tries.  I’d rather make a macro. 

On installs I LOVE to make ‘Start Up’ and ‘Shut Down’ macros.  Typically, I set fixtures to lamp on when told to do so via DMX, rather than at power up, or when DMX is present.  Therefore, once everything is powered up, it is time to lamp everything on.  Instead of having the end-user select each group of fixtures and lamp them on (of course they also need to remember any tricks to access the control function) I have a macro do everything for them.  Usually, I program the macro to home everything, wait until the homing process is finished, then lamp everything on.  That way, they can turn the console and system on, push the ‘Start Up’ macro, wait a minute or two and then everything is ready. 

Macros are my go-to tool when it comes to programming on a CueServer.  In fact, I probably use macros more on a CueServer than any other lighting device.  I use them for clearing playlists, changing/adjusting the screen, assigning looks or cues or other macros to the buttons on the face of the unit, recalling variables, and recalling looks. 

Macros are a useful tool, but only if you know when and how to use them.  There is no right or wrong answer and most manuals will only touch on the subject as the execution or how you use them is left up to the programmer.  How/when do you use macros?  Do you use them more on one console versus another?  GrandMA 2 has open ended macros; I wonder how I might use them?!?!

-BC