The Sound Cue That Arrived Late
A Year 11 production team is staging a 55-minute one-act play in a 120-seat school theatre. The sound designer, a student new to QLab, has built 34 cues but has only rehearsed them twice with the cast. At the technical rehearsal, three problems appear: (1) a 6-second thunder cue fires 2 seconds before the actor's line that motivates it; (2) the preshow music continues under the first two lines of dialogue because the operator missed the fade cue; (3) a phone-ring cue plays at full volume while the actor is speaking softly upstage, masking her words. The director wants to 'fix it in the dress rehearsal' and refuses to cut any cues. The stage manager has logged each fault with a timestamp and the operator's account of what she saw on the cue list.
1. Explain how the production team should diagnose and prioritise these three sound faults, and justify which fault must be resolved first.
Read the worked answer
The team should separate faults by cause type before deciding priority, because each fault has a different fix and a different risk.
Fault 1 (early thunder) is a timing/sequencing problem. The cue is probably written with a pre-wait or the operator is anticipating the line. The fix is structural: place the cue on the cue line (the last words before the effect) and agree who calls it - the stage manager, not the operator's judgement. This is a cue-calling protocol issue, not a volume issue.
Fault 2 (preshow music under dialogue) is an operator-attention problem. The fade cue is being missed because the operator is watching the stage rather than the script. The fix is to give the operator a marked-up cue script with the fade written as a standby and a go, and to rehearse the transition in isolation.
Fault 3 (phone masking dialogue) is an audibility/intelligibility problem and is the most serious. Sound design in theatre serves the text; if the audience cannot hear the actor, the moment is lost regardless of how well-timed the cue is. Masking also cannot be fixed by the actor 'speaking up' alone, because the cue is at full volume and the actor is upstage of the speakers.
Priority order: Fault 3 first (it destroys meaning in performance), then Fault 1 (it destroys the intended dramatic effect), then Fault 2 (it is a rehearsal-discipline issue that will resolve with a marked script). The director's refusal to cut cues is defensible only if the designer can show each cue earns its place; the team should ask the designer to justify the 34 cues against the script's dramatic beats and be willing to merge or delete cues that duplicate function. 'Fixing it in the dress rehearsal' is risky because dress rehearsals are for integration, not for discovering basic cue logic.
2. The stage manager proposes logging faults as 'operator error' in the production report. Evaluate whether this is an adequate record, and describe what a more useful log would contain.
Read the worked answer
'Operator error' is an inadequate record because it names a person rather than a condition, and it gives the next rehearsal nothing to act on. A production report is a working document for the whole team, not a blame record.
A useful log would capture, for each fault: the timestamp and cue number; the intended effect (what the script and design asked for); the observed effect (what the audience would have heard); the probable cause stated neutrally (e.g. 'cue 12 fired on operator's manual go rather than SM call'); the action agreed (e.g. 'cue 12 reassigned to SM call; operator to rehearse standby'); and the owner and deadline for the fix.
This matters because the three faults have different owners: Fault 1 belongs to the stage manager (cue-calling), Fault 2 to the operator and the designer (script markup and rehearsal), Fault 3 to the designer and director (level and speaker placement). Labelling all three 'operator error' hides the design and staging causes and would let Fault 3 - the audibility problem - go unfixed. A good log also records what was tried, so the team does not repeat a failed fix in the next rehearsal.