Building from last week, this time we’ll talk about filling in for another programmer.  This is debatably a larger subject and has many more variables in my opinion.  So I’m going to hit the big ideas, while you will have to do whatever you think is best in the moment.  This article assumes you are filling in for but NOT replacing the programmer.  But it doesn’t assume that you are filling in on your strongest console.  When I was working my way up through the ranks, I filled in on all ETC consoles, Hog 3/4, GMA2, Chamsys, and M1/Onyx.  I kept multiple pages of notes on the consoles I didn’t program regularly filled with reminders on how to do things on each platform.  I always review these notes before I head in to work- even if it means losing sleep.  The Gaffer/Designer shouldn’t have to suffer because I don’t usually program this particular console.

Communication

This is the single biggest item.  If you can communicate with the programmer you are filling in for, please do it with plenty of advance time.  Here is a starting list of questions to ask:

• Can you walk me through your show file?
• Is there a particular power up/power down sequence that needs to be done?
• What working methods do the Gaffer/DP/Designer prefer?
• Have you already made materials for the day or days of work I’ll be there?  How do you intend them to work?
• Is there a default Day Look or Night Look I should start in?
• What views do you use most in your template and why?
• Does the DP like to talk to the programmer, or does everything go through the Gaffer?  
• Are recurring custom colors a thing, and where do I find them?
• What is/are the linking key(s) for wireless?
• What is the password to their router for remote app access?
• If I am on stage- ask for PDFs of the light plots and/or lighting paperwork.  Examine and ask follow up questions.
• Is there an IP address map or list for the production?  Examine and ask follow up questions.
• Are the groups disposable/flexible, and therefor I can edit them, or are they fixed and cannot be edited?
• Does the programmer rely on pixel mapping for effects often?  Onyx (for instance) hugely relies on pixel maps to provide things that would otherwise be in the effects engine. I’ve done my share of pixel mapping, but debatably not as much as I should by now.  So this would be important for me to get a heads up about so I can hopefully explore the show file beforehand and remind myself or research best practice for this console. 
• Will the original programmer continue with this show file, or is this a “fork”?  Fork means a show file that is broken off and will not carry forward.  The advantage is you can do anything you want to the show file since you don’t have to worry about the original programmer being frustrated or confused by what you may have changed.  This may be the biggest question of all.

Saddle Up

Assuming the show file will be carried forward by the original programmer, you have to tread carefully.  On the day, I start by doing a “Save As” with the date and my initials.  Next, I make a custom layout that has areas where I can put new groups, macros, whatever I need in a place that is easy to find and add to as the day goes on.  Having space to customize without changing their template is important.  I always label the view (and everything else I make if possible) with my initials.  That way the original programmer knows what to get rid of.

If possible, I quickly flash the lighting one system at a time and test the beginning and end of each channel range to make sure I understand their numbering.  I then make sure I have a view that gives me their color and/or CCT palettes along with a view of the programmer filtered to only show me what is active, or nothing at all- depends on the console.

Next priority is to examine the Effects.  Does the programmer default to intensity effects that go DOWN from the base value, or UP?  I always do down, so it’s important to be ready to either make new effects or adjust my programming style quickly.

I then quickly test to see if typing Fixture at 5 Enter/Please will result in the fixture going to 50% or 05%.  I like it to go to 50%, but obviously I’m a guest here.

If there are moving lights, I test to make sure the orientation is what I expect.

To be honest, this list is something it will probably take you the morning to get through and you will need to be sneaky to get away with testing everything without disturbing the work going on around you.  But it’s important to know what is going to happen before you finish any command.  Be sure to check in with your Gaffer/Designer a few times through the day to see if there is anything they would like different from you.  Also- as you go through the day- try to make note of any new content you’ve created and write down anything that will help your original programmer return to work smoothly.

The Dismount

When finished, back up the file(s) to every place your programmer wants.  Be sure to take a copy of the day(s) work with you.  This will make answering any follow up questions much easier.  Call or text your programmer to give them an information dump that walks them through what happened, any new content, and especially any time your Gaffer/Designer specifically asked you to revise existing content.  Let them know if any gear behaved strangely and might need repair or attention.   

Without going into detail that probably would no longer be helpful, I believe I’ve given you enough to start a good conversation and/or process of filling in.  Every situation is unique, so try to think in the spirit of the suggestions rather than try to do exactly what I wrote.  And as always- I’m very interested in hearing of things I may have missed, or from your own best practice.  Hit me in the comments.

Featured Image Photo by Octavian-Dan Craciun on Unsplash

***

Mark LaPierre is a programmer in film and television based out of Albuquerque.  He grew up in live entertainment and has been a designer/programmer for musicals, concert dance, live music, circus and corporate.  Mark is a proud member of IATSE, an ETC Eos trainer and an enthusiastic trainer of many other platforms and subjects.  If you enjoy his content, please consider commenting on his posts on the website to appease the Algorithm.