A live-to-picture concert succeeds when the musical, visual, and technical teams work from one verified timeline. This workflow gives composers, producers, stage managers, conductors, and venue crews a practical production plan: what to confirm, which files to prepare, how to schedule rehearsals, and what to check before the audience enters. Treat the dates and technical settings below as a working template, then replace them with the venue's confirmed requirements.
Overview
In a live-to-picture performance, an orchestra or ensemble plays a score while an audience watches a film, game sequence, or other moving image. The conductor follows the picture through a combination of visible cues, click, streamers, punches, timecode, monitor mixes, and rehearsal marks. The exact system varies by production, but the basic objective remains the same: every department must agree on the same start point, tempo map, picture version, cue names, and emergency procedure.
Begin by assigning clear ownership. The producer or stage manager should maintain the master schedule and contact list. The conductor and composer should approve musical cues and revision priorities. The playback or music-technology lead should own the session, timecode, click, routing, and backups. The video operator should confirm the picture file and projection path. The venue team should document available inputs, outputs, monitors, power, network access, sightlines, and changeover limits.
Do not assume that a file that worked in a studio will work in a concert venue. Ask the house technical lead for delivery specifications before exporting anything. Confirm the picture frame rate, resolution, codec, audio layout, reference level, timecode format, start time, and preferred delivery method in writing. If the venue has a house standard, use it unless the production manager approves an alternative.
For musical preparation, separate the score into a cue list that includes cue name, start time, end time, duration, page or bar reference, click status, timecode reference, and rehearsal priority. This list becomes the shared language for the conductor, librarian, orchestra, playback operator, and stage manager. For related preparation, see the orchestral score preparation checklist and the music spotting session checklist.
What to track
1. Picture and timecode
Track the approved picture version, file name, revision date, frame rate, resolution, aspect ratio, audio configuration, and timecode start. A small picture change can move a musical event or invalidate a rehearsal note, so use one clearly labeled master picture and archive earlier versions separately.
Choose a common reference. SMPTE timecode may be used to align playback, video, lighting, or other systems, while the conductor may work primarily from click, visual cues, and rehearsal marks. Document whether timecode is linear timecode, MIDI timecode, or another synchronization method, and identify which device is the master clock. Avoid letting multiple devices independently generate tempo or timecode unless the technical lead has tested that arrangement.
2. Audio deliverables
Prepare uncompressed audio according to the venue's specification. WAV or BWF files are common working choices, but the required sample rate, bit depth, channel count, and naming convention must come from the production's technical brief. If embedded timecode or metadata is required, confirm how the receiving system reads it rather than assuming that a file name or metadata field will be interpreted consistently.
Deliver separate files or stems when the playback plan needs them: for example, guide tracks, sound-design elements, pre-recorded performers, click, count-ins, or emergency reference mixes. Keep the orchestra's live microphone feeds separate from playback where possible so the mix engineer can balance them independently. Label every channel in plain language and include a channel map.
3. Click, cues, and conductor monitoring
Track the tempo map, meter changes, count-ins, fermatas, pauses, accelerandos, and any moments where click drops out. The conductor needs a reliable monitoring path, usually through a dedicated cue mix, with the level high enough to remain intelligible but not so high that it distracts from the ensemble. Document who controls click level and what happens if the conductor requests a change during rehearsal.
Visual aids should be documented too. Streamers, punches, countdowns, bar numbers, cue lights, and rehearsal marks should use consistent names across the score, playback session, and video display. If a cue is visible only to the conductor, mark that limitation in the rehearsal plan.
4. Routing and redundancy
Draw the signal flow from playback computer to interface, console, monitor sends, conductor feed, house system, and recording or broadcast outputs. Identify every adapter, converter, cable, and power connection that is essential to the show. Keep a tested backup session and duplicate media available, and decide in advance whether the backup is a second computer, a mirrored playback system, or a manual recovery plan. A backup is useful only if someone can switch to it quickly and the conductor knows what the audience will see and hear during the change.
5. Rights, credits, and documentation
Confirm that the production has permission to present the picture, music, arrangements, recordings, and any third-party material. Keep the approved credit language, cue list, and rights contacts with the production documents. The live score performance credits and rights checklist can help organize this part of the preparation, while the cue sheet basics guide covers information that may need to be tracked for the underlying music.
Cadence and checkpoints
Use the following timeline as a planning template. Count backward from the first performance and adjust it for the venue, ensemble size, picture complexity, and travel schedule.
- Eight to twelve weeks before: Confirm rights, venue, ensemble, conductor, picture status, instrumentation, budget ownership, and technical contacts. Request the venue's file and playback specifications. Establish the master cue list and revision process.
- Six to eight weeks before: Lock or identify the picture version. Complete orchestration, engraving, parts, click, and guide-track planning. Create the first technical diagram and identify cues that require special rehearsal time.
- Four to six weeks before: Export test picture and audio files using the agreed settings. Have the venue or playback operator test imports, timecode, channel routing, and monitor paths. Resolve frame-rate, offset, and naming questions before the in-person rehearsal.
- Two to three weeks before: Distribute approved scores, parts, click references, cue lists, and rehearsal notes. Run a complete technical simulation with the actual session structure where possible. Test the backup system and document its changeover steps.
- One week before: Freeze routine edits. Issue a revision log for any remaining changes. Confirm arrival times, loading access, stage plot, riser plan, conductor monitor, video sightline, talkback, recording needs, and emergency contacts.
- Load-in day: Verify power, cable paths, projection or display, timecode, playback, console routing, monitor sends, click, and communication systems before the orchestra call. Save the final working session after the system check.
- Technical rehearsal: Test the beginning, transitions, difficult tempo changes, pauses, credits, intermission, and ending. Then run enough uninterrupted material to expose fatigue, drift, page-turn problems, or monitoring issues.
- Performance day: Hold a short pre-show briefing. Confirm the picture version and session version, run a signal check, verify the conductor's feed, and keep the emergency plan visible to the responsible operators. Avoid unlogged last-minute changes.
- After the show: Save notes on sync, cue clarity, balance, audience-facing issues, and recovery procedures. Archive the final picture reference, session, stems, score, parts, cue list, and revision log.
A useful rehearsal record has five columns: timecode or bar, event, observed problem, owner, and resolution. This turns general comments such as “the second reel felt late” into an actionable note such as “cue 27 click enters two bars early; playback lead to correct count-in and conductor to confirm at next run.”
How to interpret changes
Not every mismatch has the same cause. If the orchestra and picture are consistently offset by the same amount, investigate start time, timecode interpretation, video delay, or monitor latency. If the performance begins correctly but drifts, compare frame rate, tempo map, clock source, and any sample-rate conversion. If only one cue fails, inspect its bar count, meter change, count-in, pause, or local edit rather than rebuilding the whole system.
Separate musical problems from technical problems. A conductor who cannot hear the click clearly may appear to be fighting the picture, while the actual issue is a low or unstable monitor feed. An ensemble that sounds late may be responding to a delayed monitor rather than missing the tempo. Test the conductor's monitoring path from the position where it will be used, not only from the control table.
When the picture changes, compare the old and new versions at every music cue, not just at the beginning and end. Record whether the change affects duration, edit points, dialogue, visual cueing, credits, or the click map. Then update the cue list, session, score notes, rehearsal plan, and delivery archive together. A version number without a revision log is not enough for a complex production.
Prioritize fixes by risk. First address anything that can stop the performance or make the conductor lose the reference. Next address issues that affect the ensemble or audience experience. Cosmetic improvements, such as cleaner labels or more convenient shortcuts, can follow once the show-critical path is stable.
When to revisit
Revisit this workflow at four points: when the picture or score changes, when the venue or playback system changes, before every production season, and after each performance that reveals a new failure mode. A quarterly review is useful for recurring concert programs; a monthly review may be appropriate during an active production period. Update the file-format notes, DAW and operating-system compatibility, hardware inventory, venue delivery windows, contact list, and backup procedure when any of those variables changes.
Before each performance, create a fresh copy of this checklist and mark each item as confirmed, tested, or not applicable. Request written confirmation of the house specifications, export a new test file if the system has changed, and run the tech-rehearsal sequence again even if the program has been performed before. Reuse the timeline, not assumptions.
- Confirm the approved picture, timecode, frame rate, and start point.
- Confirm audio format, channel map, click, guide tracks, and monitor sends.
- Confirm score, parts, cue list, revision log, and credits.
- Test the complete signal path and the conductor's actual monitor position.
- Test the backup session, media, power, and changeover instructions.
- Log unresolved issues with an owner and deadline.
- Archive the final files and performance notes after the show.
For audience-facing planning, pair the production checklist with a live score concert etiquette guide. For future programming and outreach, the film score concert research guide offers a separate way to track events and discover comparable presentations.
