The evening Marcus rang us
Marcus runs a small regional panel programme that goes out live on a Thursday evening. He rang us in the first weeks of autumn because his two-person gallery had begun to struggle. The show had grown from a half-hour chat into a full hour with a studio audience, a remote guest on most nights, and a set of lower-third captions that someone had to fire by hand while also watching the clock. He was candid on the phone. Nothing had gone badly wrong yet, he said, but he could feel it coming. One person was cueing playout, mixing the captions and answering the director all at once, and the director was starting to dread the quiet gaps between segments.
I took the call because the problem sat squarely in real-time video operation, which is the part of our work I spend most of my time on. I asked him to send the running order and a sketch of how his signals reached the desk. Those two documents told me more than an hour of talking would have done, and they shaped everything we proposed next.
What the gallery looked like before
The running order showed a tight hour with nine segments, three pre-recorded inserts, a handful of replayed moments from earlier in the show, and one remote guest joining over an internet link. The desk handled all of it from a single seat, with the director talking over the operator's shoulder and calling cues aloud. What stood out was how many different jobs were hidden inside the word operator. Playing the inserts was one job. Triggering captions was another. Pulling a replay clip in the right place was a third. Watching the remote link for trouble was a fourth, and nobody was formally watching it at all. It simply got attention whenever the other three allowed.
None of this was careless. It is how many small teams grow into live work, one extra duty at a time. But each added duty makes the next mistake more likely, and a live show gives you exactly one attempt at every moment.
- Playout of pre-recorded inserts
- Caption and graphics triggering
- Replay clip selection
- Monitoring the remote guest's incoming feed
Splitting the work across trained operators
Our proposal was modest. We would supply two operators for the evening rather than one, and divide the duties so that nobody carried more than two at once. One operator took playout and the remote feed. The other took graphics and replay. Marcus's own switcher stayed with him, cutting between cameras as he always had. We held a rehearsal in the afternoon before the first show, not the night itself. The operators learned the order of the segments, the names of the clips and the way Marcus's director liked to call cues, which was short and slightly clipped. Matching that rhythm mattered more than any piece of equipment, because a cue that arrives late by a second feels very long in a gallery.
We also agreed on a small set of spoken phrases for problems, so that bad news could travel across the room in a calm, flat voice.
The night the remote guest froze
About forty minutes in, the remote guest's picture stopped. The face held on one expression while the audio carried on, then the audio began to stutter as well. In the old arrangement this would have been the moment the single operator lost the thread of everything else. Instead the operator on the remote feed said, in an even voice, that the link was degrading. The director had perhaps ten seconds of warning. The graphics operator already had a holding caption ready with the guest's name, and the replay operator offered a clip of the guest's earlier answer, which the director chose to run while the host filled gently.
The guest reconnected two minutes later with audio only, and the show carried on. Viewers at home saw a short replay and a steady host. Marcus told us afterwards that nobody in the studio raised their voice, which was the real result he had been hoping for.
What we took from it as a team
The lesson was not that two operators beat one, though they did that night. It was that live work becomes calm when each duty has a named owner and a plain spoken signal for trouble. The freeze was an ordinary fault. What made it manageable was that someone was assigned to watch for exactly that kind of fault. Since then we have used the same habit on other shows: list every job hidden inside the word operator, give each one a person, and rehearse the bad moments out loud before they happen. It costs an afternoon and saves a good deal of nerves.
Marcus still books us for the larger Thursday editions, and his own team now handles the lighter ones, having sat beside our operators long enough to borrow their routines.
- List each duty separately before assigning anyone
- Rehearse the spoken phrases for faults
- Keep a holding caption and a replay clip ready for the remote link
Real-time video operation is mostly about attention: knowing who is watching which signal, and saying so plainly when something changes. Marcus's evening ended well because the work had been divided and rehearsed, not because anyone was heroic. If your own gallery has one person quietly doing four jobs, it is worth writing the jobs down. The list alone often shows where the next live problem is likely to appear.
