OmniBridge

Future Plan

What's on the roadmap, what's deliberately parked, and why — so you know what to expect (and not expect) in a coming release.

On the roadmap

Topology / signal-flow view

A real interactive diagram of source → gateway → destination routing, rather than reading it off the Operate/Diagnostics tables. For now, see Diagnostics and Signal Flow for a text-diagram stand-in — a full interactive version is being considered but isn't built yet.

Redundant matrix pair / failover

Running two gateways in an active/standby or active/active pair, so a single hardware failure doesn't take down a whole show. Not started — today, a single gateway is a single point of failure for the gateway process itself (see Home's "What survives a restart" for what actually happens if it goes down mid-show: routes and presets are preserved, and everything reconnects automatically once it's back up, but there's no automatic failover to a second machine while it's down).

NDI support

Not foreseen in the near future. If it happens, the more likely path is broader capture-card support (Decklink, SDI) rather than NDI specifically.

OBS SRT Toolkit's own dedicated encoder

OBS SRT Toolkit (see the OBS Setup Guide) is real, shipped, and verified end-to-end against a real OmniBridge instance — see "Shipped" below. One limitation remains: its SRT Output currently reuses whichever encoder OBS's own Streaming or Recording output already has configured, rather than creating a dedicated one, so Stream or Record needs to have been started at least once first. A version with its own independent encoder is planned as a follow-up — see issue #1 for status.

Persistent event logging

The Events tab (see Home) is currently a live, in-memory session log only — it doesn't survive a gateway restart. Persisting it to disk (a rotated log file next to app_config.json) so you can pull up what happened even after an unplanned restart, crash, or power loss, is on the roadmap. Not started yet.

Shipped

Everything below already exists in the current release — kept here so "what's actually on the roadmap" above isn't confused with what's already done:

  • Protocol Support — RTMP, UDP MPEG-TS, and RIST output.
  • Observability — the three-state status indicators, the (in-memory) event/audit log, relay traffic counters, the endpoint Diagnostics view, and per-connection metrics (RTT/loss/retransmits).
  • Core Platform & Config — the shared program-out port + stream-ID architecture, per-endpoint SRT latency/passphrase overrides, and the source/destination terminology cleanup.
  • OBS Media Source reliability (#17) — OBS's Media Source had appeared less reliable than a raw SRT connection under otherwise identical conditions; root-caused to FFmpeg libsrt's default listener-socket timeout/buffer settings, not the gateway side — the OBS Setup Guide's manual-setup Direction 2 documents the URL parameters (timeout, latency, rcvbuf, pkt_size) that fix the "freezes on disconnect" and stutter symptoms.
  • OBS integration — OBS SRT Toolkit, a native OBS plugin adding a real SRT Output (its own dock) and SRT Source, replacing the old Media-Source-tuning and Custom-FFmpeg-Output workarounds documented further down the OBS Setup Guide. Verified end-to-end against a real OmniBridge instance in both directions, with sustained throughput. The manual, no-plugin methods (Media Source tuning, Custom FFmpeg Output) remain fully documented and supported for anyone who can't install a plugin.

Tracking

All roadmap work — shipped and open — is tracked as GitLab issues, grouped into milestones by theme (not by release date — no ETA is implied on the open ones):

  • Reliability & Failover — redundant matrix pair/failover (open), the OBS Media Source reliability investigation (shipped).
  • Protocol Support — RTMP/UDP-TS/RIST output (shipped), NDI support (open).
  • Observability — status indicators, event log, traffic counters, diagnostics view, connection metrics (all shipped), plus the topology/signal-flow view and persistent event logging (both open).
  • Core Platform & Config — shared port architecture, per-endpoint SRT config, terminology cleanup (all shipped).
  • Backlog (not scheduled) — single-feed destination diagnostics, per-destination preset scoping (see below).

Deliberately not planned

Tracked as GitLab issues for visibility, but not committed to any release — see the Backlog milestone:

  • Single-feed destination diagnostics (RTMP/RIST/UDP-TS connectivity tracking in the Diagnostics view) — a real, acknowledged gap (see Known Issues), but not scheduled; a bigger lift than a quick add-on to the existing view.
  • Per-destination preset scoping — no current plan; presets stay all-or-nothing across the whole matrix.