Hardwired or IP: Choosing a Signal Path for Live Shows

SDI is simple in a way that matters on air. A signal leaves a source, passes through the router and arrives at the mixer with a delay so small that nobody in the gallery has to think about it. Cueing a camera shot or a roll-in behaves the way the crew expects, and that predictability is worth a great deal when a presenter is waiting for a countdown.

IP can match that, but only when the network is designed for it. Timing relies on a shared reference, switches must be configured to prioritise media traffic, and a single misconfigured port can introduce delay that shows up as a lip-sync complaint twenty minutes into the show. If your team already spends time chasing audio drift, adding network timing to the list needs a clear owner.

When a picture drops during a live broadcast, the fastest diagnosis wins. With baseband, the chain is physical: you trace the cable, swap a connector, check the router output, and a trained operator can usually isolate the fault in a couple of minutes. The failure modes are familiar, and most of the crew will have met them before.

On an IP system the fault might sit in a switch, a configuration, a firmware mismatch or a bandwidth limit, and finding it needs tools and someone who can read them. The upside is visibility: a good monitoring page shows every flow and its health at once. The catch is that this only helps if somebody has built it and knows what normal looks like before the show begins.

Live Production Workflows covers more than getting pictures to the mixer. Cue sheets, intercom, graphics triggers, isolated camera recording and the feed to the outside world all depend on the signal path you pick. In a baseband gallery, recording an isolated feed means a dedicated router output and a recorder for each source, which is straightforward but uses ports and cable quickly.

With IP, taking a second copy of any flow is far easier, because a signal can be subscribed to in more than one place. That makes isolated recordings, remote monitoring and a clean delivery feed cheaper to add. For teams that record many sources or send material to a remote contributor, this flexibility is the strongest argument for the network route, provided the planning is done early.

Equipment is only half the decision. A baseband gallery asks for solid cable discipline, labelling and a patching habit that the whole crew shares. A team that has worked this way for years will move quickly and make few mistakes, and new starters can be trained in a day or two on the basics of the router and the signal flow.

An IP gallery asks for different skills: understanding addressing, reading switch status and agreeing a change procedure so that nobody alters a setting an hour before transmission. If you have one person who enjoys that work and can document it, the route is open to you. If not, you may spend the savings on outside help and still feel uneasy on show day.

For a small or mid-sized studio running regular live shows with a fixed gallery, I recommend staying with baseband for the main programme path and adding IP only where it earns its place, such as isolated recordings, remote monitoring or a contribution feed from another location. This keeps the on-air chain simple and familiar while giving you the flexibility that matters.

Move the whole gallery to IP when you are rebuilding it anyway, when the show count justifies a dedicated network engineer, or when you need to share a signal across several rooms. Whichever way you go, draw the signal map on paper first, agree who owns each part of it, and run a full rehearsal with the recording and delivery chain connected, not only the pictures.