Six Wiring and Setup Mistakes We Keep Finding in Live Studio Galleries

The first mistake happens before any cable is pulled. A studio buys a vision mixer, a router and a monitoring wall as separate items, each chosen on its own merits, and only afterwards asks how they will talk to one another. The result is adapters, converters and workarounds that nobody drew on a diagram. In mid autumn, when many stations are refreshing their schedules, this is the habit I see most often.

The fix is dull but effective: start from the programme you need to put on air and work backwards. How many sources, how many outputs, which of them must keep running if a unit fails. Once that is written down, the equipment choices become much narrower, and each item has a stated reason for being in the rack rather than a place on a wish list.

• Write the signal list before choosing hardware
• Mark which paths must survive a single failure
• Agree control protocols between units early

A router can be set up in an afternoon, and that is exactly the danger. Names, salvos and lock settings get entered from memory, and six months later nobody can say why input 14 feeds a monitor in the green room. When something goes wrong during a live bulletin, the engineer on shift is reading labels that no longer match reality.

We keep a single configuration record for every router we install: source and destination names, the logic behind each preset, and a dated change log. It sits with the studio, not with us. A new technician should be able to open it on a quiet afternoon and understand the system without asking anyone who has since left the company.

• Use one naming scheme across router, mixer and monitors
• Keep a dated change log beside the configuration file

Intercom is often the last thing specified and the first thing a director complains about. Too few channels, a floor panel nobody can hear over the set, or a talkback feed that bleeds into the programme mix: each of these is a small error with a very visible cost on air. Producers rarely notice until the first rehearsal with a full crew.

Plan intercom as a system with its own routing, not as a box that comes with the mixer. Decide who needs to speak to whom, which groups share a channel, and where the floor beltpacks are charged. Then test it with the real number of people, because a four-person trial tells you nothing about a gallery of ten talking at once.

• List every role that needs talkback and its partners
• Test with the full crew, not a quiet half-team

Hum and buzz are among the most stubborn faults in a studio, and they usually start with how power was distributed. Equipment plugged into whichever socket was nearest, mixed earth paths between the gallery and the floor, and long unbalanced runs all invite noise that no amount of later tinkering fully removes.

Before racks are populated, agree where power enters, how it is split, and how earth is handled across the building. Use balanced connections wherever the signal allows, and keep power and signal cables apart in the trunking. These decisions cost little at the planning stage and a great deal if the ceiling and floor have to be reopened after the studio is already in use.

• Plan power distribution before racks are filled
• Separate mains and signal runs in all trunking

A commissioning test that proves everything works when nothing goes wrong is not much of a test. Studios sign off a system after seeing picture and sound on the monitors, then discover during a live programme that a failed power supply or a dropped link has no safe route around it. The plan existed on paper but was never rehearsed.

We deliberately break things during commissioning, with the client watching: pull a feed, power down a unit, lose a link. The crew sees how the system behaves and what the recovery steps are. Each fault is then written into a short failover checklist that stays in the gallery. Rehearsing a failure on a quiet afternoon is far cheaper than meeting one for the first time on air.

• Simulate a failed feed, unit and link before sign-off
• Turn each rehearsed fault into a checklist line

The last mistake is treating handover as a folder of PDFs left on a desk. Documentation matters, but the people who will run the gallery every morning need to have their hands on it while someone who built it is standing next to them. Otherwise knowledge stays with the installer and leaves the building when we do.

Plan at least one session where the operating crew runs a rehearsal programme themselves, asking questions as they go. Note what confuses them and fix the labelling or the documentation on the spot. A studio that can be operated confidently by its own team a week after we leave is the real measure of a finished integration.

• Run a full rehearsal led by your own crew
• Correct labels and notes on the day questions arise