Building a Show File: How to Program Lighting Cues for Repeatable Events
What a Show File Actually Is
A show file is a saved collection of programming data for your lighting rig. Depending on your controller, it might be called a project file, a show, or a library. Inside that file, you store scenes, chases, and cue stacks, each of which handles a different layer of your show.
A scene is a static look. Every fixture has a specific value: pan, tilt, color, gobo, intensity. When you trigger a scene, all those fixtures snap or fade to those stored positions. Think of it as a photograph of your rig at one moment in time. A warm amber wash for dinner hour. A tight blue spot on the head table during toasts. A blackout preset for video playback. These are all scenes.
A chase is a sequence of scenes played back in a loop at a tempo you set. Traditional chases pulse colors across a row of pars or sweep moving heads in synchronized patterns. Most controllers let you sync chase speed to MIDI clock or tap tempo, so your chase locks to the BPM of whatever you're playing.
A cue stack is where show files get powerful. A cue stack is a linear list of scenes or chases, executed in order, one at a time, either manually triggered or on a timer. You build a cue stack for a wedding reception and it becomes your roadmap: cocktail hour look, grand entrance, first dance, open dancing, cake cutting, last dance. Hit GO at each transition, and your rig moves exactly where it needs to be without you touching a fader.
Mapping Your Event Timeline Before You Touch the Console
The most common mistake operators make when building a show file is jumping straight into programming without mapping the event first. Spend ten minutes writing out every distinct moment in the event and what the lighting needs to do at each one. Use the client's timeline or your standard event runsheet as the source.
For a wedding reception, that list typically looks like this: guest seating, cocktail hour, bridal party entrance, couple's entrance, first dance, parent dances, dinner service, open dancing, special songs (anniversary dance, dollar dance), cake cutting, and last dance. Each of those moments has a different energy level, a different color palette, and often a specific fixture behavior. A first dance calls for a tight follow spot, soft colors, and minimal movement. Open dancing is the opposite: full saturation, fast chases, moving heads sweeping the room.
Once you have the timeline, you know exactly how many cues you need. Build one cue per moment, name them clearly (no "Cue 7" or "Scene 12"), and stack them in order. Your show file now mirrors the event from start to finish.
Building Scenes That Hold Up Across Different Venues
One of the hardest parts of building reusable show files is that venues are never the same. Ceiling height, room color, fixture placement, and ambient light all change the way your scenes look. The solution is to build scenes around relative values and fixture groups rather than absolute positions.
Group your fixtures by type and function: front wash, back wash, moving heads, uplights, effects units. When you store a scene, store it at the group level. If your front wash is set to 70% intensity in a warm white, that 70% will read differently in a 12-foot ballroom ceiling than in a 20-foot warehouse, but it gives you a starting point you can nudge quickly on-site.
For moving heads, store home positions as default values for each venue type rather than absolute degree values. Some operators keep three versions of each major scene: low ceiling, standard ceiling, and high ceiling. It adds a few extra cues to the library, but a 30-second pre-show check lets you swap to the right version and never think about it again.
Atmosphere effects need to be part of your scene planning, not an afterthought. If you're running haze machines or fog machines as part of your production, coordinate their output levels with the corresponding lighting scenes. A beam-heavy chase in a dry room looks flat. The same chase in a properly hazed room looks like a headline concert. Build your haze trigger or DMX control into the cue stack so the atmosphere and lighting always move together.
Structuring a Corporate Show File vs. a Wedding File
Wedding and corporate show files share the same architecture, but they have different content priorities. Wedding files lean heavily on emotional transitions: soft, warm scenes for ceremony and dining, then a sharp shift into high-energy dance looks. Corporate files are more utilitarian. You need solid presentation modes (low wash, no movement, clean white or neutral), branded color matching for the client's logo palette, and reliable blackouts for AV moments.
For corporate events, build a "presentation mode" scene group that kills all movement and dials intensity down to a level that doesn't compete with a projected screen. Store it as a single button trigger so you can hit it the moment a speaker walks to the podium. Missing that cue because you're scrolling through menus is the kind of thing clients notice and remember.
For weddings, the first dance and last dance cues carry the most emotional weight. Consider adding a timed cue stack specifically for first dances that you can trigger and walk away from. If the couple wants bubbles during their first dance, a professional bubble machine triggered on a DMX channel can be written directly into that cue so it fires automatically with the lighting shift. No manual trigger, no missed moment.
Making the File Reusable Without Starting From Scratch
The goal of a show file isn't one perfect show. It's a template you iterate and improve over time. After every event, spend five minutes noting what worked and what needed adjustment. Did the dinner wash feel too cool? Did the open dancing chase feel slow for the room? Update the file, save it as the new default, and your next event starts from a better position.
Build your library in layers. Start with a master template that has your core cue stack. Then build venue-specific overlays: outdoor tent values, small club adjustments, large ballroom versions. Keep them all in the same file under clearly labeled groups so you're never rebuilding from zero.
Invest in a controller with enough memory and USB export capability so your show file travels with you on a backup drive. A controller failure mid-event is bad enough. Losing your programming on top of it turns a recoverable situation into a nightmare.
Once your show file discipline is locked in, the rest of your production follows. Your CO2 jets, atmosphere units, and effects gear all become programmable elements in a coordinated show rather than standalone triggers you hit manually and hope land on beat. That's the difference between running a rig and producing a show.
If you're ready to build out the effects side of your production, explore the full SurgeFX lineup of stage lighting and atmosphere equipment designed for mobile DJs and event production professionals. Start with one product category, get it into your show file, and build from there.
]]>