← News Signal Management

Live Signal Management: Common Mistakes and How to Avoid Them

Most live feed failures start with small oversights long before the broadcast begins. Callum Reid goes through the mistakes he sees most often in signal routing and backup, and how to avoid them.

Callum Reid · 20 October 2026 · 6 minutes to read

Treating the backup path as an afterthought

The most common mistake I see is a backup route that exists on paper but has never carried a picture. A second path is only worth having if it follows a genuinely different course from the first: a different connection, different power and, where possible, a different physical cable run. Two links that share one switch or one patch panel fail together, and the producer finds out at the worst moment.

When we plan a signal path from venue to broadcaster, we draw the backup first and check what it shares with the main route. Anything shared is marked as a single point of failure and either removed or accepted openly. A backup you have never tested is a guess, so we send a live picture down it before the event and confirm the receiving end sees it.

Give the backup its own physical route where the venue allows
List every shared device between main and backup paths
Send a real picture down the backup before doors open

Skipping the full chain test on site

Checking each piece of equipment in isolation tells you very little about the whole chain. A camera can be fine, an encoder can be fine, and the feed can still arrive at the broadcaster with the audio a few frames out or a colour range that clips the highlights. These faults only show when the entire path is running from the venue to the receiving desk.

We ask for a window before every outside broadcast to run the complete chain end to end, with the broadcaster's own monitoring on the other end. That is where we catch audio embedding errors, mismatched frame rates and return feeds that were never switched on. Thirty minutes spent here is far cheaper than a troubleshooting call while the programme is already on air.

Run the whole path, not separate components
Ask the receiving desk to confirm picture and sound
Check that return feeds and talkback actually work

Leaving audio until the picture looks right

Video draws the attention, so audio often gets checked last and fastest. Yet a clean picture with a hum, a dropped channel or sound that drifts from the lips will reach viewers as a faulty broadcast. Audio problems are also harder to spot in a noisy venue, where the engineer cannot trust what they hear in the room.

We monitor audio on headphones and on level meters throughout, and we confirm which channels carry which sources before anything goes out. Embedded channel layout is agreed in writing with the broadcaster, because a swapped pair of channels is an easy mistake and a visible one. Treat sound as half of the signal from the first minute of setup, not as a finishing touch.

Agree the channel layout with the broadcaster beforehand
Watch level meters as well as listening
Check lip sync at the receiving end

Assuming the venue network will cope

Venues often promise a fast connection, and the promise is rarely tested under load. A network that works well in an empty hall can slow badly once the audience arrives and thousands of phones join it. Shared bandwidth, firewalls that block the ports a feed needs and wireless links crowded by other equipment are all frequent causes of dropouts.

Our approach is to ask early for a dedicated connection, ask what is actually blocked, and measure it on site at a similar time of day to the event itself. Where a dedicated line is not possible, we plan a bonded or alternative route and tell the producer plainly what risk remains. It is better to know the weakness in advance than to find it halfway through a live programme.

Request a dedicated line, not shared guest wifi
Ask which ports and protocols the venue blocks
Measure bandwidth during busy periods, not quiet ones

Poor monitoring and no one watching the signal

A feed that nobody is watching can fail quietly. Freezes, black frames and audio loss are easy to miss if the engineer is also busy with other tasks, and the broadcaster may not tell you until the problem has run for minutes. Monitoring needs to be a named job, with a person whose attention stays on the outgoing signal for the whole programme.

We keep a monitor on the actual output, not just the source, so that what we see is what the broadcaster receives. Alarms for loss of picture or audio are set but never relied on alone. Clear roles also help: one person watches the signal, another handles changes, and both know who calls the broadcaster if something goes wrong. Calm, specific communication matters more than speed.

Monitor the outgoing feed, not only the source
Name one person responsible for watching the signal
Agree who contacts the broadcaster and by what route

Rushing the setup and the handover

Late arrival is the quiet cause of many of these mistakes. When setup is squeezed, tests are shortened, labels are skipped and the backup is left unchecked. The handover to the broadcaster suffers too, because the details they need, such as contact numbers, feed formats and timings, are never written down clearly.

We build a margin into every schedule and agree a single sheet of facts with the broadcaster: formats, timings, who to call and what the fallback is. Everything on the cables is labelled, so that anyone can follow the path in a hurry. A well-prepared setup looks uneventful, and that is precisely the aim. When nothing dramatic happens, the preparation has done its job.

Allow time for tests in every schedule
Write a one-page sheet of formats, timings and contacts
Label every cable and port

Most live signal faults are not exotic. They come from untested backups, partial testing, neglected audio, optimistic assumptions about networks and nobody watching the output. Each is avoidable with a little planning and a calm routine. If you have a broadcast coming up this autumn, go through these points with your engineer well beforehand, and ask what has actually been tested rather than what is expected to work.

Callum Reid

Senior Video Engineer

Callum designs signal paths and backup routes, keeping live feeds stable under pressure.