Before You Commit: A Checklist for Gallery Equipment Integration

Start with what the gallery has to do

Before anyone talks about racks or cable runs, write down what the gallery must deliver on a bad day, not an average one. How many cameras go live at once, how many guests are miked, how many graphics and playback sources feed the vision mixer, and who needs to hear whom. A news programme with a single presenter has very different demands from a live interview show with remote guests and a studio audience.

I come to these projects from the audio side, and the same pattern repeats: the brief names the equipment, but not the behaviour. A list of boxes tells an integrator what to buy. A list of behaviours, such as two presenters able to talk back to the gallery without the guest hearing, tells them how to connect it all and what to test at the end.

Keep this first page short and plain. One side of paper, agreed by the producer, the studio manager and the technical lead, is a better foundation than a thirty-page specification nobody has read.

• Number of live camera and playback sources
• Number of microphones and who hears them
• Remote guests, if any, and how they join
• Longest broadcast the gallery must sustain

Map the signal flow on paper first

A signal flow diagram is the cheapest piece of engineering in the whole project. Draw every source on the left, every destination on the right, and the router, mixer and converters in between. Mark each connection with its format and where it physically runs. Gaps and surprises show up on paper in minutes; found during installation, they cost days.

Pay particular attention to the places where formats change: an older camera feeding a newer mixer, an embedded audio path that has to be broken out, a monitor wall that expects a different standard. Each conversion is a small risk of delay, lost sync or a wrong aspect ratio on air.

Ask whoever plans the wiring to show you this diagram in a form you can read without specialist software. If you cannot follow it, neither will the person covering a shift when the original engineer is away.

Treat intercom and talkback as a system, not an extra

Intercom is often the last thing specified and the first thing blamed when a live show wobbles. A director who cannot reach the floor manager in time, or a presenter who hears the wrong channel in their earpiece, causes more visible mistakes than most picture faults.

Decide early who needs a private line, who needs to hear programme audio, and who must never hear the gallery chatter. Talk through what happens when a user leaves the room, and whether a belt pack can be swapped without reprogramming anything. Check that the intercom shares a sensible reference with the rest of the system, since a mismatch there produces hum or drift that is tiresome to trace.

Make a short list of the talkback paths your best director uses without thinking. Then ask to see each one working before anything is signed off.

• Private director to floor manager line
• Producer to presenter earpiece feed
• Clean programme return for guests
• Separate route for engineering calls

Plan monitoring so people can actually see problems

Monitoring decides how quickly a team spots a fault. Think about what each person needs to see: the director needs every source and the preview, the vision mixer operator needs the next shot clearly, the audio operator needs meters and a trustworthy listening position. Placing screens purely to fit the room often hides the one picture somebody needed.

Consider the viewing distance and the lighting in the gallery itself. A bright room washes out a screen that looked fine in the showroom, and low light makes small text unreadable at the back of the desk. Mark where each monitor sits relative to the people who rely on it.

Also decide how the team will know a source has failed. A frozen frame on a small tile is easy to miss under pressure, so ask about clear indicators for loss of signal and for tally state.

Insist on a test plan before installation begins

Wiring that has been plugged in is not wiring that has been tested. Ask for a written test plan that lists what will be checked, in what order, and who signs it off. It should cover every source to every destination, every intercom path, and the behaviour of the system when a unit is switched off or a cable is pulled.

Run at least one rehearsal as a real programme, with the real crew, at real length. Faults that hide for ten minutes often appear at minute forty, when a thermal setting or a buffer limit is reached. Priya's rule on the audio side is to listen for the first hour, not the first minute.

Keep the results. A short record of what passed on the day makes later faults far quicker to trace, and gives a new engineer a fair starting point.

• Every source to every destination
• Every intercom and talkback path
• Switch-off and cable-pull behaviour
• A rehearsal at full programme length

Decide the fallback and the handover before you decide anything else

Every gallery fails eventually, so ask what happens when it does. Which source goes to air if the main mixer drops out? Can the team reach a basic output from a second path in under a minute? A modest fallback you have rehearsed is worth more than an elaborate one nobody has tried.

Then ask about handover. Who holds the diagrams, the router configuration and the passwords, and where are they stored? Will your own staff be shown how things work, or will they learn when something breaks? A gallery that only one person understands carries a hidden risk.

Finally, agree what support looks like once the work is finished: who answers the phone, how quickly, and what is outside scope. These answers belong in writing next to the diagrams.