Building a One-Person Event Streaming and Recording System

What I Learned

I built a system that balances screen production at the venue with streaming and archive recording at the event site. By physically separating yet network-integrating the different requirements of “never stopping venue progression” (Main System) and “creating high-quality archives” (Sub System), both could be achieved simultaneously. By incorporating long-distance transmission via SDI and one-button control with Bitfocus Companion, the system became robust with minimal chance of operator errors even with a small team.

Details

Overall Concept and Requirements

Complete Separation and Integration of Venue Production (Screen) and Streaming/Recording

Building an environment where video sent to venue screens (Main) and video saved for archives/streaming (Sub) are physically separated yet controllable by a single operator.

Design Requirements

  1. Physical Separation of Roles (Risk Distribution)

    • Main System (Projector): Dedicated to venue screen production. Streaming-side troubles don’t affect venue progression
    • Sub System (Streaming, Recording): Dedicated to package video creation. Composites slides and camera footage, performs ISO recording

  2. Long-Distance Transmission (SDI)

    • To accommodate the distance between Main and Sub desks, convert HDMI to SDI (using Blackmagic BiDirectional Converter) for transmission

  3. Mutual Monitoring and Return

    • Use ATEM Streaming Bridge to return Sub System video to Main System’s input 4 via Ethernet
    • Allow performers to check recorded footage

System Configuration Diagram

System Configuration Diagram

Mermaid source code: system-diagram.mmd

Actual Setup

Actual Setup

The actual operation environment. PC on the left (displaying ATEM Software Control), two ATEM Mini Pro units in the center, Stream Deck, Loupedeck, and operator PC on the right. All equipment is consolidated on the desk in an arrangement that enables one-person operation control.

Operation Configuration (Control & Network)

Centralized setup for running physically separated systems single-handedly.

  • Bitfocus Companion (Stream Deck)

    • Controls both Main/Sub ATEMs via network
    • Operating Rule: Don’t touch ATEM unit buttons (prevents infinite loops). Use Companion presets to batch-switch between “Slide Mode,” “Q&A Mode,” etc.

  • Insta360 Link 2 & Loupedeck

    • Control webcam (Insta360 Link 2) with Loupedeck buttons
    • Button layout for angle presets (presenter, questioner, venue) and OBS Replay Buffer (clip creation)

  • Network Hub Consolidation

    • Manage all control signals and Streaming Bridge video signals through one hub
    • Important: Set static IP addresses for all devices
    • Keep ATEM Software Control for Main System (venue side) always running on PC to monitor audio faders

Setup Checklist

PC Operator (Mac)

  • Connection: Connect LAN, Stream Deck, Loupedeck, Insta360, Prograde via Satechi Hub
  • Display: Display OBS Preview Projector (Insta360 preview) on extended display and connect to ATEM mini Pro’s HDMI input 1
  • Software: Launch ATEM Software Control (Main monitoring), Bitfocus Companion

Source PC (Windows)

  • App: Launch “Camera” app and switch cameras (signal stabilization, sleep prevention)
  • Network: Completely offline (prevent update/notification accidents)

ATEM Mini Pro ISO (Sub System)

  • Output: SSD REC [ON], Stream [ON]
  • Audio (Mix):
    • Mic 1 (Sony Wireless): ON
    • Mic 2: OFF
    • HDMI 2 (SDI Conv): ON
    • HDMI 1 & 3: OFF

ATEM Mini Pro (Main System)

  • Output: Set USB Out to MultiView (MV)
  • Audio (PA):
    • HDMI 1, 2, 3: ON
    • HDMI 4 (Return): OFF (Absolute) ※Prevents infinite loop

Trial and Error / What Couldn’t Be Achieved

Simultaneous Streaming to YouTube Live and ATEM Streaming Bridge

  • What I wanted to do: Simultaneously stream to YouTube Live and send to ATEM Streaming Bridge for venue return from the ATEM Mini Pro ISO alone
  • Result: Discovered that due to ATEM hardware specifications, only one streaming output destination can be set
  • Solution: Prioritized venue return (sending to Bridge) and didn’t use YouTube streaming function

Operation Consolidation on Elgato Stream Deck

  • What I wanted to do: Consolidate all operations (ATEM, Insta360, OBS) on one Stream Deck unit
  • Result: Coexistence and simultaneous use of Bitfocus Companion (for ATEM control) and Elgato official software (for plugin control) was unstable and difficult
  • Solution: Added Loupedeck Live and physically separated devices (Stream Deck = ATEM dedicated, Loupedeck = Camera/OBS dedicated)

MultiView Monitoring on iPad

  • What I wanted to do: Connect ATEM Mini Pro (Main) Type-C output to iPad and use it as a MultiView monitor with apps like Camo Studio
  • Result: Handshake was unstable, requiring ATEM restart each time for iPad recognition. Too risky for live settings
  • Solution: Changed to PC connection (PC Monitor) prioritizing stability

Conclusion

By organizing the control environment (Stream Deck & Loupedeck), I gained the mental and time margin to perform switching operations single-handedly while simultaneously “recording clips of highlights” and “instant editing of review footage.” Even if the system looks complex, operations become extremely simple when the control system is well organized.

Particularly, mundane settings like “audio infinite loop prevention” and “static IP addressing” are essential for stable on-site operation.

References

event streaming atem obs video-production system-design