Documenting Projection Rehearsals for Better Show Flow
Projection design is rarely static, and the difference between a smooth tech session and a chaotic one often depends on how you capture the chaos. While software like QLab or TouchDesigner handles the execution, the human side of tracking changes remains messy. Documentation styles vary wildly between touring productions and resident houses, but the most successful teams treat their rehearsal logs as a living technical document rather than a simple checklist.
What essential components should be included in a technical rider for projection mapping?
A technical rider must list exact projector throw distances and native resolution requirements to prevent hardware mismatches. Include a minimum of 4 dedicated power circuits rated for 20 amps each to support high-lumen laser projectors. These specifications prevent last-minute power failures or image distortion during the actual performance run.
Quick facts
| Category | Recommended Tool | Update Frequency |
|---|---|---|
| Cue Timing | Spreadsheet/DAW | Every run |
| Hardware State | Configuration File | Daily |
| Design Notes | Shared Task Board | Per session |
| Versioning | Git/Cloud Sync | Every save |
How can stage managers effectively track cue sequences and timing adjustments during technical rehearsals?
Stage managers should utilize a live cue-tracking document that syncs directly with the media server’s internal clock. By logging the precise timecode for every visual transition, the team can identify drifting sequences that occur when actors vary their pacing. Using a dedicated column for "Actual vs. Planned" duration allows for immediate identification of timing discrepancies during a run.
One common nuance involves the "human factor" in live performance. Even when cues are perfectly timed to a clock, a live performer might hold a beat for dramatic effect. In these instances, the stage manager must document the specific trigger point—such as a hand gesture or a vocal cue—rather than relying solely on the timecode to initiate the next projection sequence.
What are the best practices for logging hardware configurations and software settings to ensure consistency across rehearsals?
Consistency relies on maintaining a rigorous, centralized record of every device parameter and software state throughout the production cycle.
- Projector IP addresses: Assign static addresses to every unit to prevent network conflicts when hardware is power-cycled during daily setup.
- EDID settings: Lock these values to make sure the media server always recognizes the projector's native resolution and refresh rate correctly.
- Color profiles: Save ICC profiles locally on the server to prevent shifts in color reproduction if a monitor is swapped.
- Firmware versions: Log the exact build number for every piece of hardware to avoid unexpected compatibility issues during critical rehearsals.
How should collaborative feedback between directors and media designers be documented to streamline iterative changes?
Use a shared digital comment thread linked directly to specific timecodes in your media server’s interface to keep feedback contextual. This prevents the loss of nuance that occurs when feedback is separated from the visual sequence it addresses. Many people assume that a weekly summary email is enough to track design changes, but these messages quickly become outdated and lack the granular detail needed for precise technical adjustments. Real-time logging makes sure that every tweak is tied to a specific rehearsal date and outcome.
What methods are most effective for archiving visual assets and version control throughout the production process?
Store all high-resolution source files in a cloud-based repository that supports at least 5 versions of every asset. Label files using a standard date-based naming convention, such as YYYYMMDD_AssetName_V01, to prevent confusion. This structure allows the team to revert to a stable look within seconds if a new render fails.
How can safety protocols and equipment maintenance schedules be integrated into the rehearsal documentation?
Integrate these requirements by embedding maintenance logs directly into the master rehearsal schedule to make sure no equipment is overlooked.
- Lamp hours: Track the total usage time for each projector to schedule replacements before the light output drops below 80 percent brightness.
- Filter cleanings: Perform these every 50 hours of operation to prevent overheating and premature component failure in dusty venue environments.
- Cable integrity: Inspect all signal lines for kinks or fraying after every load-out to prevent intermittent signal loss during the next show.
- Thermal checks: Monitor internal temperature readings during the first 15 minutes of operation to identify cooling system obstructions early.
What strategies help in mapping out physical projection surfaces and sightlines for future reference?
Documenting physical surfaces requires creating a 3D wireframe model that maps the exact coordinates of the projection area relative to the lens position. Use laser distance measures to record the distance from the lens to the center of the surface, noting the horizontal and vertical offsets in millimeters. This data allows for rapid realignment if the projector is bumped or moved between sessions.
The primary exception involves complex, non-planar surfaces where light wrap becomes an issue. In these cases, simple distance measurements aren't enough. You must also document the specific "keystone" or "warp" values applied in the software to compensate for the surface geometry. Without these specific software-side adjustments, even a perfectly positioned projector will produce a distorted image that fails to align with the physical architecture of the set.
How can post-rehearsal debriefing notes be structured to improve workflow efficiency for subsequent performances?
Debriefing notes should categorize issues by frequency and impact to prioritize technical fixes for the next rehearsal.
| Issue Category | Frequency (Per Week) | Impact Score (1-10) |
|---|---|---|
| Server Latency | 3 | 8 |
| Focus Drift | 5 | 6 |
| Color Mismatch | 1 | 9 |
| Cue Misalignment | 8 | 4 |
Use these scores to allocate your limited technical time, addressing items with high impact scores first to stabilize the production.
Common mistakes
- Relying on memory. Designers often assume they'll remember specific brightness tweaks, but these must be logged immediately to avoid repeating the same errors the next day.
- Ignoring hardware logs. Failing to record exact projector positioning and lens settings makes it nearly impossible to replicate a look if a unit is bumped or replaced.
- Fragmented communication. Spreading feedback across text messages and sticky notes creates gaps in the record; keep all design notes in one shared document.
Maintaining your production records
Establish a single source of truth for your technical data before the first rehearsal begins. Reviewing these logs with your team after every run makes sure that minor adjustments don't become major obstacles during the final dress rehearsals.