Chapter 24: Live, Event, and Multi-Camera Production

Overview

Two videographers cover the same wedding. Same church, same afternoon light, same couple. As the ceremony reaches the vows, the first videographer is standing in the aisle with a single camera, and at the exact moment the bride's voice catches and she wipes her eyes, that camera is pointed at the groom — because the operator, sensibly, wanted his reaction, and had no way to know she would break first. By the time they swing back, the moment is gone. It happened once. It will never happen again. The second videographer has two cameras locked off before the processional even starts — one holding a clean wide of the whole altar, one tight on the couple's faces — plus a third small camera on the officiant. When the bride's voice catches, all three are already rolling. In the edit, they cut from the wide to the tight and hold on her face through the whole trembling breath. One videographer got the wedding. The other got footage of a wedding, minus the one shot the couple will actually cry over for the next fifty years.

Nothing separated them but preparation and a second camera. That is this entire chapter. Live and event work — weddings, conferences, concerts, ceremonies, streams, anything that unfolds in real time in front of a real audience — is a different discipline from everything you have practiced so far, and the difference is one brutal fact: there is no second take. You cannot ask the bride to cry again. You cannot re-run the keynote. You cannot say "cut, reset, let's go from the top" when the founder's face crumples at the surprise award. The moment happens once, at full speed, whether or not you were ready — and being ready is the whole job.

Everything you have learned still applies: you frame (Chapters 6–7), you light or expose for what the room gives you (Chapters 5, 13), you record clean sound (Chapters 14–15), you run the day (Chapter 18). But live work bends all of it toward one goal — survive the one take — and it adds three tools that make survival possible: more than one camera, a way to choose between them, and a plan detailed enough that the thinking is already done before the moment arrives. This chapter is where preparation stops being a virtue and becomes the only thing between you and disaster.

Think of it as the opposite of the Café Scene. That scene you built and rebuilt across the whole book — frame it, re-light it, re-shoot it, re-cut it — because it was yours to control and repeat. An event is the Café Scene's mirror image: you get one pass, at a speed you don't set, and your only power is the power you brought with you in the plan.

In this chapter you will learn to:

• Adopt the event mindset — treat event coverage as a one-take discipline built on planning and redundancy, not reflexes.
• Design multicamera coverage: give every camera a distinct angle and job, and match them so they actually cut together.
• Decide between switching a show live on a switcher (producing a program feed in real time) and recording every angle to cut later in post.
• Build a live streaming signal chain, end to end, with a local backup record you will thank yourself for.
• Run the two jobs that pay — weddings and conferences — and get event audio clean from the board feed.

Learning Paths

This is the most "one-take, high-stakes" chapter in the book, and it is where a lot of people first get paid. Weight your reading to your path:

• 📱 Phone-first: you can do real multicam and real streaming with phones. §24.2 (two-phone coverage), §24.3 (a free software or phone-app switcher), and §24.4 (going live) are written so a two-phone shooter can execute the whole chapter. Don't skip §24.1 — the mindset is the gear that matters most.
• 🎥 Creator: §24.4 (the streaming signal chain) is your chapter — going live is a core creator skill — and §24.3 shows you how to switch a multi-angle stream instead of staring into one lens for an hour.
• 💼 Pro-track: all of it, cold. Weddings and conferences (§24.5) are the bread-and-butter of paid videography, and the board feed (§24.6) is the difference between a professional deliverable and an amateur one. This is money-work; learn the redundancy discipline like your business depends on it, because it does.
• 🎓 Student: §24.1 and §24.2 are the exam — the mindset and the coverage logic. Case Study 1 (the birth of multicam) is your analysis anchor; Case Study 2 walks a full event shoot end to end.

24.1 The event mindset: you only get one take

Every skill in this book so far has quietly assumed you could try again. A soft-focus take? Roll another. Muddy audio? Reset the mic and go from the top. A cut that doesn't work? Try a different one. That assumption — the safety net of the retake — is the thing an event removes, and removing it changes everything about how you work.

Let us name the discipline plainly. Event coverage is the craft of capturing a real, unrepeatable event — a wedding, a ceremony, a conference, a concert, a graduation, a live broadcast — as it actually unfolds, with no ability to stop it, re-stage it, or ask for another take. The subject is not a performer you direct; it is reality happening on its own schedule, and your job is to be positioned, exposed, focused, rolling, and recording clean sound before each moment arrives, because you will never get a second chance at any of them. Event coverage is less like directing and more like goalkeeping: most of the job is anticipation and positioning, and the save has to be made in the half-second the ball is actually on you.

This is why the event mindset inverts the usual relationship between planning and shooting. On a controlled shoot, the plan is a convenience — a way to make the day efficient. On an event, the plan is the entire performance, because during the event itself you have almost no time to think. Everything you did not decide in advance, you will be deciding in a panic while the moment you came for slips past. The professional truth of live work is uncomfortable and freeing at the same time: the event is won or lost before it starts. You already know this idea — it is Theme 5, fix it in pre, not in post — but events take it to its absolute extreme. There is no post-production rescue for a moment you were not rolling on. There is only the plan.

🚪 Threshold Concept: there is no second take. Once you truly internalize that an event offers exactly one pass, your whole way of working reorganizes around it. You stop trusting that you'll "get it on the next one," because there is no next one. You start building redundancy into everything — two cameras so one covers while the other reframes, two audio sources so a dropout doesn't cost you the vows, spare batteries and cards so a dead one doesn't end the day. You start rolling early and stopping late, because the moment never happens on your cue. And you start scripting your own attention in advance — deciding, before the event, which moments you cannot miss — because in the moment there is no time to decide. This single shift is what separates people who can be trusted with a once-in-a-lifetime event from people who own nice cameras. The stakes are real: a wedding is not a genre where "we'll fix it in post" is a joke. It's a genre where it's a lawsuit.

The three pillars of the event mindset — the things that let you survive the one take — are these:

A run-of-show. Borrow the producer's document from Chapter 18 (§18.2) and sharpen it. Every event has an order: processional, readings, vows, rings, kiss, recessional; or doors, welcome, keynote, panel, Q&A, awards, close. Get that order in writing from whoever is running the event — the wedding planner, the officiant, the event's AV lead — and build your shot plan against it, minute by minute, marking the two or three moments you absolutely cannot miss. This is the run-of-show, and it is your script for a thing you don't control. When you know the kiss comes right after "you may now," you are framed and rolling on the couple before the officiant finishes the sentence.

Redundancy, everywhere. In controlled work, a backup is prudent. In event work, a backup is mandatory, because the failure you didn't back up against is a failure with no remedy. Two cameras minimum, so that at any instant one is holding a safe, usable frame while the other hunts for reactions or resets. Two audio paths, so a wireless dropout or a bumped cable doesn't erase the speeches. More batteries and cards than you could possibly need. A camera that dies mid-ceremony is a catastrophe only if it was your only camera.

Roll early, stop late, and never chase. The amateur reflex is to start recording when the moment starts and stop when it ends — which guarantees you miss the beginning of everything, because moments don't announce themselves. The professional habit is to roll before and hold after: start the camera as the couple reaches the altar, not when the vows begin; keep rolling through the hug after the award, because the real reaction often comes a beat late. And when something happens off to your side, resist the instinct to whip the camera at it — a violent chase produces unusable footage and abandons the frame you had. That is exactly what the second camera is for.

You already watched this mindset pay off. In Chapter 18 (FIGURE 18.8), a well-run crew caught the bakery owner's face at the instant she realized a community award was hers — because a PA had whispered "award in two minutes," the operator was already framed and rolling, exposure was locked earlier for that spot, and sound had run a cable to the board. That shot was not luck; it was the event mindset producing its one guaranteed result. This chapter takes that same gala and asks the next question: what if one camera on that moment isn't enough? What if you want her face and the crowd's gasp and a clean wide, all cuttable together? That is multicam, and it's where we go next.

🔄 Check Your Eye. 1. In one sentence, what is the single fact that makes event coverage different from every other kind of shoot? 2. Name the three pillars of the event mindset. 3. Why does the event mindset demand redundancy in a way a controlled studio shoot doesn't?

Check yourself

1. There is no second take — the event happens once, at its own speed, and cannot be stopped, re-staged, or re-run.
2. A written run-of-show (the event's order, with your must-get moments marked); redundancy everywhere (two cameras, two audio paths, spare power/cards); and roll early, stop late, never chase.
3. Because a failure you didn't back up against has no remedy — you can't reshoot. In the studio a dropped shot is a retake; at an event it's gone forever, so a second camera, a second mic, and spare power aren't luxuries, they're the only insurance that exists.

24.2 Multicamera coverage and angles

The answer to "there is no second take" is to point more than one camera at the moment, so that no single reframe, refocus, or mistake can lose it. Let us define the tool. Multicamera (or "multicam") shooting is capturing the same event or subject with two or more cameras running simultaneously from different angles, so that in the edit — or live, on a switcher — you can cut between angles of a single continuous, unrepeatable moment. It is the defining technique of event work, and its logic is simple: if one camera is always holding a clean, safe frame, you are free to let another camera take risks, reframe, and hunt for the reactions that make a piece feel alive — and you can cut them together because they are the same moment seen from two places at once.

The mistake beginners make is to think multicam means "two cameras getting the same shot." It's the opposite. Multicam is coverage, the concept you learned in Chapter 7 (§7.5) — a wide, a medium, a close-up, a detail — except that at an event you can't get them one at a time by re-shooting, so you get them all at once by running several cameras, each assigned a different size and job. The single most important act of multicam planning is therefore assigning each camera a role and, as much as possible, holding it there. Cameras that each own a distinct job give you a cuttable scene; cameras that all drift toward the same framing give you three copies of one shot and nothing to cut to.

Here are the standard roles, using the event/room anchor — the nonprofit's fundraising gala from Chapter 18, now covered properly with three cameras:

FIGURE 24.1 — Multicam coverage of a stage event (top-down): three cameras, three jobs

                        [ STAGE ]     ▽ house wash (venue's own light)
              ┌───────────────────────────────────┐
              │   ( podium )        ( award table )│
              │       ( S )  ← speaker              │
              └───────────────────────────────────┘
   ================ the 180° line (front edge of stage) ================
                        ((•  board feed from the venue mixer (audio, §24.6)
        [CAM C]                                        the audience
        roaming ⇄        · · · · · · seating · · · · · ·
        reactions,       [ guests ]   [ guests ]   [ guests ]
        cutaways
                              [CAM B]                 [CAM A]
                           tight / punch-in         wide MASTER
                           on the speaker's face    locked, whole stage
                           (from house left)        (dead center, back)

   CAM A = the MASTER: a locked, safe wide of the whole stage. Never stops, never
           reframes. This is your safety — if everything else fails, you have a show.
   CAM B = the TIGHT: a close-up on the speaker's face / the lectern. The emotion.
           Reframes slowly between speakers; the operator watches the podium.
   CAM C = the ROAMER: handheld/gimbal, hunting reactions, applause, the award, details.
           This is the camera allowed to take risks, because A is holding the safety.
   ALL THREE stay on ONE side of the 180° line (Ch.7 §7.3) so the stage's screen
   direction never flips between angles. Cross it and the cut will feel "wrong."

Read the roles as a hierarchy of safety. CAM A, the master, is sacred: a locked-off wide (Chapter 8, §8.1) of the entire stage that never stops rolling and never reframes. It is boring on purpose. It is also the shot that saves the entire event, because as long as A is running, you have a complete, usable, if unglamorous, record of everything that happened — and every other camera is now free to fail. CAM B, the tight, lives on the emotion: a close-up on the speaker's face, reframing slowly and only when the subject changes. CAM C, the roamer, is the one that makes the piece feel alive — handheld or on a gimbal (Chapter 8, §8.4), moving through the room for reaction shots, the gasp when the award is announced, applauding hands, the detail on the table. C is allowed to be caught mid-move or briefly out of focus precisely because A and B are holding safe frames underneath it.

Now the rule that decides whether your angles will actually cut together, and it is the one most first-time multicam shooters break: the 180-degree line applies across all your cameras at once. You learned the line in Chapter 7 (§7.3) and how crossing it breaks a scene in Chapter 9 (§9.2). At an event, the "line" runs along the front of the stage (or between the two people at the altar), and every camera must stay on the same side of it. Put CAM A on the audience's side and CAM C behind the stage shooting back toward the crowd, and when you cut from A to C the speaker will suddenly appear to face the wrong way — the podium that was on frame-left is now on frame-right, and the audience feels a lurch they can't name. Keep all your cameras in the same broad arc, on one side of the line, and every angle cuts cleanly against every other.

🎞️ Read This Sequence. Add this to your Watch This shelf: a genuinely famous, genuinely once-only live moment, covered multicam. It is the purest illustration in the chapter of "you only get one take."

FIGURE 24.2 — "The rooftop concert"        [after the Beatles' rooftop concert, 1969]
  THE FRAME    A band plays live and unannounced on a London rooftop on a cold January day. Coverage
               is spread across positions: cameras up on the roof for the musicians in tight and wide;
               cameras down in the street for the crowd craning up; a camera in the building lobby.
  THE MOVE     A mix — locked wides on the roof, roving handheld among the players and down in the
               street. The roving cameras hunt reactions; a wide always holds the whole performance.
  THE LIGHT    Flat, grey, available daylight. Nobody lit it; there was no time and no second chance.
               The exposure had to be right the first time, because there was no first-time rehearsal.
  THE SOUND    The live performance itself, plus the sound of a city reacting — and, famously, the
               police arriving to shut it down. The audio is the event; it could not be recreated.
  THE CUT      In the edit, the angles interweave — the band, the baffled and delighted crowd below,
               the street — because all of it was captured *simultaneously.* One performance, many views.
  THE EFFECT   We feel we are *there,* at a thing that happened exactly once and was never repeated —
               the band's last public performance, ended by the authorities mid-song.
  THE LESSON   An unrepeatable live moment is only "coverable" if you run several cameras at once. The
               reactions, the wide, and the detail are the *same* moment from different places — which
               is the entire definition of multicam, and the only way to edit a thing you can't reshoot.

Everything about that rooftop is the chapter in miniature: one take, available light, sound you can't recreate, and — the reason any of it can be edited — multiple cameras rolling at once, so the performance, the crowd, and the street are all the same minutes seen from different angles. (Specific camera placements are rendered here as the sequence is widely described, not as verified fact.)

There is one more discipline that separates multicam that cuts from multicam that clashes: matching your cameras before you roll. Two angles will only cut together seamlessly if they look like the same event, and that means matching four things across every camera: the frame rate (all on 24 fps, or all on 25/30 — never mixed, or motion won't match), the shutter (all following the 180° rule for that frame rate — Chapter 2, §2.4), the white balance (all set to the same manual value — Chapter 12 — so one camera isn't warm and the next cold), and the exposure (matched brightness, judged on the waveform from Chapter 5, so the cut doesn't flash light-to-dark). A minute spent matching settings across your cameras before the event saves hours of fighting in the grade — and some mismatches (a frame-rate mix especially) can't be fully fixed at all.

💡 Why It Works: matched cameras let the moment survive the cut. When you cut between two angles of the same instant, you want the viewer's attention to stay on what's happening — the vow, the gasp, the winning point — and never snag on the machinery. A jump in color temperature, brightness, or motion cadence between angles does exactly that: it announces "you are now watching a different camera," which yanks the audience out of the moment. Matching frame rate, shutter, white balance, and exposure makes the seam disappear, so a three-camera edit reads as one continuous event witnessed from three places rather than three separate videos stapled together. The technical discipline exists to protect the emotional continuity. That is the whole point of multicam, and it is Theme 3 — you shoot for the edit — applied to several cameras at once.

⚠️ Common Mistake: two cameras, one shot (and the crossed line). The two classic multicam failures both come from not assigning roles. The first is redundant coverage — both operators, drawn to the emotion, end up in the same tight shot of the same face, so the edit has two versions of one angle and no wide, no reaction, nothing to cut to. The fix is discipline: A holds the wide no matter how tempting the close-up is, and each camera stays in its lane. The second is crossing the line — placing cameras on opposite sides of the stage or the couple, so cuts between them flip screen direction and the space falls apart. The fix is to keep every camera in one arc, on one side of the 180° line, and to walk that line during your setup (the recce — Chapter 16, §16.6) before a single guest arrives.

🔄 Check Your Eye. 1. What is the job of the "master" camera in a multicam setup, and why must it never reframe? 2. Name the four settings you must match across all cameras so their angles cut together. 3. Why does the 180-degree line matter more in multicam than in single-camera work?

Check yourself

1. The master is a locked, safe wide of the whole scene that never stops and never reframes; it's your guaranteed usable record of the entire event, which is what frees every other camera to take risks. If it reframes, you lose the one shot that can't fail.
2. Frame rate, shutter (the 180° rule for that frame rate), white balance, and exposure/brightness. Mismatches make the cut flash or the motion stutter; a frame-rate mismatch especially can't be fully fixed later.
3. Because in multicam you cut between angles of the same moment, so a crossed line flips screen direction within a single continuous event — the speaker or couple appears to jump to the opposite side on the cut. In single-camera you at least control one viewpoint at a time.

24.3 Switching live vs multicam in post

You have several cameras rolling. Now comes the defining decision of live production: when do you choose which angle the audience sees — in the moment, or afterward? There are two complete philosophies, and picking the right one for the job is half of directing live.

The first philosophy is to switch live. Here you feed every camera into one device and cut between them as the event happens, producing a single finished output in real time. That device is a switcher (also called a vision mixer): a piece of hardware or software that takes multiple live camera inputs and lets you cut, dissolve, or wipe between them instantly, sending out one selected feed. That selected output — the "live cut," the single stream of what the audience is seeing at this instant — is the program feed (often labeled PGM or program). Most switchers also give you a preview (PVW): a second monitor showing the angle you're about to cut to, so you can line up the next shot before you take it. The rhythm of live switching is preview it, then take it — you set up the next camera on preview, and on the beat you want, you take it to program, and that's what goes out. Switch live and the show is done the instant the event ends: no edit, the program feed is the finished video.

The second philosophy is to record everything and cut later — often called multicam in post. Here every camera simply records its own angle to its own card, in full, start to finish, and you make no live cutting decisions at all. Later, in the edit, you line up all the angles in sync (by their audio, or by timecode) and cut between them at your desk, with the luxury of hindsight, rewind, and as many attempts as you want. This is the sitcom method, the wedding-film method, the method behind almost every polished multicam piece that isn't a live broadcast. It trades the immediacy of a finished live show for control — you're never forced to guess the cut in real time, and you can't miss a cut, because you have every angle in full and choose at leisure.

Neither is "better"; they answer different needs. Here is the trade-off, and it is the thing to actually understand:

Look closely at that last row, because it is the professional habit that reconciles the two philosophies: even when you switch live, record every camera's isolated feed too. An "ISO" (isolated) recording is each individual camera's own full-length angle, captured to its own card independent of the live cut. It costs you nothing but storage, and it means a live switching mistake — cutting to CAM B a half-second before the kiss, missing the gasp because you were on the wide — is recoverable in post, because you still have every angle in full. The rule: switch live for the deliverable, but never let the live program be your only record. Roll ISOs on everything. It's the redundancy pillar from §24.1 applied to switching.

FIGURE 24.3 — Two philosophies for a multicam event (same cameras, different decision point)

  SWITCH LIVE                                   CUT IN POST
  ───────────                                   ───────────
  CAM A ─┐                                       CAM A ──▶ [card A: full angle]
  CAM B ─┼─▶ [SWITCHER] ─▶ PROGRAM FEED ─▶ out   CAM B ──▶ [card B: full angle]
  CAM C ─┘      │  ▲        (the live cut)        CAM C ──▶ [card C: full angle]
               PVW │  cut/dissolve NOW                          │
          (also record each ISO angle!)                        ▼
                                                  [EDIT: sync all angles, cut at leisure]
   Decision made:  IN THE MOMENT                   Decision made:  LATER, WITH HINDSIGHT
   Output ready:   IMMEDIATELY                     Output ready:   AFTER THE EDIT

✂️ In the Edit: multicam in post is a sync problem first. When you choose to cut in post, your edit begins with a task you must plan for on set: getting three (or five) separate angles to line up perfectly in time so that when you cut between them, lips still match voices. The clean way is to give every camera something to sync to — a common sound. If every camera's on-board mic hears the same room (or, best, the same board feed), your editor can line the angles up by matching their audio waveforms; if your cameras support timecode, they can be jam-synced to line up frame-accurately. Modern editors automate this: you select all the angles and the software builds a synced "multicam clip" you can cut live-style at your desk — in DaVinci Resolve it's a multicam clip synced by audio or timecode (see Appendix E; the full ingest-and-sync workflow is Chapter 27, §27.4). The set habit that makes it painless: clap once, loudly, in view of every camera before the event starts — the same self-slate reflex from Chapter 18 (§18.3). That one clap is a spike every camera hears and sees, and it's the anchor your sync hangs on. Skip it and you're aligning angles by eye, frame by frame, which is exactly the archaeology you learned to avoid.

🎒 Gear Note: the switcher ladder (a principle, not a purchase). A switcher is a function, not a specific box, and it comes at every price including free. From most elaborate to most accessible: a hardware switcher (a dedicated unit with physical buttons and multiple video inputs — fast, reliable, what live-broadcast and event pros use); software switchers (free programs that turn a laptop into a full switcher and streamer — OBS Studio is the standard free one, and it both switches and streams); and phone/tablet apps that let two or more phones feed one phone acting as the switcher over Wi-Fi. The phone-first truth: you can run a real two- or three-camera live switch with phones and a free app, or you can skip live switching entirely and simply record each phone's full angle to cut in post — which needs no switcher at all, just two phones on two tripods and a clap to sync them. Do not buy a hardware switcher to shoot a wedding; wedding films are almost always cut in post precisely because quality beats immediacy there. Buy the switcher only when the job genuinely must be live.

🔄 Check Your Eye. 1. Define "switcher" and "program feed" in one sentence each. 2. What is the single biggest risk of switching live, and what habit makes it recoverable? 3. When would you choose to cut in post rather than switch live?

Check yourself

1. A switcher is a device (hardware or software) that takes multiple live camera inputs and lets you cut/dissolve between them in real time; the program feed is its selected output — the single "live cut" the audience sees at any instant.
2. A missed cut is permanent — you can be on the wrong camera at the key moment with no do-over. Recording every camera's ISO (isolated) angle in full makes it recoverable in post.
3. When quality matters more than immediacy and there's no requirement to be live — weddings, polished event films, anything you'll deliver as an edited piece. You record every angle in full and cut at leisure.

24.4 Live streaming: the signal chain

Sometimes the deliverable is the live event, sent out over the internet as it happens — a streamed conference, a webinar, a concert, a service, a creator going live. This is live streaming: broadcasting video and audio in real time over the internet to viewers who watch it as it happens, with no edit between the camera and their screen. Streaming raises the stakes of everything in this chapter one more notch, because now there is not only no second take — there is no edit at all. Whatever leaves your switcher goes straight to the audience, mistakes and all. Which means the whole game is the signal chain: the ordered path your picture and sound travel from the cameras to the viewer, and every link in it that can fail.

Walk the chain from left to right, because if you understand it as a chain you can find the weak link before it breaks on you live:

FIGURE 24.4 — The live-streaming signal chain (cameras → switcher → encoder → viewer)

  CAMERAS          SWITCHER            ENCODER              INTERNET        PLATFORM     VIEWER
  ┌──────┐                                                                                       
  │CAM A │─┐                                                                                      
  ├──────┤ │   ┌──────────┐        ┌───────────────┐       ┌──────┐      ┌─────────┐    ┌──────┐
  │CAM B │─┼──▶│ SWITCHER │──PGM──▶│   ENCODER      │──────▶│UPLOAD│─────▶│ STREAM  │───▶│phones│
  ├──────┤ │   │ (PGM/PVW)│  video │ compress to    │ RTMP/ │ (your│      │ SERVICE │    │ TVs, │
  │CAM C │─┘   └────┬─────┘        │ H.264/H.265    │ SRT   │ up-  │      │(re-sends│    │ etc. │
  └──────┘         audio│          │ + set bitrate  │       │ load)│      │ to all) │    └──────┘
   BOARD ((• ───────────┘          └───────┬───────┘       └──────┘      └─────────┘
   feed (§24.6)                            │
                                  ┌────────▼─────────┐
                                  │  LOCAL BACKUP    │  ◀── ALWAYS record the program
                                  │  RECORD (to disk)│      to disk too. The stream can
                                  └──────────────────┘      drop; the local file can't.

  Every ARROW is a link that can fail. The two that fail most: the UPLOAD (your internet
  isn't fast or stable enough) and the ENCODER settings (bitrate too high for your upload).

Three links deserve your attention because they are where streams actually die.

The encoder is the piece — usually software, sometimes a dedicated box — that takes your program feed and compresses it into a stream small enough to send over the internet, using a delivery codec like H.264 or H.265 (the codecs you met in Chapter 3) at a bitrate you choose. Bitrate is the crucial dial: too low and the stream looks blocky and smeared; too high and it exceeds your upload speed and the stream stutters, buffers, and drops. The art of streaming is setting a bitrate your internet connection can reliably sustain with room to spare — not the highest number your picture would like, but the highest number your upload can carry all day without choking.

The upload is your internet connection's upstream speed, and it is the link beginners never check until it's too late. Streaming uses upload bandwidth, which on most home and venue connections is a fraction of the download speed you're used to — and it must comfortably exceed your chosen bitrate, or the stream falls apart. The professional habit is to test the actual upload at the actual venue, on the actual connection, before the event, and whenever possible to run on a wired connection rather than Wi-Fi, because Wi-Fi at a crowded venue competes with three hundred guests' phones. For anything that truly matters, carry a backup path to the internet (a second connection, or a cellular hotspot) the way you carry a spare battery.

The platform is the streaming service that receives your single uploaded stream and re-sends it out to all your viewers at once. You send it one feed, usually over a protocol called RTMP (or the more resilient SRT), and the platform handles distribution. Each platform publishes its own required specs — resolution, frame rate, bitrate range, keyframe interval — and those specs change, so you check the current ones every time (this is the same platform-spec discipline you'll formalize for delivery in Chapter 36, §36.3, and for vertical/social platforms in Chapter 23).

And underneath all of it, the one rule that turns a streaming disaster into a mere inconvenience: always record the program locally, to disk, at the same time you stream it. The internet can drop; a plug can be kicked; the platform can hiccup. A local recording of your program feed can't be taken from you by a bad Wi-Fi signal. When the stream fails — and someday it will — the local file means you still have the whole event to deliver afterward. This is the redundancy pillar again: the stream is the deliverable, but it is never your only copy.

🔬 The Tech: bitrate, keyframes, latency, and protocols. (Skippable — the practitioner flow never depends on this box.) A stream is a constant flow of compressed data, and a few numbers govern it. Bitrate (in Mb/s or kb/s) is how much data per second you send; higher is sharper but demands more upload. A widely published starting point for 1080p at 30 fps is roughly 4.5–6 Mb/s, but treat that as a hint and defer to your platform's current recommendation and your tested upload — never assume. The keyframe interval is how often the codec sends a full "anchor" frame that the compression rebuilds from; live platforms commonly want one every 2 seconds, and getting this wrong is a frequent cause of a stream the platform rejects or stalls. Latency is the delay between the real moment and the viewer seeing it — usually several seconds — which matters if you're taking live audience questions. And the protocol is the language your encoder speaks to the platform: RTMP is the long-standing common one; SRT is a newer protocol built to survive unreliable connections. You do not need to master any of this to stream — a free tool like OBS Studio ships with sane defaults — but knowing the chain's vocabulary is how you diagnose a sick stream instead of panicking at it.

⚠️ Common Mistake: no local backup, and an untested upload. The two failures that ruin streams are both preventable in pre-production. The first is streaming with no local recording, so when the connection drops for ninety seconds, that ninety seconds is simply gone — unrecorded, unrecoverable, in the middle of the keynote. Always record the program to disk. The second is showing up and assuming the venue Wi-Fi will carry your stream. It won't; conference Wi-Fi is saturated and hotel upload is throttled. Test the real upload on the real connection days ahead, prefer a wired line, carry a cellular backup, and set your bitrate to what the connection reliably sustains, not what you wish it would. Fix it in pre — because a stream has no post.

♿ Accessibility & Inclusion: a live event is still for everyone. Live doesn't excuse you from access — it just means you plan it in advance. Live captions (real-time captioning, whether by a human captioner or an automated service the platform offers) make a stream usable for deaf and hard-of-hearing viewers and for the large share of people watching with sound off; enable and test them before you go live. If your event has any flashing lights, strobes, or intense stage effects (concerts especially), that is a genuine photosensitivity hazard — warn viewers and keep any strobing you control within safe limits. And at real-world events with real people, consent still applies: guests, audience members, and speakers should know they may be on a public stream, and anyone identifiable in a deliverable needs the release you'll formalize in Chapter 38 (§38.4). Reachable video is finished video — on a stream just as much as in an edit.

🔄 Check Your Eye. 1. Which link in the streaming signal chain do beginners most often fail to check, and why does it break the stream? 2. What is the one rule that turns a dropped-stream disaster into a mere inconvenience? 3. Why set your bitrate to what your upload "reliably sustains" rather than the highest quality your picture wants?

Check yourself

1. The upload — streaming uses upstream bandwidth, which is usually far smaller than download speed, and if it doesn't comfortably exceed your bitrate the stream stutters and drops. Test the real upload on the real connection before the event.
2. Always record the program locally to disk while you stream. If the connection drops, the local file still has the whole event to deliver.
3. Because a bitrate above your reliable sustained upload will choke the connection and make the stream buffer and drop — a stuttering stream is far worse than a slightly softer one that plays perfectly. Leave headroom.

24.5 Weddings and conferences: the playbook

Two kinds of event pay the bills for most working videographers, and they are near-opposites in feeling: the wedding, an emotional, unrepeatable, high-stakes ceremony where the moments are sacred and the clients are living the most important day of their lives; and the conference, a controlled, scheduled, content-heavy business event where reliability and clean deliverables matter more than art. Master both and you have a livelihood. Here is the playbook for each — the specific, hard-won discipline that a general "event mindset" turns into on the day.

The wedding. A wedding is the ultimate one-take job, and its danger is emotional as much as technical: you are not covering an event, you are preserving the only record of the most emotionally significant day in two people's lives, and there is no version of "we'll fix it in post" that survives contact with a bride who wanted to see her own vows. So the wedding playbook is redundancy taken to its limit. The ceremony gets a minimum of two cameras, both locked and rolling before the processional: a wide master holding the whole altar (never touched — your safety) and a tight on the couple's faces. A third camera, if you have it, covers the officiant or catches the guests. You get the run-of-show from the couple or planner and you mark the untouchable must-gets, because these are the shots that, missed, cannot be re-created:

FIGURE 24.5 — The wedding ceremony must-get list (the shots you cannot miss, in order)

   MOMENT              WHO COVERS IT            WHY IT'S SACRED
   ──────              ─────────────            ───────────────
   Processional        wide + tight on aisle    the entrance happens once, walking one way
   The vows            TIGHT on each face        the emotional core — often where they break
   Ring exchange       tight/detail on hands     small, fast, easy to miss — pre-frame it
   The first kiss      wide AND tight, rolling   THE shot; if you miss it, there is no reshoot
   The recessional     wide, hold it long        joy and release; hold past the exit
   Reactions           roamer / 3rd camera       parents' tears, the crowd — the story around it

The wedding's cruelest trap is the one from this chapter's opening: a single camera cannot cover a two-person emotional exchange, because the emotion jumps between two faces and the camera can only be on one. The kiss and the vows demand multicam — a wide that can never miss plus a tight that catches the tears — which is exactly why weddings are shot on two-plus cameras and almost always cut in post (§24.3): quality and safety beat immediacy when the stakes are a lifetime. And because a wedding is a business transaction wrapped around a sacred day, the contract matters as much as the coverage — what you'll deliver, how many cameras, how long the edit, what happens if gear fails — which is the client-and-release work you'll formalize in Chapter 38 (§38.2, §38.4).

The conference. A conference is the calmer, more controlled cousin, and its virtues are reliability and volume: many sessions, clean audio, readable slides, fast turnaround, often a live stream. The conference playbook is built around the stage-event coverage you diagrammed in FIGURE 24.1 — a locked wide master of the stage, a tight on the speaker, and (crucially) a way to capture the slides cleanly, either by pointing a camera at the screen or, far better, by taking the presentation feed directly. Conferences reward standardization: because session after session has the same shape (speaker at a lectern, slides behind, Q&A at the end), you set one reliable multicam rig and run it all day, and you take audio from the venue's board (§24.6) because the speakers are already miked into the house system. Conferences are also where live streaming (§24.4) most often shows up as a paid deliverable, and where lower-thirds naming each speaker (Chapter 34) and clean, captioned exports (Chapter 36) make the difference between amateur and professional.

🎬 On Set: cover a two-person moment you cannot reshoot. Stage a small "event" you only get one pass at — a mock toast, an interview exchange, someone opening a gift, two people in conversation — and cover it as a real multicam event. Constraint: two cameras minimum (two phones is perfect), rolling before the moment starts. Camera A is a locked wide of both people (your master — it never moves). Camera B is a tight on faces. Clap once in view of both cameras before you start, so you can sync them. Do not stop and restage; treat it as one take. Self-review question: in the edit, could you cut between your two angles on the key beat — the laugh, the reaction, the tears — and did the cut land on the emotion, or did you discover the tight camera was on the wrong face? That gap between "I had two angles" and "I had the right two angles rolling at the right moment" is the entire craft of event coverage. Add this week's Frame Log entry: watch any live broadcast or event video and count the cameras — how many angles can you spot, and which one is the "safety" wide?

🔗 Connection: the event is also a client, a contract, and a license. Weddings and conferences are where craft meets business hardest. What you promise to deliver, how many cameras and hours, your backup obligations, and what happens if a card fails are contract questions (Chapter 38, §38.2); the guests and speakers you record identifiably need releases (§38.4); and the reception's DJ music or the conference's walk-on track is copyrighted — you cannot simply keep it in your deliverable without dealing with licensing (§38.5). Event work makes the business chapters concrete, because on an event the business is the craft: an unhappy wedding client and a missed contractual deliverable are the same disaster.

⚠️ Common Mistake: the single-camera wedding, and the un-captured slides. Two genre-specific errors sink beginners. At weddings, trying to cover the ceremony on one camera — you will be on the wrong face at the vows or reframing during the kiss, guaranteed, because one camera cannot be two places during a two-person moment. Bring two, lock the wide, and never let it stop. At conferences, not capturing the slides — you deliver a beautiful shot of a speaker gesturing at content the viewer can't read, which makes the talk useless. Take the slide feed directly, or frame a clean locked shot of the screen you can cut to, and treat the slides as a fourth "camera."

🔄 Check Your Eye. 1. Why does a wedding ceremony require at least two cameras — what specifically can't a single camera do? 2. At a conference, what is the "fourth camera" beginners forget, and why does it matter? 3. Why are weddings almost always cut in post rather than switched live?

Check yourself

1. A single camera can only be on one face, but a ceremony's emotion jumps between two people (the vows, the reactions) and includes a moment you cannot reshoot (the kiss). One camera is guaranteed to be on the wrong face or reframing at the key beat; a locked wide plus a tight solves it.
2. The slides / presentation feed. A talk is useless if the viewer can't read the content; capture the slide feed directly or hold a clean locked shot of the screen to cut to.
3. Because at a wedding, quality and safety beat immediacy — there's no need to be live, and you never want to risk a missed live cut on an unrepeatable day. Recording every angle in full lets you cut at leisure with zero chance of "missing" the shot.

24.6 Audio for events (the board feed)

Everything you learned about sound being half the picture (Chapter 14) applies double at an event, for a simple reason: the picture, you can cover with cameras, but the audio of a speech, a vow, or a song is a single fragile thing happening once, and if you don't capture it cleanly there is no B-roll of a voice. An event with gorgeous multicam footage and muddy, echoing audio is a failure, and it fails in exactly the place audiences are least forgiving. So the last and most important discipline of event work is getting clean sound — and at most real events, the cleanest sound in the building is already being made by someone else.

Almost every event of any size runs its speakers, microphones, and music through a mixing board (or "sound desk") operated by the venue's or event's audio team — the podium mic, the lavalier on the officiant, the band's inputs, all mixed into the house speakers. The single best audio decision you can make is to take that mix directly, rather than trying to re-capture the sound of speakers with your own microphone across a noisy room. This direct output is the board feed: a copy of the venue's mixed audio, handed to you from the sound desk as a clean electrical signal, free of room echo, crowd noise, and distance. A board feed is the difference between a vow that sounds like it was whispered into your ear and one that sounds like it was recorded from the back of a gymnasium — because that's exactly what those two options are.

Getting a board feed is a social skill as much as a technical one: you find the audio person early (during setup — the recce again, Chapter 16 §16.6), introduce yourself, and politely ask for a feed, ideally a mult or split output so that taking your copy doesn't affect their mix. You run it into your recorder or camera, set your levels with headroom (Chapter 15, §15.4) so the loudest applause doesn't clip past 0 dBFS, and you monitor it on headphones (Chapter 15, §15.3) — because the one failure mode of a board feed is trusting it blind and discovering afterward that the desk sent you a dead channel.

FIGURE 24.6 — Event audio: the board feed, always with a backup

   VENUE MIXING BOARD                    YOUR RIG
   ┌───────────────┐                     ┌────────────────────┐
   │ podium mic     │                    │  RECORDER          │
   │ officiant lav  │──▶ house mix ──────┼─▶ [board feed]  ◀── the clean copy: primary audio
   │ band inputs    │    (ask for a      │  (mult/split)      │
   │ music          │     MULT/SPLIT)    │                    │
   └───────────────┘                     │  [scratch mic] ◀───┼── on-camera / room mic:
        │                                └────────────────────┘   the BACKUP + sync reference
        ▼ house speakers                          ((•  camera mic hears the room
                                                        (never your only source, but
                                                         always rolling — it saves you
                                                         when the board feed fails, and
                                                         it syncs the multicam angles)

   RULE: take the board feed as PRIMARY, but ALWAYS also record a scratch/room mic as
   BACKUP. The board can send a dead channel; the scratch never does. Bonus: the scratch
   audio, common to every camera, is what you sync your multicam angles to in post (§24.3).

Notice that the scratch mic — a simple on-camera or room microphone — does two jobs at once, which is why it's never optional. First, it's your backup: if the board feed is dead, silent, or distorted (and someday it will be), the scratch mic's rougher-but-real capture of the room saves the entire event from having no usable audio. Second, it's your sync reference: because every camera's on-board mic hears the same room, that common audio is what lets you line up all your multicam angles in the edit (§24.3) — the clap you do at the start is captured by these same scratch mics. Take the board feed for quality; keep the scratch for safety and sync. Never run only one.

For events without a board — a small wedding, an outdoor ceremony, a talk with no PA system — you fall back on everything from Chapters 14 and 15: put your own microphone as close to the source as you can (a lavalier on the officiant or groom, a recorder tucked by the lectern), because proximity beats every other audio trick, and you still keep a room mic rolling as backup. The principle never changes, board or no board: get the cleanest possible source, get a backup, and monitor it on headphones so you know — live, in the moment — that sound is actually being captured. At an event, "I thought it was recording" is the six most expensive words in the language.

💡 Why It Works: the board feed is proximity without the microphone. Everything you learned in Chapter 14 said the same thing — the closer the mic is to the source, the cleaner the sound, because you capture more of the voice and less of the room. A board feed is the ultimate version of that principle: the venue already put a microphone right on the speaker's mouth and the instruments, and the board feed hands you the sound from those close mics without you having to place a single one. You are, in effect, borrowing the best mic position in the building. That's why a board feed beats even a good camera-mounted shotgun across the room — it's not a different technique, it's maximum proximity, achieved by taking sound from mics that are already perfectly placed.

⚠️ Common Mistake: the board feed as your only source (and no headphones). The two audio catastrophes of event work are cousins. The first is taking the board feed and recording nothing else — then discovering in the edit that the desk muted your channel, sent you only the music and not the speeches, or handed you a dead cable, and now the entire event has no usable audio and no remedy. Always record a scratch/room mic too. The second is not monitoring — trusting the feed blind, without headphones, so you never hear that it's dead until it's too late. Wear the headphones. Watch the levels. A board feed you didn't monitor is a bet you'll lose eventually, and at an event, losing it once is losing it forever.

🔄 Check Your Eye. 1. What is a board feed, and why does it beat pointing your own mic at the speakers? 2. Name the two jobs a scratch/room mic does at an event. 3. What must you do the entire time a board feed is recording, and why?

Check yourself

1. A board feed is a direct copy of the venue's mixed audio, taken from the sound desk — free of room echo and distance. It beats your own room mic because the venue already placed microphones right on the speakers and instruments; the feed borrows those ideal close positions.
2. It's the backup (if the board feed fails, the room mic still captured usable audio) and the sync reference (its common room sound lets you line up all the multicam angles in the edit).
3. Monitor it on headphones (and watch levels). The one way a board feed fails you is silently — a dead or muted channel you don't discover until the edit, when it's unrecoverable. Headphones catch it live, while you can still fix it.

Production Checkpoint

Your documentary short (Project 2) and branded piece (Project 3) have taught you controlled shooting, where you set the pace. This chapter adds the opposite skill — capturing something you don't control — and the checkpoint proves you can do it even at the smallest scale.

Your task: capture (or, if you lack a live event, plan and storyboard) a multicam or event element — two angles of one moment you could cut together — and write the sync and audio plan. Concretely:

1. Find or stage a one-take moment. A real event if you have access to one (a meeting, a performance, a family gathering, a talk); if not, stage a small unrepeatable exchange the way the §24.5 🎬 On Set box describes.
2. Cover it with two angles rolling at once. Two cameras or two phones: one a locked, safe master wide of the whole moment, one a tight on the face or detail. Match their frame rate, shutter, white balance, and exposure (§24.2) so they'll cut together. Roll both before the moment starts.
3. Write the sync and audio plan. In a few lines, note: how you'll sync the two angles in the edit (a clap at the start? matching the audio waveforms? — see Chapter 27, §27.4); and where your audio comes from (a board feed? a close mic? an on-camera scratch as backup?). If you're planning rather than shooting, storyboard the two angles and the moment they cut on.

Why this matters: this is the whole chapter compressed into one exercise — coverage that survives a single take, cameras matched to cut, and an audio plan with a backup. It also advances your portfolio: a multicam event element (an interview cut between two angles, a captured performance, a real moment) is exactly the kind of footage that strengthens Project 2 or 3 and, later, your reel (Chapter 39). Whether you shot it or storyboarded it, you now have a plan for the one situation where planning is the only thing that saves you.

Summary

• Event coverage captures a real, unrepeatable event as it unfolds — there is no second take. The event is won or lost in pre-production; the plan is the performance.
• The three pillars of the event mindset: a written run-of-show with your must-get moments marked; redundancy everywhere (two cameras, two audio paths, spare power/cards); and roll early, stop late, never chase.

Multicam angle roles (assign each camera one job and hold it):

• Match all cameras on frame rate, shutter, white balance, and exposure or the angles won't cut together. Keep every camera on one side of the 180° line (Chapters 7, 9) so screen direction never flips on a cut.
• Switch live vs. cut in post — the defining choice:

• Live streaming signal chain: cameras → switcher (program feed) → encoder (compress to H.264/H.265 at a tested bitrate) → upload (test the real upstream; prefer wired) → platform → viewer. Always record the program locally — the stream can drop; the disk can't.
• Wedding playbook: two-plus cameras, locked wide never touched; must-gets are processional, vows, rings, the kiss (wide and tight), recessional, reactions; cut in post; contract + releases (Chapter 38).
• Conference playbook: standardized stage rig (wide + tight), capture the slides, take audio from the board, often stream it live, lower-thirds and captions on export.
• Event audio: take the board feed (the venue's mixed audio — maximum proximity) as your primary, but always also record a scratch/room mic as backup and sync reference, and monitor on headphones the whole time.

Spaced Review

This chapter stands on two earlier ones. Answer from memory, then check.

1. (Ch.8) This chapter's "master" camera is a locked-off wide that never moves. What did Chapter 8 say a locked-off shot does that a moving one can't — and why is stillness the right choice for the safety camera?
2. (Ch.8) Chapter 8 taught you to shoot a locked-off "safety" of any moving shot. How is that same edit-minded instinct behind recording every camera's ISO angle even when you switch live?
3. (Ch.18) A shoot is a small organization with named crew roles. On a multicam event, which role must own sound (including chasing the board feed), and what happens to the event if nobody does?
4. (Ch.18) Chapter 18 gave you the on-the-day triage order. When three things go wrong during a live event, why does audio outrank light in that order — and how does that map onto this chapter's "board feed with a backup"?

What's Next

You can now survive the one take: point several cameras at a moment, match them so they cut, decide whether to switch live or assemble later, push a stream out through a signal chain that won't collapse, and capture event audio clean from the board with a backup underneath it. That is the hardest test of preparation in the whole book, because live work punishes every gap in your plan in real time. In Chapter 25 we lift off — literally — into aerial, action, and specialty capture: drones for the establishing shot that used to cost a helicopter, action cameras and FPV for the places you can't put a normal rig, timelapse and high-speed for bending time itself, and 360/VR for stepping inside the frame. Each adds production value and a new perspective — used, as always, with restraint and within the law, and only when the story genuinely calls for it. You've learned to catch reality as it happens once. Now let's learn to see it from angles reality doesn't usually offer.