Five minutes into the opening keynote of a well-funded 800-person hybrid conference, the stream froze. Not for the remote attendees — they got a clean 30-second buffer and recovery. The people watching from the overflow room next door got nothing. Their display pulled from the same single feed as the remote platform, and the venue's conference-center wifi, shared with the overflow room projector, collapsed when keynote registrations spiked the connection count. Everything about this failure was preventable at the setup stage. None of it was fixed in time.
Live streaming at events is a discipline closer to broadcast engineering than IT. The failure modes are unforgiving and visible in real time. This guide covers the hardware, network, encoder, and platform choices that produce broadcast-quality streams without the venue-AV chaos most organizers inherit.
1. Camera and switching setup
A three-camera minimum is non-negotiable for anything you want people to keep watching:
- Camera 1: Wide/establishing shot. Shows the stage, speaker, and a suggestion of audience. Anchors the scene for remote viewers.
- Camera 2: Speaker close-up. Tight on the speaker's face. Cuts for applause, laughs, emotional moments.
- Camera 3: Audience or presentation. Either pointed at the audience (for reaction shots and Q&A) or capturing a clean screen feed of the slides.
A hardware video switcher (Blackmagic Atem Mini Pro ISO is the budget standard, upgrade to Atem 2 M/E for multi-room productions) manages cuts. Avoid software-only switchers for live work — they introduce latency and drop frames when the host machine hiccups. A camera operator for each moving camera, plus one technical director on the switcher, is the minimum crew.
Events that run a single locked-down wide shot look like CCTV. Remote attendees drop off within 20 minutes. Three cameras properly cut feels like television and holds attention through a 45-minute session.
2. Audio — the single most important element
Viewers will forgive bad video. They will not forgive bad audio. Two rules:
- Take audio from the venue's mix console, never from a room mic. Speakers are mic'd; use that signal. A ceiling or camera mic picks up HVAC, audience rustle, and echo — the result sounds like a 1997 corporate training video.
- Run a backup feed with phantom power and an independent mixer. The backup feed costs $600-1,200 to add and has saved more than a few events when the venue's mixer dropped a channel mid-session.
The audio engineer should be a different person from the video TD. Double-hatting the role compromises both. At a $15,000 AV budget, audio deserves at least $4,000 of that line.
3. Encoder and network
The encoder converts camera output into streaming-ready video. Three tiers:
- Software encoder on a laptop (OBS, vMix on a capable machine). Works for a single-camera single-session stream. Fragile for multi-camera or multi-hour events.
- Hardware encoder (Epiphan Pearl, LiveU, vMix on a purpose-built machine). The professional default. Isolated from the venue network. Does not crash when the conference wifi does.
- Cloud encoder with SRT or RIST ingest (LiveU Studio, Haivision). Reserve for the highest-stakes productions where an on-site encoder failure would be catastrophic.
For network, the rule is redundancy at every layer:
- Two separate ISPs if the venue supports them (not just two drops from the same provider).
- Bonded LTE or 5G backup for the encoder. A $40/day cellular bonding appliance can save a $50,000 keynote.
- A dedicated streaming VLAN, isolated from attendee wifi and venue-shared traffic. If your stream shares bandwidth with 500 laptops on the attendee wifi, you will lose.
- Minimum 20 Mbps upload per stream, double that for 4K. Most venues advertise much more and deliver far less under load.
Test the network under simulated load 48 hours before. Run a 30-minute test stream with all expected attendee devices on the wifi simultaneously. Failure during the test is a gift — you still have time to fix it.
4. Streaming platform and access gating
Platform selection depends on audience and monetization:
- YouTube Live. Free, reliable, globally CDN-backed. Fine for public events and press conferences. No native registration gating; "private" streams still leak via URL sharing.
- Vimeo Livestream. Supports registration gating, paywalls, and white-label embeds. Solid default for B2B paid events.
- LinkedIn Live. Useful for thought-leadership events targeting LinkedIn-native audiences. Not suitable for paid gating.
- Purpose-built event platform. The event management software that runs your event app can also host the stream, which gives you registration gating, chat, polls, and session attendance analytics in one place. Use this when the stream is for registered attendees only.
For B2B paid events, avoid platforms without native gating. A $2,000 ticket on a public YouTube URL is a poor business decision. For free marketing events, a public YouTube stream is usually the right choice and gives you an asset that keeps working for years.
5. The run-of-show document
The most overlooked piece of streaming infrastructure is the run-of-show: a minute-by-minute document the streaming team uses to hit cues. It should include:
- Every session start/stop with timestamps.
- Each speaker's name, walk-on music cue, and intro slide.
- All lower-third graphics (speaker name, title, company) with correct spellings.
- Cuts to sponsor bumpers and their exact durations.
- Transitions between sessions, including walk-off music and scene switches.
- Scheduled breaks with what the stream should show during them (recap reels, sponsor content, a "we are back at 14:00" card).
Without a run-of-show, the stream drifts, cuts to black randomly, and loses remote viewers every time the in-room energy peaks.
6. Pre-event technical checklist
Run through this during the setup day, not the morning of:
- [ ] Three cameras positioned, white-balanced, and focus-locked
- [ ] Audio feed tested from the venue board to the encoder
- [ ] Backup audio feed live and monitored
- [ ] Hardware encoder connected and successfully pushing to the platform test channel
- [ ] Primary ISP verified at advertised upload speed under simulated load
- [ ] Secondary ISP or cellular backup confirmed working
- [ ] Streaming VLAN isolated from attendee wifi
- [ ] Stream tested end-to-end, including remote viewer login and gating
- [ ] Run-of-show printed, shared, and walked through with every crew member
- [ ] Lower-third graphics tested with correct speaker names
- [ ] Walk-in music and bumpers queued
- [ ] Chat moderation staff briefed and roles assigned
- [ ] Emergency contact numbers posted at the TD station
Common mistakes
- Treating streaming as an afterthought and assigning it to the general AV team. Streaming is a separate specialty; hire accordingly.
- Running everything on venue wifi. Shared networks collapse under load and there is nothing you can do on the day.
- No audio backup. One dead mic and the stream is unusable.
- Relying on a single encoder with no failover. When the encoder goes down mid-keynote, remote viewers do not wait for the fix.
- Skipping the run-of-show. The crew improvises, and the stream shows it.
- Launching without a captioning setup. Accessibility obligations aside, captions double watch-time for many audiences.
FAQ
What is a reasonable budget for streaming a 2-day hybrid event? $18,000-45,000 for a three-camera production with hardware encoder, dual ISP, a three-person crew, and platform fees. Anything under $10,000 is a compromised production; anything over $60,000 usually signals the vendor is marked up rather than delivering uniquely.
Should I hire the streaming crew separately from the venue AV? Yes, almost always. Venue AV teams are excellent at in-room sound and projection and usually weak at streaming. A dedicated streaming vendor who works with the venue AV team produces better results than either alone.
Can I use attendee-shot content as a stream backup? No. Crowd-shot phone footage looks like crowd-shot phone footage and destroys the production value everything else supported. Invest in a proper backup feed instead.
How long should I keep recordings live post-event? See session recording distribution strategy. Typically 48 hours restricted to live attendees, 7 days all attendees, then selective public releases.
Do I need a rehearsal day? For any event over 500 attendees or multi-track: yes. For single-track under 300: a 2-hour morning-of tech check can substitute, but only if the same crew worked together recently.
Related guides
Stream, gate, chat, poll, and record — all inside one attendee app: Create your event on WebMobi →