Overview
Hive is built to flexibly scale-up, but you don’t have to. This article outlines how to design a complete production setup using Hive, even if you're the only operator in the room. Whether you’re building a full studio pipeline or simply upgrading your live streaming setup, Hive allows you to ingest, control, monitor, and output your production, all through a clean, modular interface.
This guide is tailored for single-producer workflows and covers:
Recommended and minimum infrastructure
Ideal and alternative camera integration methods
Audio and graphics system routing
Network requirements and output bandwidth
How Hive balances simplicity with scale
1. Core Infrastructure and Studio Setup
To begin:
Launch Hive, log in, and select or create your studio.
Connect your Hive Bridge to a Gigabit or Multi-Gigabit router or switch. This switch should also have the capability to recognize:
Cameras (IP or USB-based)
Audio interfaces or mixers
Any graphic playback or screen capture systems
A router with internet access (for remote control or cloud sync)
Managed switches are recommended for multicast support, NDI routing, and traffic management. Unmanaged switch setups are effective as long as proper planning goes into pre-production!
2. Ideal Camera Configuration – IP-Based Control and Video
The ideal method of connecting cameras to Hive is over a network connection using IP protocols like NDI and RTSP. This allows Hive to fully access:
Camera control functions (PTZ, zoom, focus)
Image settings (exposure, white balance, gamma, detail)
System and network-level diagnostics
In-camera audio and tally indicators
Driver-based customization via the Advanced Settings panel
Cameras connected over the network via Ethernet allow for bi-directional communication, enabling Hive to control and manipulate the camera, not just ingest video.
The intent of the Hive platform is to maximize the use of your hardware’s capabilities, not just to receive a signal. Network-based integration is the only method that unlocks full control and automation.
3. Alternative Camera Inputs – Signal Only (No Control)
While networked cameras are ideal, Hive supports a wide range of non-IP video sources for simple ingest, such as:
HDMI via Capture Cards – Great for computers, consoles, or DSLRs
USB Capture Cards – Common for webcams and consumer video gear
SDI via PCIe Interfaces – Useful in traditional studio routing
NDI Screen Capture or HDMI Output – From external PCs or media systems
These sources are treated as video-only: Hive cannot control exposure, zoom, tally, or settings from these devices. They are useful for:
Graphic playback machines
Mobile devices and game consoles
Photography carousels or digital signage
Any non-camera HDMI or USB video output
If your workflow depends on remote control or image adjustment, USB or HDMI ingest will not provide that functionality. Use IP when possible.
4. Audio System Integration
Audio in Hive is intentionally protocol-agnostic and integrates well with most modern mixers, interfaces, and DAWs. To connect audio into Hive:
Use USB audio interfaces directly into the Hive Bridge.
For Dante-based mixers& connections, use a Dante AVIO to USB-C adapter or connect the Dante Controller Network to the same subnet as the Hive Bridge.
Analog audio systems can route through a capture card’s audio input, if available.
As long as your system’s OS can recognize the device as a valid input/output (speaker or microphone), Hive will discover it.
5. Graphics Playback and External Sources
Graphics engines, playback software, or presentation systems can be integrated into Hive in several ways:
HDMI via capture card
NDI Tools (Screen Capture or Scan Converter) from a graphics PC
USB capture devices for small form factor systems
RTSP feeds from real-time media players or playback servers
These integrations treat the graphics system as a video source.
Hive doesn't limit your content format, as long as the source gets into the bridge, it's usable in your studio.
6. Internet Speed Recommendations
For streaming, remote access, and cloud recording, your upload bandwidth matters most.
Minimum (1 camera, H.264, 30fps): 30 Mbps upload
Recommended (multi-camera, cloud routing): 150 Mbps upload
No ceiling: Hive is built to scale across any production size or bandwidth capacity.
Local mode does not consume any bandwidth from your Hive cloud plan. Only cloud-linked operations draw from your subscription quota.
To test bandwidth, tools like speedtest.net or your router’s diagnostics panel are useful before a production.
7. Scale as You Need—Or Not at All
One of Hive’s core strengths is that it adapts to your goals.
Just need a single feed for remote viewing? Done.
Want a 12-camera, cloud-managed, multi-user control room? Hive is ready.
Building a flypack for a touring crew with shared presets and routing? That works too.
Hive isn’t here to force scale, it’s here to support it. Many users adopt Hive to solve one specific problem (remote PTZ control, cloud ingest, synchronized switching) and expand only if the need arises.
Whether you're a one-person operator or leading a hybrid AV team, Hive integrates with the ecosystem you already have, and grows with you if and when you're ready.
Hive fits into nearly any production setup, from simple one-room studios to broadcast-level command centers. The ideal workflow starts with IP-connected, driver-supported cameras, but the platform supports almost any video source format or audio routing setup. It’s built to scale with your creativity and infrastructure, whether you're just getting started or optimizing a global network of sources.