Multi‑Bridge NDI Output & Selectable Recording

Overview

This Feature decouples sources from the bridge hardware they’re cabled to. Operators can now:

In the UI you’ll see a Bridge selector inside each output tab (NDI, RTMP, Loopback) plus the Recording panel.

v 1.0 note: Bridge routing is live for Recording and NDI only; RTMP and Loopback switching are placeholders for an upcoming point‑release.

Open Sources → Recording.
In Record To Bridge, pick the bridge that will store files.
- ✱ Only one recording bridge is active per session.
(Optional: local only) On the bridge host computer, click Folder Path → Change to choose a custom directory; remote sessions can view but not edit the path.
Click Save. The UI’s table adds a Destination column showing the chosen bridge for each source.
For every source to capture, toggle Record → Start. An Elapsed timer appears per source.
When finished, click Stop on each source. (There is no global time‑linked stop yet.)

Set Bridge A for NDI and Bridge B for Recording; this feature keeps the routes independent so both run simultaneously.

Single Recording Bridge Rule – Only the selected bridge writes files.
Default Folder Path – Hive auto‑sets a path (e.g. C:/HiveRecordings or /var/media/Hive). Remote users can’t change it but can see where files will land and receive a tooltip that path edits require local access.
Quality Handling
- RTMP: Encoded once at the streaming profile.
- Local Recording: Captured at each camera’s highest quality.
Elapsed vs Timecode – The UI shows an elapsed recording timer; this feature does not embed or sync to external timecode.
Session Persistence – Bridge choices are saved until manually changed or Hive Controller reboots.

Verify the target folder on the recording bridge before starting to avoid permission errors.
Remote users can view but cannot edit Folder Path; use Cloud Recording if you need remote control.
Give bridges descriptive names (NY Rec, LA NDI) to avoid accidental cross routing.
Click Stop on every source; no master stop button today.
Monitor disk space, original quality files are large.
Does not sync to timecode; clips start immediately when you hit Start.
Bridge routing for RTMP and Loopback is scheduled for v 1.1. Stay tuned!

Can I have two recording bridges at once?
Not yet—v 1.0 supports a single recording bridge per session.
Where are my recordings saved by default?
In the default folder shown next to each source (e.g. C:/HiveRecordings). Change it locally on the recording bridge if needed.
Does this feature affect Cloud Recording?
No, cloud captures bypass local bridges entirely.
What happens if the recording bridge goes offline?
Recording stops immediately; NDI outputs continue if they’re routed to another bridge.
Can I change the folder path remotely?
Not in v 1.0. You need local access to the recording bridge’s OS.
Is NDI video re‑encoded?
No, frames pass through untouched at camera output quality.
Will future versions support time‑linked start/stop?
Yes, it’s on the roadmap; up‑vote in the Hive Community forum.

Redundant Capture – Output program feed via Bridge A while capturing ISO recordings on Bridge B.
Load Balancing – Heavy NDI mixing on one bridge; recording I/O on another.
Geographic Distribution – Cameras in London stream NDI locally; recordings land on a rack‑side bridge for faster ingest.
Training/Review – Low‑bitrate RTMP to cloud for review while pristine masters record locally.
Hybrid Event – Bridge A streams RTMP to a webcast platform (future v 1.1), Bridge B handles local archive recording.

This Feature removes the last hard link between sources and physical bridges. Route NDI to one machine, record on another, and stay flexible.

Release Details: v 1.0 targeting Q4 2025; RTMP/Loopback bridge routing planned for v 1.1.