Automated lighting programmers must be very skilled at programming for various types of productions and designers. In most cases, there is a great collaborative working relationship that allows the programmer to share in the creative vision along with the LD. However, there are some shows and LDs that require the programmer to simply enter data into the desk without regard to the end result on stage. In many cases this will occur in theatrical environments, but it could also occur as part of a programming session with any production. It is very important for programmers to be ready to switch to a working format that is purely data entry.
How It Works
Many theatrical LDs will take the time to prepare their notes and magic sheets so that they can simply call out their desired lighting data to a programmer. In these cases, the LD will recite things such as “1 thru 5 and 23 at full, 47 and 201 thru 208 at 50, backlight wash at color seven at full.” The programmer must listen carefully and enter the proper data into the desk almost in time with the LD’s commands.
This is very common when working with conventional fixtures, as it is easy to call out dimmer channels and values. However when working with moving lights, it can become much more complex. There are multitudes of parameters that could be adjusted, and most LDs don’t have the time to call out all the instructions when building cues. This is why the LD will usually take the time to define certain “building blocks” that can be called quickly. These are usually colors, positions, lens focus, gobos, and more that are assigned numbers and/or names. The programmer will receive these notes and create palette/presets accordingly so that they can be quickly selected when called.
The Programmer’s Responsibilities
When programming for an LD that is calling out cue data, it is essential for the programmer to have certain skills and procedures. First, the show file must be organized in a manner that matches the LD’s notes/magic sheets. Second, the programmer must give his/her full attention to the words that the LD is speaking. As the data is called out, it must be entered into the desk exactly. If a programmer is not paying full attention, then mistakes will surely be made. Programmers need to always be at the ready (with fingers hovering above the console keys). There will be little to no time to distract yourself with text messages or other things.
Not only does the programmer need to be ready for immediate and correct data entry, but also the programmer needs to feel comfortable to ask the LD for clarification when something is not heard or sounds incorrect. Furthermore, if the LD changes a channel from its current value to a new value, the programmer must be ready to restore the channel to its previous value if needed. Quite often an LD will ask for a change (could be a value, position, color, or more) and then decide the change is not appropriate and ask the programmer to restore back to the original value. Depending on your console, there could be multiple ways to achieve this, and programmers must always be ready to make the requested restore.
It’s Time to Record
Once a look is built, the LD will usually call out a cue number to record the data to. Again, the programmer must be listening and at the ready to execute this command. It signifies the end of this look’s construction and also the desire to save all the previous commanded work. The LD is counting on the programmer to successfully record the data into the desired cue with the appropriate timing and other information. It is imperative that programmers successfully record cues when asked.
In the event of overlapping cues, the console will usually warn the programmer of the conflict. This must be relayed to the LD so that the LD can decide the appropriate action to resolve the conflict. The programmer must indicate when this happens so that undesired cues are not accidently recorded or changed.
When an LD Goes Exploring
Quite often an LD will be building looks and will want to view various lights, colors, gobos and such. During this time of exploration they will call out things and then decide they no longer need that parameter or value. The programmer must know how to remove the information without erasing all of the existing data and without storing zero (or unwanted) values. For instance, if the LD says, “channel 15 at full,” then “channel 22 at 50,” then “kill 15,” you must respond accordingly. A good programmer will knockout (or OFF) the value so that it no longer exists, while a poor programmer will put channel 15 at zero and record this into the cue. This same situation can happen with any parameter or sets of parameters with automated lights as well as with conventional channels. Always be careful to never accidently record unwanted data into a cue!
The exact procedure to remove data from your active data will be different depending upon your console, so take the time to read the user manual to learn the best method available. LDs will often spend a good amount of time building something and then decide to scrap a portion of it a bit later. Being able to quickly remove portions of a look prior to recording is an essential skill.
Verbal Feedback
Some LDs will have console monitors available to them, while others will simply sit in the house on a headset. This allows them to see the cue data as it is being created and recorded. Some LDs also like to hear their programmer repeat data to ensure it has changed. For example, I program for one theatrical LD that likes for me to verbally repeat adjustments of intensity levels. So when he calls out “channel 44 down 10 percent,” I will make the change and say, “44 at 70.” Some LDs do not like the chatter though, so please be sure to talk with your LD before programming to learn what type of feedback they would like.
Push Button, Get Banana
Automated lighting programming via data entry is certainly not as much fun as collaborating with an LD to create looks. However, there are times when it is required to get data into the desk exactly as the LD envisioned. When these situations arise, it is important for a programmer to understand the responsibilities and procedures to guarantee a great programming session. Listening skills, along with programming skills, are keys to ensuring a successful production. Hopefully too, you will get to share in some collaboration along with the data entry programming style.
