How to Plan Projection Rehearsals for Live Performance

What are the essential technical specifications to gather before beginning projection rehearsals?

Collect the native resolution of your projectors and the exact throw distance from the lens to the surface in meters. You also need the lumen output of each unit and the specific color temperature, usually 6500K, to make sure your content files match the hardware capabilities before you start programming.

How should a production team integrate projection cues into the broader technical rehearsal schedule?

Projection cues should be treated as distinct technical events that require dedicated slots within the broader cue list to avoid overwhelming the stage manager.

• Timecode syncs allow the media server to follow the show clock, removing the need for manual triggering during complex musical sequences.
• Hold points provide the stage manager with a predefined moment to pause the media flow if a performer misses a mark.
• Backups must be pre-loaded on a secondary machine, with a physical switcher ready to toggle in under 2 seconds if the primary server fails.
• Checklists for the deck crew should include specific steps for cleaning lenses and verifying projector alignment before every single performance.

What strategies are most effective for troubleshooting hardware and software failures during live rehearsals?

Effective troubleshooting relies on isolating the signal chain immediately when a failure occurs. Start by checking the physical connection points, such as the HDMI or SDI cables, as these are the most common points of failure in a high-vibration stage environment. If the image is dropping out, bypass any signal splitters or long-run extenders to determine if the hardware or the distribution path is the culprit. Having a secondary, pre-tested laptop ready to feed a simple test pattern into the projector can quickly confirm whether the issue lies within the primary media server software or the projection hardware itself.

The nuance here is that software crashes often stem from memory leaks caused by high-resolution video files. If your system is stuttering, try reducing the bit rate of your clips rather than immediately replacing hardware, as this often resolves performance issues without requiring a full system reboot during a high-stakes rehearsal.

How do you establish a clear communication workflow between the projection designer and the stage management team?

Establish a dedicated communication channel that prioritizes brevity and clarity between the projection designer and the stage management team.

1. Headsets should be used to maintain a private, low-latency audio loop that doesn't distract the performers or the director.
2. Terminology must be standardized, using specific cue numbers rather than descriptive names like "the blue scene" to prevent confusion.
3. Check-ins should occur at the start of every session to confirm that the media server and console are talking to each other.
4. Logs of every change made during the rehearsal must be shared in a digital document immediately after the session ends.
5. Signals for "go" and "standby" must be strictly followed, even during dry technical rehearsals, to build muscle memory for the entire crew.

What is the recommended process for blocking performers in relation to projected content?

Performers should maintain a minimum distance of 1.5 meters from the projection surface to prevent their bodies from casting large, distracting shadows. Use floor tape to mark these "no-go" zones during the initial blocking phase so actors can internalize their boundaries without needing to look at the screen constantly.

How can projection rehearsals be structured to maximize efficiency when limited stage time is available?

Prioritize the most complex visual sequences first, as these consume the majority of your setup time and require the most refinement. Use a "looping" technique where you run only the specific cue transition repeatedly until the timing is precise, rather than running the entire scene from start to finish. A lot of people assume that you need to run the full show to get the timing right, but you actually save hours by isolating the specific 10-second window where the projection meets the performer.

What documentation is necessary to ensure consistency in projection playback across multiple performances?

Maintain a master cue sheet that tracks every transition, including the specific server layer, opacity level, and transition duration for every single projection event. This document serves as the source of truth for the entire technical team. For example, if a specific transition requires a 3-second fade, that timing must be explicitly logged to prevent variations between the dress rehearsal and opening night. If you don't have this level of detail, the show will drift as different operators interpret the cues differently.

The exception to this rule is when the show requires live, improvisational elements. In those cases, the documentation should focus on the "base state" of the media server rather than rigid timing, allowing the operator the flexibility to react to the performer's energy while keeping the technical parameters within a safe, pre-defined range.

How should the rehearsal environment be adapted to accurately simulate the final lighting and projection conditions?

The rehearsal environment requires a controlled lighting state that mimics the final show conditions to prevent surprises during the first public performance.

• Worklights must be turned off completely, as even low-level stage lighting can significantly reduce the perceived contrast of your projected images.
• Scrims or other translucent materials should be placed in their final positions to test how they interact with the light output.
• Fog machines need to be run at the exact intensity used in the show, as haze drastically changes how the beam appears to the audience.
• Reflections from the stage floor must be measured, as high-gloss surfaces can bounce light back into the audience's eyes or onto the scenery.