Learning the switcher on live kit: how Jamie's team found its footing

A request that began with a missed cue

Jamie runs a small events company that streams conferences and panel evenings. He got in touch in the early autumn after a live session in which his operator cut to the wrong camera during a speaker handover, and nobody on comms said a word about it until the break. The show survived, but he wanted his three-person crew to work as a gallery rather than as three people sitting near one another.

We talked on the phone for about twenty minutes. He did not ask for a lecture on broadcast theory. He asked whether we could put his crew in front of a proper switcher, with real cameras and a real talkback system, and let them make their mistakes somewhere that did not have an audience watching.

That suited how we teach. The crew-training sessions at narravix are built around production equipment, not slides, and I agreed to run the first two days at his own venue so the team could learn on the room they actually use.

What we set up before anyone touched a button

Before the first morning I asked Jamie for his usual run sheet and a rough camera plan. From those I built a short rehearsal show: a presenter, a two-person panel and a few pre-recorded inserts. It was deliberately ordinary, because the aim was to practise the shows he really delivers rather than anything spectacular.

On arrival we walked the signal path together. I asked each person to point at the source, the switcher input and the output feeding the stream. Two of the three could not do it for the audio path, and that gap explained a good deal of the earlier confusion.

We agreed the ground rules for the room: one voice on the director channel at a time, cues called in a fixed order, and no operator acting on a hunch without a call. Small rules, but they gave everyone something firm to lean on when the pace picked up.

• Walk the full signal path from camera to stream
• Agree who speaks on comms, and in what order
• Run a short show that mirrors the real programme

Day one: slow cuts and plain language

On the first morning I kept the pace gentle. Each person took a turn on the switcher while another directed, and the third watched the multiview and noted anything that looked off. We rotated every half hour so nobody stayed comfortable for long.

Most of the early errors were not about the equipment at all. They were about words. The director would say cut when she meant take the next shot, or ready two without naming the camera. We stopped and rewrote the phrases on a sheet taped above the desk, using the same few words for the same few actions.

By the afternoon the cuts were cleaner, mostly because the calls were. Jamie, who sat in at the back, told me later that it was the first time he had heard his crew sound like they were reading from the same page.

Day two: breaking things on purpose

The second day was about faults. I would not recommend learning fault handling during a paid broadcast, so we caused problems deliberately. I pulled a camera feed mid-programme, muted a microphone without warning and let a graphic fail to fire. The crew had to find it, say it and fix it while the show carried on.

The first attempt was untidy. Two people spoke at once and the director lost the thread. We paused, talked through what each person should have done, and ran it again. The second time the operator flagged the lost feed within a few seconds and the director cut away before the fault reached the output.

That is the habit we work towards: name the problem calmly, state the action, then act. Repetition does most of the work, and it only works when the equipment in front of you is real.

• Lose a camera feed during a live cut
• Drop a microphone without warning
• Miss a graphic cue and recover on air

What changed afterwards

Jamie sent me a note a few weeks after the workshop. His crew had streamed a full-day conference since then, and the handover between speakers, the very point where things had gone wrong before, passed without a hitch. He said the biggest difference was how quiet the gallery had become, in a good way, with fewer overlapping voices and more short, clear calls.

I try not to overstate what two days can do. His team still has plenty to learn, and they know it. What they now have is a shared vocabulary, a habit of checking the signal path before a show and a rehearsed response to the common faults.

He has since asked about a follow-up session focused on graphics and replay for a sports client, which we will discuss once his diary settles.

What I took from it as the trainer

Every crew I train teaches me something about how people behave in a gallery under pressure. With Jamie's team, the lesson was that confidence comes from vocabulary and repetition more than from knowing every button on the desk. Once the language was settled, the hardware stopped feeling intimidating.

I also noticed how much it helped to train in the venue itself. The crew learned the quirks of their own cabling, their own monitor positions and their own talkback unit, which a borrowed studio would never have given them.

If you are weighing up training for your own operators, think about where it will be delivered and on what equipment. The closer it is to your real show, the more of it stays with the team afterwards.