Start from the programme, not the equipment list
Every integration job I take on begins with a plain question: what does the programme need to do on air? A two-person news desk with a weather segment asks very different things of a gallery than a three-camera interview show with remote guests. Write down the formats, the number of sources, how many people sit in the gallery, and what has to be possible at the press of one button. Only then does a vision mixer, a router or an intercom panel become a sensible choice rather than a catalogue preference.
It helps to keep this brief to a single page. List the sources you expect on a busy day, the outputs you must feed, and the people who need to talk to one another. Add the things that happen rarely but must never fail, such as a guest joining late or a camera being swapped mid-programme. This page becomes the reference for every later decision, and it is far cheaper to correct on paper than after the racks are built.
- Number of cameras, graphics sources and remote feeds
- Outputs: transmission, recording, confidence monitors
- Gallery roles and who needs talkback to whom
- Rare events the system must survive
Draw the signal path before choosing a mixer
A signal diagram is the most useful document in the whole project. Draw each source from its origin to every place it ends up, marking format, cable type and any conversion along the way. Mistakes show up on paper: a source that needs two outputs but has one, a monitor wall fed through a converter nobody budgeted for, or an audio embed that happens in two places. When the diagram is clean, the specification of the vision mixer and router almost writes itself.
Resist the urge to add capacity everywhere. Spare inputs are sensible, but a router sized three times larger than the studio will ever need adds cost, heat and menus for operators to wade through. I usually plan for the current programme plus a modest margin, and make sure the frame or chassis can be expanded later without rewiring. Label every path on the diagram with the same names that will appear on the physical panels.
- Mark format and cable type on every path
- Note every conversion and where it happens
- Use identical names on diagram, panels and labels
Choose the vision mixer for the operators who will use it
The mixer is the part of the chain people look at most, so judge it by how your crew will actually work. Consider the number of mix levels, the keyers you need for graphics and pictures-in-picture, and whether macros can recall the common sequences of a bulletin. A control surface that suits a technical director cutting a fast multi-camera show may be more than a small news operation needs, while a compact panel can frustrate a gallery running complex layouts.
Ask for a hands-on session with your own operators before you commit. Have them run through a typical running order, including a recovery from a mistake. Note which buttons they reach for, how long it takes to find a source, and whether the labelling makes sense across a long shift. Those observations matter more than a feature table. Finally, check how the mixer takes its reference and how it is controlled, because it must sit comfortably within the rest of the studio's timing.
- Match keyers and mix levels to real formats
- Test macros against a genuine running order
- Check reference and control connections early
Treat monitoring and intercom as part of the system
Monitoring and intercom are often left until the end, which is when they are squeezed. Give them the same care as the mixer. The picture monitors in the gallery should show the sources the director needs in a sensible layout, with clear tallies and labels that follow the router's names. Audio monitoring needs a quiet, consistent listening position, and a decision about what each operator hears in their own channel and what is shared.
Intercom deserves a short design of its own. Decide who talks to the studio floor, who talks to the presenter's earpiece, and who has a private line between gallery roles. Keep the number of party lines small enough that people remember them under pressure. Test every belt pack and panel from every position, and confirm that talkback still works if one part of the network drops out. Calm, clear communication is what holds a live programme together when something goes wrong.
- Labels and tallies follow the router names
- Keep party lines few and memorable
- Test talkback from every position and after a fault
Install in stages and test each one
Build the system in stages rather than all at once. Start with power and grounding, then the racks and the core routing, then each source and destination in turn. After every stage, check the result against the diagram and sign it off before moving on. Faults found when one cable run is connected are quick to trace; faults found when the whole studio is wired and the presenter is waiting are not. Keep a simple log of what was tested, by whom and what the result was.
Leave proper time for a full rehearsal with the real crew. Run the longest and most awkward programme you expect, with graphics, remote guests and a deliberate failure or two. Watch what the operators do rather than what the manual says they should do. Adjust labels, macros and monitor layouts straight away, while the reasons are fresh. A studio that is handed over after a convincing rehearsal is far easier to look after than one that was simply switched on.
- Sign off each stage against the diagram
- Keep a short test log
- Rehearse the hardest programme with the real crew
Document it so the crew can rely on it
The last job is the one most often skipped: writing it down. A good handover pack includes the final signal diagram, a list of every source and destination with its label, the settings stored in the mixer and router, and a short note on what to do when each major piece fails. Keep it in plain language and place a printed copy in the gallery as well as a digital one.
Revisit the documents after the first few weeks of live use. Crews will have found shortcuts and small annoyances, and the system should be tidied to match. Labels that nobody uses can be renamed, and a macro that is never pressed can be replaced with one that is. Integration is not finished when the last cable is clipped; it is finished when the people on shift can find what they need quickly and trust that it will work.
- Final diagram and full source and destination list
- Stored settings backed up and dated
- Plain fault notes printed in the gallery
A reliable studio is rarely the result of one clever purchase. It comes from a clear brief, an honest signal diagram, equipment chosen for the people who will operate it, and careful staged testing. Work through those steps in order and each decision becomes easier to defend. If you would like a second pair of eyes on a plan before you commit, get in touch through the contact page and we can talk it through.
