Audiovisual control · Practical guide
Immersive experience: prepare repeated audiovisual sessions
Repeating a session requires knowing when the previous one ended and what content stays visible while the next is prepared. Restarting the program should not be confused with fresh start authorization.
- AV holding content
- Operator authorization for an identified session
- Introduction → main content → closing
- End review and fresh authorization
Give each session its own identity
Use a session identity alongside the cue: DEMO_A and DEMO_B are fictional examples. An opening can have the same number in both performances, but requests and records need to distinguish them.
Prepare introduction, main block, and return-to-hold files with duration and revision. Describe any point that must wait for a human decision in the rundown.
What changes between performances
| Stage | Decision or condition | Intended output |
|---|---|---|
| Preparation | Operator reviews files and destinations | Holding content |
| Start | Fresh authorization for the session | Identified introduction |
| Main | Agreed confirmation of the prior step | That session’s AV content |
| End | Operator confirms closing | Return to holding background |
| Next performance | Review pending requests and issue a fresh call | New session without replaying prior cues |
A timer ending does not establish that every player finished. Define which documented interface feedback will be used and what the operator will observe to confirm completion. If it is missing, retain holding content and decide how to proceed.
If a session is interrupted
Proposal: the operator identifies the last confirmed content and chooses to restart the block or return to holding content. Document what happens to audio, image, and lighting calls; stopping a timeline does not independently define the outputs.
Before the next performance, review pending requests and discard those belonging to the closed session under the agreed logic. Recovering a project file does not establish recovery of every device state.
Rehearsal plan and proposal scope
- Normal session: compare the four change points with intended outputs.
- Start requested twice: review that the proposed program does not repeat the introduction improperly.
- Unconfirmed closing: retain holding content or take the agreed manual alternative.
- New session: review content and confirm no old request remains pending.
These checks form a rehearsal plan: record the observed result before treating each stage as verified. To choose a platform, confirm zone count, media types, session staffing, and rundown variability. The proposal does not control doors, access, evacuation, or machinery.