Mapping Signal Routing Before You Pull a Single Cable
A practical walk through planning camera, graphics and intercom routing on paper first, so a studio or live event gets cabled once and runs predictably from rehearsal to transmission.
Most routing problems I see on shared productions began with a floor plan drawn before anyone listed what actually needs to travel. Before measuring any cable run, write down every source and every destination: cameras, graphics machines, playout, replay, talkback stations, confidence monitors, and the vision mixer itself. Give each one a short, permanent name. That list becomes the spine of the whole project. When a director asks whether the second graphics output can feed the stage screen as well as the mixer, you can answer from a sheet instead of guessing at a rack. It also shows early on where you are short of inputs, outputs or converters, while changing the plan still costs nothing.
Keep the list to one page where you can. Group the entries by direction: what leaves the camera positions, what arrives at the control room, what returns to the floor. Mark anything that needs a different format, such as a camera feeding in at one frame rate while the graphics machine outputs at another. Those mismatches are quiet and expensive when they surface during line-up, and a single note beside the entry is usually enough to catch them.
Once the list exists, decide which signals travel straight from source to destination and which pass through a router. A direct run is simple and has one fewer thing to fail, which suits a camera that only ever feeds one input. A routed path costs a port and a little planning, but it lets you change who sees what without touching a connector. For a studio that will be used for several programmes, I lean towards routing anything a producer might reasonably want to move: graphics, replay, programme return and the feeds going to the green room. For a one-day event, direct runs with a couple of splitters are often the calmer choice, because fewer layers mean fewer places to look when something goes dark.
Whichever way you lean, write the decision beside each path and give the reason in a few words. Six months later, someone arriving to adapt the room will want to know whether a direct cable was a deliberate choice or a shortcut taken on a busy afternoon. That note saves a surprising amount of rewiring and a good deal of argument.
Intercom is often added last and cabled in whatever space remains. That tends to show in rehearsal, when the camera operators cannot hear the director over a hum nobody can trace. Plan talkback as a system with its own list of stations, its own channels and its own power, kept physically apart from audio cable where the layout allows. Decide how many channels the show needs and who sits on each. A common split gives the director and vision mixer one channel, the camera crew another, and a third for floor management and stage staff. Keep the arrangement simple enough that a new operator can understand it from a single printed card beside their position.
Also plan what happens when a belt pack fails or a headset cable is pulled. Having a spare station patched and labelled in the rack means the answer takes a minute instead of an anxious search through a flight case with the clock running. Test every station from the control room, speaking and listening, before anything else is switched on.
Labelling is the part everyone agrees with and few finish. Put the same name on both ends of every cable, using the names from your signal list, and add a colour band for the type of signal so a glance tells you whether you are holding video, audio or data. Do it while the cable is in your hand, not at the end of a long day. Photograph the rack and the patch panel once the system is working, and file the image with the signal list. If the room is rebuilt for another production, the photograph shows what was connected and where it ended up, which is far quicker than reading a plan that has drifted from reality.
Keep one master copy of the documentation and make everyone work from it. Several slightly different versions pinned in different corners cause more confusion than having none. When a change is made during rehearsal, update the master that evening and tell the crew what moved. It takes ten minutes and prevents the same fault being rediscovered by someone new.
Run a full test with nobody else in the room. Send a clear test signal down each path, from every source to every destination on the list, and tick the entry off only when you have seen or heard it arrive at the other end. It is slow work, and it is the cheapest time you will ever spend on the project. Look for the quiet failures as well as the obvious ones: a signal that arrives but flickers when a cable is touched, audio that is present but a little low, a feed that works until the router changes state. Gently move the connectors and watch for any drop. A cable that fails under a light tug will fail under a passing foot.
Finish by running the system for a while, perhaps an hour, with everything switched on and warm. Some faults only appear once equipment has heated up and settled. If the hour passes quietly, you have a rig you can hand to a crew with some confidence, and a record showing exactly what was checked and when.
No production keeps the plan it started with. A guest arrives with their own laptop, a producer wants a second screen in the foyer, a camera is moved to a different position. The aim of good routing is not to prevent change but to make it cheap.
Leave a few spare inputs and outputs unassigned and labelled as spare, and keep a short run of known-good cable and a couple of converters within reach. When a change request comes, handle it the same way as the original plan: add it to the signal list, decide direct or routed, label it, test it. It feels slower in the moment than simply plugging something in, but it keeps the documentation true, and a true document is what lets a different person take over the desk without a long handover conversation.
Good signal routing is mostly written down before it is built. A clear list, sensible choices between direct and routed paths, a separate plan for intercom, honest labelling and patient testing give a crew a system they can trust and adapt. None of it is glamorous, but the calm you hear in a control room during transmission usually comes from this quiet preparation done well in the weeks before.
Keep reading
What Does a Live Event Production Crew Actually Do on the Day?
The question we hear most from organisers is what happens between doors opening and the final fade. Helen Marsh walks through the crew roles, the run-of-show and the decisions made live.
A checklist for signal routing before you commit to a design
Tom Eastley sets out the questions worth answering before a cabling, routing and intercom plan is signed off, so cameras, graphics and playout connect without surprises on the day.