Starting without a written signal map
The most common fault I see on multi-camera jobs is simple: nobody has written down where each signal goes. Cameras are patched, the vision mixer shows eight inputs, and the crew relies on memory. It works until someone swaps a cable during a lunch break, and then the director calls for camera three and gets the wide shot from camera five.
A signal map is one page. It lists each camera, its control unit, its return feed, its tally and its input number on the mixer. Keep it taped near the control position and keep a copy with the engineer on the floor. When something changes, change the page first, then the patch.
Treat the map as part of the setup, not as paperwork for afterwards. Ten minutes spent writing it during rigging saves much longer during rehearsal, when every fault looks like a mystery until you can see what is supposed to be connected to what.
- Number cameras and inputs the same way wherever possible
- Record tally and intercom routing on the same page
- Date the page and mark who changed it last
Matching cameras late in the day
Colour and exposure matching is often left until the doors are about to open. By then the lighting has been adjusted, the set has been dressed and everyone is tired. Small differences between cameras then get blamed on the lighting, when the cause is simply that each camera head was left on its own settings.
Do the matching once the lighting is final, and do it under the same light the audience or viewers will see. Use a neutral reference chart in the main playing area, set white balance and black levels on every camera, and then compare shots side by side on one monitor rather than judging each on its own.
Repeat a quick check after any lighting change. A cue that adds warm light to one side of a stage will pull one camera's skin tones away from the rest, and it is far easier to correct that at the control unit than to explain it afterwards.
- Match only after lighting is locked
- Use the same chart position for every camera
- Re-check after major cue or set changes
Overloading the operator at the control position
Remote operation is useful because one person can manage several cameras, but there is a limit. A shader who is also expected to cover tally faults, intercom and recording checks will miss something, usually at the worst moment. The mistake is planning the crew around the equipment rather than around the attention available.
Decide in advance who owns what. One person looks after exposure and colour, another looks after the mixer, and someone has the job of watching the recorded and outgoing feeds. On a small production these may be the same person, but then the show should be simpler: fewer cameras, fewer moves, fewer graphics layered at once.
If you must double up roles, write the priorities down. Knowing that picture quality comes before a cosmetic fix helps a tired operator choose quickly, and it stops small distractions from pulling attention away from the programme output.
- Name an owner for every monitoring task
- Reduce the number of cameras before reducing checks
Ignoring cable runs and latency
Long runs between camera and control room cause quiet trouble. A cable that is slightly too long, a joiner hidden under a flight case or a converter added at the last minute can bring dropouts, delay or noise that only appears once the cameras are moving.
Test every run with the equipment in its final position, not on the workshop bench. Move the cable while watching the picture, because intermittent faults rarely show up on a static test. Where converters or extenders are needed, label them and keep spares of the same type at the control position.
Delay matters too. If remote heads, tally and the return video travel by different routes, the operator may be reacting to a picture that is a moment behind. Check that the lag is small and consistent, and tell the director what to expect when calling fast moves.
- Test runs with cameras in final positions
- Flex cables while watching the picture
- Keep labelled spares for every converter
Skipping the rehearsal of failures
Crews rehearse the show but rarely rehearse what happens when something fails. If a control unit drops out, who takes over its camera? If the mixer needs restarting, what does the director see in the meantime? Without an answer, the first real fault turns into several minutes of confusion.
Pick two or three likely failures and walk through them during the technical rehearsal. Pull a camera feed, switch off a control panel, lose a tally. Watch how the team responds and write down the steps that worked. Keep that list beside the signal map.
The aim is not to expect trouble but to make the response routine. A calm, practised swap to a fixed wide shot looks like a deliberate choice on air, whereas a panicked search through menus looks like exactly what it is.
Leaving settings unsaved and undocumented
After a good setup, many teams forget to save it. Camera presets, mixer memories and panel assignments live only on the equipment, and one power cycle or a borrowed panel later, they are gone. The next job then starts from scratch, repeating the same mistakes.
Save a copy of every configuration at the end of rigging and again at the end of the production. Name files with the date and venue, and store them somewhere other than the device itself. A short note about what was changed and why is worth more than the file alone.
When a studio is used regularly, this record becomes the baseline for the next set of operators. They can see what was tried, what failed and what the director preferred, and they can start from a known good state rather than a guess.
- Export settings at the start and end of each job
- Store notes with the files, not in someone's head
None of these mistakes needs new equipment to fix. A written signal map, matching done at the right moment, sensible roles at the control position, tested cable runs, a rehearsed failure and saved settings all cost time rather than money. Pick the one that worries you most, put it in place before your next multi-camera job, and add the others as the production allows. Small, steady habits make camera control feel quieter, and that is what a good operating team aims for.