Starting with the cameras instead of the signal path
The most common mistake is also the quietest one. A team arrives, unboxes the camera heads, aims them at the stage and only then asks where the signals will go. By the time the vision mixer, the monitor wall and the recording feeds are discussed, cable runs are already laid in the wrong direction and someone is carrying a spool back across the room.
Draw the path first, on paper if necessary: camera, control unit, mixer, outputs. Count the connections at each stage and note the cable length between them. Many of the faults we are called out for, such as a camera that drops out only when the mixer is switched, come down to a run that was never planned and a connector that was never checked against the one on the other end.
- Sketch every camera from head to mixer input before loading in
- Label both ends of each cable run
- Check connector types against the control unit, not the catalogue
Skipping a proper line-up before the first rehearsal
Cameras that look fine on their own often look wrong side by side. One leans warm, another a touch green, a third has black levels that sit higher than the rest. If nobody matches them before the presenter walks on, the director spends the first rehearsal cutting between mismatched pictures and wondering why the show feels uneven.
Give shading its own slot in the schedule, ahead of rehearsal and with the lighting already set. Point every camera at the same reference, balance white, set black and bring exposure into agreement, then check faces under the actual stage lighting. A quiet half hour here saves a long evening of small corrections, and it gives the operator a baseline to return to when something drifts.
- Line up under the final lighting, not work lights
- Use one shared reference for every camera
- Re-check after any change to the lighting plot
Treating remote heads as if an operator were standing behind them
A remote camera head removes the person from behind the lens, and that changes the job rather than shrinking it. Shots that a handheld operator would adjust without thinking now depend on stored positions, speed settings and a controller that someone must actually be watching. Teams that skip this thinking end up with a lovely wide shot and a close-up that arrives with a lurch.
Spend time on the moves themselves. Store the shots you know you will need, test the speed of each transition, and agree who owns the controller during the show. Set sensible limits so a head cannot swing into a lighting stand or a guest's line of sight. Remote operation rewards preparation more than any other part of a multi-camera job, and it forgives very little improvisation.
- Store and name the key shots before doors open
- Test transition speeds on air-like movements
- Set travel limits near rigging and set pieces
Leaving communication to chance
Intercom is easy to treat as an afterthought, yet it carries the whole production. When the director cannot reach the shader, or the camera operators hear every instruction meant for someone else, small errors turn into visible ones. Crews often pile onto a single channel because it was the quickest to patch, and by the second hour everyone is talking over each other.
Decide who needs to hear whom, and give each group a line of its own. The director and vision mixer need a clear channel, shading and camera control another, and the floor team a third where needed. Test every beltpack and headset before rehearsal, and keep a spare of each to hand. A calm intercom does more for a smooth show than almost any piece of expensive equipment.
- Separate director, technical and floor channels
- Test every headset before rehearsal
- Carry spare beltpacks and a spare headset
Forgetting about the people who will take over
Shows rarely run with the same crew from start to finish. Shifts change, a colleague steps in, or the setup is reused weeks later by a team that never saw the original build. If settings live only in one person's head, the next operator starts from nothing and repeats every mistake already solved.
Keep a short written record of the setup: camera positions, stored shots, shading references, intercom assignments and any quirk worth knowing. Photograph the rack and the patching before breaking down. It takes ten minutes at the end of a long day, which is exactly when it feels least appealing, but it is the single habit that makes a repeat production feel familiar instead of fragile.
- Photograph rack and patching before strike
- Write down stored shots and shading notes
- Note any known quirks for the next crew
Testing the whole chain under show conditions
Individual tests pass, then the full chain fails. A camera works on the bench, the mixer works on its own, and together they produce a flicker nobody can explain. The cause is usually a part of the system that was never exercised with everything else running at once.
Before the audience or the stream goes live, run the complete chain for long enough to see it settle: all cameras powered, all outputs feeding recording and monitors, and the intercom in use. Watch for heat, for dropouts and for anything that changes after twenty minutes. Problems found during a quiet run are an inconvenience, while the same problems found during a broadcast are something the viewer sees.
- Run every camera and output together for a full cycle
- Watch for drift and dropouts after the system warms up
Most camera control trouble is not caused by faulty equipment. It comes from skipped planning, rushed line-ups and settings nobody wrote down. Plan the signal path first, match the cameras under real lighting, treat remote heads as a skill of their own, give the crew clear communication and keep a record for whoever follows. These habits cost very little on the day and spare a production its most avoidable problems.
