What a Dress Rehearsal Really Means Before a Multi-Camera Stream

The term, in plain words

In live production, a dress rehearsal means running the whole show as if the audience were already watching, from the first opening scene to the last closing graphic. The word comes from theatre, where actors wear their full costumes for the last practice. In a stream, the costume is everything that will be live on the day: the cameras, the microphones, the scenes, the overlays and the platform connection.

A common mistake is to treat a quick signal check as a rehearsal. Switching on each camera and speaking into each microphone proves that a device works. It does not prove that the show works. A rehearsal tests the sequence, the timing and the people operating it, and it exposes the gaps between the parts.

I teach audio routing, so I tend to hear problems first, but the idea applies to every part of the chain.

Rehearsal is not the same as a test

A test asks one narrow question: does this thing work right now? Is the camera feed arriving, does the encoder connect, is the microphone level moving? Tests are quick and are best done one at a time, early in the day, while there is still room to fix what they find.

A rehearsal asks a wider question: can this crew run this show from start to finish without stopping? That includes the moments between segments, the handover from one speaker to another and the point where a presenter walks out of frame. These are exactly the places where a signal that tested fine can still fail in practice.

Learners in the programme often find that their tests all passed and their first rehearsal still went wrong. That is normal, and it is the reason the rehearsal exists.

What the written checklist is for

The checklist is the written record of what the rehearsal must prove. It covers four areas: cameras, sound, scenes and platform settings. Each line is a plain statement that can be ticked or not, such as camera two is labelled and framed, or the lapel microphone is unmuted and peaks below the agreed level.

Writing it down matters because live work is stressful and memory is unreliable. A person who has set up the same room many times will still skip a step when the clock is running. A paper list does not skip steps, and it lets a second person check the first.

The list also belongs to the crew, not to one person. Anyone who joins late can read it and know what has already been confirmed.

• Cameras: each source present, labelled, framed and stable
• Sound: every microphone live, levels set, no echo in the room
• Scenes: each layout and overlay shown in the planned order
• Platform: stream key entered, resolution and bitrate confirmed

Running the full pass

Start the rehearsal at the planned show start time and run it without stopping unless something breaks badly. Stopping at every small flaw hides the real problem, which is how the crew copes when something goes slightly wrong with no pause available. Note the flaw, keep going and fix it afterwards.

Use real content. If the show opens with a title scene and a spoken welcome, do exactly that. If a guest joins at the midpoint, rehearse the moment they appear and the moment their microphone opens. These handovers are where audio drops, wrong scenes and late cuts tend to show up.

Record the rehearsal if you can, then watch it back with sound on. Problems you missed while operating are often obvious from the viewer's side, such as a hum under quiet speech or a camera that sits slightly off level.

Checking from the audience side

Once the stream is sending to the destination platform, open it on a separate device, ideally on a different network from the one used to send. This shows what a viewer would actually receive rather than what the control desk believes it is sending. Delay, dropped frames and level differences between speakers all become visible and audible here.

Listen on ordinary speakers or headphones rather than the studio monitors. A mix that sounds balanced in a treated room can have a voice buried under music on a laptop. As an audio instructor I would rather you found that on a Tuesday than during the event.

Remember that results still depend on the venue connection, the platform and the equipment agreed for the day. The rehearsal shows how your own setup behaves, not how any outside network will behave later.

Fixing, then repeating

After the pass, go through your notes in order of risk. Anything that could take the stream off air comes first: a weak connection, a camera that dropped, a microphone that cut out. Cosmetic issues such as an overlay position come last, and some can wait for another day.

Change one thing at a time and then check it again. Making three adjustments together makes it impossible to know which one helped or which one caused a new fault. Add the fix to the checklist so that it is checked from now on.

If the first pass needed many repairs, run a second shorter rehearsal covering only the parts that changed. A crew that has seen the whole show work once is calmer on the day, and calm is what keeps a live stream steady.