Skip to content

Push Button, Get Banana

Share this Post:

For years, scientists have used buttons to train animals and determine behaviors. The simple act of pressing a button to achieve a certain response can easily be taught to many different species. Button pressing is unassuming process that can be used in various applications to produce different results. At this very moment I am pressing combinations of 56 buttons to write this article.

Later I will be pressing buttons on an automated lighting console to create artistic looks for a production. To be effective in either case, I must completely understand not only what pressing the button does for the system I am working with, but I must also understand how the various buttons and actions interact with each other. Automated lighting programmers spend most of their time pressing buttons and thus must fully understand the abilities of the buttons on their console. Of course, lighting programmers do much more than just push buttons, but there is an art to button pressing, too — and keeping button-presses to a minimum.

Button Press Reduction

The other day, I was heating up something in the microwave. I needed to only cook the item for about 25 seconds. I did as I always do and just pressed the “add minute” button, which puts one minute on the timer and instantly starts the oven. Then after 25 seconds I hit stop and removed my warmed food. My wife asked why I don’t just put in the exact time I need and wait for the oven to stop on its own. I explained that my method was just two button presses, one to start and one to end. Otherwise, I would have to press “cook time” then “2” then “5” then “start.” That would be four button presses! I realized that, as an instinct, I am always looking for ways to reduce button presses throughout my life. Of course, it might not make a big difference when using the microwave, but the practice certainly can speed up my programming time on a lighting console.

Have you ever thought about exactly how many buttons you press on a console when programming a show? There are often many things you can do to reduce the button count of certain actions. One of the best ways to manage your button presses is to plan carefully when setting up your console. First, when assigning fixture numbers, try to use the smallest digit numbers as much as possible. For instance, if your rig has 24 spot fixtures, 24 wash fixtures and 24 dimmers you might want to number them as 1-24 for the spots, 31-54 for the wash, and 61-84 for the dimmers. This way, every fixture requires only two button presses to select. However, if you numbered them as 101-124 for the spots, 201-224 for the wash, and 301-324 for the dimmers, then you would be pressing an additional button every time you selected a fixture. Over the course of a 12-hour programming session, this could result in thousands of unnecessary presses.

You could even reduce the button count for fixture selection further if your console allows you to set up an on-screen plot, or if you create a group for each individual fixture. In either case, you would then only need to touch the screen once for each fixture you wish to select. Speaking of groups, this common console tool is invaluable in helping to reduce button count. You should certainly take the time to create groups for fixture selections that are used often in your programming. Whether you select the group from a touch screen or a keypad, you will always save time and presses by selecting a single group instead of typing discrete fixture numbers.

Making the Most of Your Console

Many functions of automated lighting consoles are designed to streamline operations and reduce button presses. It is important that you take the time to learn about the specific functions and uses of your console. Quite often, you might learn that simply holding a “shift” key while pressing another will accomplish a common task that usually requires multiple button presses. Additionally, you should setup default settings and actions to reduce the need for repetitive modifications in the future. For instance, most consoles default timing at two seconds. If you know you need most of your cues to be in zero time or ten seconds, then you should set the default accordingly, in advance of building cues. This way you only need to adjust the time parameter for cues that differ from the “normal.” You can also usually set the defaults for playback button actions, record methods, new cue options and more. Many consoles let you define what happens after a cue is created or edited. Some settings may clear the programmer or play the new cue as it is created. These automated actions definitely remove repetitive button pushes.

Automated lighting consoles are built on complex computer systems, which enable them to help us perform tasks with less interaction. One example is through the use of keystroke macros. If you know that you will use a particular set of keystrokes often, then you can simply record a macro that remembers the specific sequence. Now you can reduce a large button press routine down to just a few, such as “Macro 4-Enter.” You can even get clever and further reduce the button count by assigning a quick key or playback to trigger the macro. Now you can press just one button, and the console will automatically perform the complex syntax stored in the macro.

More Than Programming

When programming a console, you should also think about how you can reduce the button presses required for playback of the show. If you are setting up a typical concert production that uses multiple pages, you might be able to use special commands that trigger actions as the operator changes pages. Or you could eliminate the need to change pages completely by automating the page change at the end of each song.

As you program, think about the person operating the show and what will be required of them during the production. If a cue requires a light to come on, then snap to another color and fade out, you should determine if this can be automated via auto-follows or if it needs to be three discrete button-presses. Often, it is better to make it only one press and let the console timing trigger the subsequent cues. This frees the operator up to trigger other cues and be ready for the next main cue.

It’s About Efficiency

Reducing the number of buttons we push when programming is not an attempt to shrink the work we do. On the contrary, it is a challenge to increase our efficiency and accuracy when programming. By reducing the number of unnecessary button presses, we have more time to press buttons required to accomplish the tasks at hand. In addition, it ensures that we can use more of our time being creative with the lighting on stage.

It is important to fully understand the capabilities of our console, and reading the manual will often provide insight to shortcuts and defaults that we can use. In addition, every time we choose a quicker method to accomplish a goal, the better we get at it. Automated lighting programmers must be swift and accurate as they program a show, because time is always of the essence. And who knows, these new reduced button-pressing habits might even help in other areas of your life too. Give it a try the next time you program a show or heat something in the microwave.