Chapter 24 — Key Takeaways
The one-page reference for live, event, and multicam work. Screenshot it before an event. The governing fact of this whole chapter: there is no second take — so everything is decided before the moment arrives.
The five terms
| Term |
One-line definition |
| Event coverage |
Capturing a real, unrepeatable event as it unfolds — no ability to stop, re-stage, or re-run it. |
| Multicamera |
Two or more cameras rolling simultaneously from different angles, so one moment can be cut between angles. |
| Switcher |
A device (hardware or software) that takes multiple live inputs and cuts/dissolves between them in real time. |
| Program feed |
The switcher's single selected output — the "live cut" the audience sees at any instant (PGM). |
| Live streaming |
Broadcasting video and audio in real time over the internet, with no edit between camera and viewer. |
The event mindset (the three pillars)
| Pillar |
What it means |
The habit |
| Run-of-show |
The event's order, in writing, with your must-gets marked |
Get it from the planner/AV lead; script your attention in advance |
| Redundancy |
Two of everything that can fail |
2+ cameras, 2 audio paths, spare batteries/cards |
| Roll early, stop late, never chase |
Moments don't announce themselves |
Start before, hold after; let the other camera catch off-side action |
The one rule: at an event, "we'll fix it in post" is not a joke — it's a disaster. The event is won or lost before it starts.
The multicam angle plan (assign each camera one job)
| Camera |
Role |
Behavior |
Never allowed to… |
| A — Master |
Locked safe wide of the whole scene |
On a tripod; never stops, never reframes |
…reframe or drift — it's the guaranteed record |
| B — Tight |
Close-up on the face / the emotion |
Reframes slowly, only when the subject changes; pre-framed and rolling early on the key moment |
…still be hunting when the moment lands |
| C — Roamer |
Reactions, crowd, details, movement |
Handheld/gimbal; takes risks because A and B hold safety |
…become a second copy of B |
| (Slides) |
Conference presentation feed |
Capture the feed directly, or a clean locked shot of the screen |
…be forgotten — an unreadable talk is useless |
Match across ALL cameras or they won't cut:
| Setting |
Rule |
If mismatched |
| Frame rate |
Identical on every camera (24/25/30 fps) |
Motion won't match — often can't be fixed |
| Shutter |
180° for that rate (1/50 s at 25 fps) |
Different motion cadence per angle |
| White balance |
Manual, one shared value |
Angles are different colors on every cut |
| Exposure |
Matched brightness (judge on the waveform, Ch.5) |
Cuts flash light-to-dark |
| 180° line |
Every camera on ONE side |
Screen direction flips; subject "jumps" sides |
Switch live vs. cut in post
|
Switch live |
Cut in post |
| Deliverable ready |
Instantly, no edit |
After an edit |
| Best for |
Streams, broadcasts, fast turnaround |
Weddings, polished films, precious moments |
| The risk |
A missed cut is permanent |
Almost none — every angle in full |
| You need |
A switcher + total concentration |
Storage for every angle + edit/sync time |
| Safety net |
Also record every ISO angle |
The angles are the safety net |
The synthesis pros use: switch live for immediacy and record every ISO angle for safety. Refuse to choose.
Multicam-in-post sync: give every camera a common sound (room, board feed) and clap once in view of all cameras before you start. Sync by matching audio waveforms (or timecode); modern editors build a synced multicam clip automatically (Resolve → Appendix E; workflow → Ch.27 §27.4).
The live-streaming signal chain
CAMERAS → SWITCHER (program feed) → ENCODER (compress, set bitrate)
→ UPLOAD (test it!) → PLATFORM → VIEWER
└─▶ [LOCAL BACKUP RECORD — always]
| Link |
What kills it |
The fix |
| Encoder |
Bitrate too high for your upload |
Set bitrate to what upload reliably sustains, with headroom |
| Upload |
Upstream speed too low / Wi-Fi saturated |
Test real upload at the venue; prefer wired; carry a cellular backup |
| Platform |
Wrong specs (bitrate, keyframe interval) |
Check the platform's current spec every time (Ch.36 §36.3) |
| Everything |
The stream drops |
Always record the program locally — the disk can't be dropped |
Common streaming starting points (hints, not gospel — defer to the platform's current spec and your tested upload): 1080p30 ≈ roughly 4.5–6 Mb/s; keyframe every ~2 s; protocol usually RTMP (or SRT for shaky connections). Free path: OBS Studio switches and streams.
Event audio: the board feed
VENUE BOARD ──(ask for a MULT/SPLIT)──▶ YOUR RECORDER [board feed = PRIMARY]
+ scratch/room mic on every camera
[= BACKUP + sync reference]
▲ monitor on headphones the WHOLE time — a board feed fails silently
| Do |
Why |
| Take the board feed as primary |
It's maximum proximity — borrows the venue's close mics; cleanest source in the building |
| Ask for a mult/split |
So your copy doesn't affect the AV team's house mix |
| Keep a scratch/room mic on every camera |
Backup if the board dies + the common track that syncs your angles |
Monitor on headphones, watch levels (headroom below 0 dBFS) |
The board feed's only failure mode is silent — a dead channel you don't hear |
| No board? Get your own mic close (lav/recorder) |
Proximity beats every other audio trick (Ch.14–15) |
The wedding & conference playbooks
|
Wedding |
Conference |
| Feeling |
Emotional, sacred, one-take, high-stakes |
Controlled, scheduled, content-heavy |
| Cameras |
2+; locked wide never touched + tight on faces |
Standardized rig: wide master + tight + slides |
| Method |
Cut in post (safety > immediacy) |
Often live-streamed; cut or switch |
| Must-gets |
Processional, vows, rings, the kiss (wide and tight), recessional, reactions |
Speaker clean, readable slides, Q&A, lower-thirds |
| Audio |
Lav on officiant/groom + board if available |
Board feed (speakers already miked) |
| Business |
Contract + releases (Ch.38); manage expectations |
Volume, reliability, fast turnaround, captions |
Top common mistakes → fixes
| Mistake |
Fix |
| One camera on a two-person moment (the wedding trap) |
Two cameras: locked wide + tight; roll both early |
| Both cameras drift to the same shot |
Assign roles and hold them; the master never reframes |
| Crossing the 180° line with a camera |
Keep every camera on one arc/side; walk the line in setup |
| Mixed frame rates / auto white balance |
Match frame rate and set manual WB identically |
| Streaming with no local recording |
Always record the program to disk |
| Assuming venue Wi-Fi will carry the stream |
Test real upload; go wired; carry a backup path |
| Board feed as your only audio |
Always keep a scratch/room mic rolling too |
| Not monitoring the board feed |
Headphones on, meters watched, the whole time |
| Cutting on the announcement, not the reaction |
Cut on the emotion; hold long enough to breathe |
The craft principles (why any of this matters)
- Fix it in pre, not in post (Theme 5), at its extreme: an event has no post-rescue for a moment you weren't rolling on.
- You shoot for the edit (Theme 3): matched, synced, ISO-recorded angles are you handing the edit every choice.
- Sound is half the picture (Theme 2): the audio of a vow or speech is a single fragile thing — board feed + backup, monitored.
- Story is the boss (Theme 1): cut to the moment, not the machinery; the master exists to protect the story, not to dazzle.
The project increment (Production Checkpoint)
Capture (or plan and storyboard) a multicam/event element — two angles of one moment you could cut together — and write the sync and audio plan. A locked master + a tight, matched to cut, rolling before the moment; note how you'll sync (a clap / matching waveforms → Ch.27) and where audio comes from (board feed? close mic? on-camera scratch backup?). It advances Project 2/3 and, later, your reel (Ch.39).
Remember: two phones and a clap is a real multicam rig. The number of cameras never changed the thinking — and the thinking is the craft.