What is automated NDI failover?

Automated NDI failover is a system configuration where a production router or video switcher continuously monitors an active primary NDI IP video feed and automatically switches to an identical secondary backup feed within milliseconds if the primary signal drops or freezes.

How fast does an NDI failover switch occur during a hardware crash?

An automated NDI failover switch typically executes within 33 to 100 milliseconds (one to three frames at 60fps), depending on network polling intervals and switcher buffer settings, preventing noticeable black screens or visual disruption.

Do you need identical hardware specifications for primary and backup NDI machines?

While identical hardware specifications are not strictly mandatory, matching the operating system, GPU architecture, screen resolutions, and font directories between primary and backup machines ensures visual consistency and prevents frame-rate desynchronization during an automated switch.

How much network bandwidth is required for a dual-redundant NDI presentation rig?

A dual-redundant NDI presentation rig outputting two simultaneous 1080p60 high-bandwidth NDI streams requires approximately 250 to 300 Mbps of dedicated network bandwidth, making a managed 1 Gbps or 10 Gbps Ethernet infrastructure essential.

← Blog

Zero-Downtime Live Visuals: How to Configure Automated NDI Failover for Dual-Redundancy Presentation Rigs

October 5, 2026

TL;DR

A dual-redundancy presentation rig pairs primary and backup media servers running identical content over a managed gigabit network via NDI. Automated failover systems continuously monitor heartbeat signals or video loss, instantly switching outputs in under 50 milliseconds without audience interruption. This architecture guarantees zero-downtime visuals for high-stakes live events, worship services, and broadcast productions.

When a presentation computer freezes during a high-stakes keynote, corporate broadcast, or worship service, the delay in manually swapping video cables or switching inputs can feel like an eternity. A dual-redundancy presentation rig eliminates this vulnerability by pairing primary and secondary presentation engines that mirror content in real time. By leveraging Network Device Interface (NDI) protocols and automated failover routing, production engineers can protect live stage environments from software crashes, operating system freezes, and hardware failures with sub-second recovery.

What Is an NDI Dual-Redundancy Presentation Rig?

An NDI dual-redundancy presentation rig consists of two independent computers running synchronized presentation software simultaneously. Both machines encode their display outputs into high-bandwidth NDI IP video streams sent across a dedicated local area network (LAN).

Rather than relying on manual HDMI or SDI matrix switchers, an automated NDI failover setup uses an intelligent monitoring layer—such as software watchdogs, network management scripts, or video production switchers—to continuously poll the health of the primary stream. If the primary system drops frames, loses network connectivity, or ceases transmission, the receiving destination automatically shifts to the secondary NDI stream without requiring manual operator intervention.

Core Hardware and Network Prerequisites

Reliable IP video failover depends heavily on proper network architecture. Deploying redundant NDI streams requires specific infrastructure to prevent packet collisions and packet loss:

Dedicated Managed Network Switch: Use a managed Gigabit or 10-Gigabit switch supporting Quality of Service (QoS), IGMP snooping, and flow control. High-bandwidth NDI streams typically consume 100 to 150 Mbps per 1080p60 channel.
Matched Presentation Hardware: While not strictly mandatory, using matched primary and backup presentation machines ensures identical font rendering, GPU acceleration behaviors, and transition timings.
Secondary Control Interfaces: A dedicated control surface, such as an Elgato Stream Deck powered by Bitfocus Companion, allows simultaneous cue firing across both rigs via OSC (Open Sound Control), MIDI, or REST API triggers.

Step-by-Step Configuration of Automated NDI Failover

Configuring an automated failover workflow involves three primary components: cue synchronization, stream naming conventions, and automated switching triggers.

1. Synchronize Playback Cues Across Both Machines

For automated failover to succeed, the backup system must mirror the exact slide or video state of the primary system. Configure your presentation software to accept external network triggers. Tools like Bitfocus Companion can broadcast a single slide change command simultaneously to the IP addresses of both the primary and backup presentation machines.

2. Configure Discrete NDI Channel Output Names

Assign explicit, static NDI stream names on each machine to avoid discovery conflicts on the local subnet. For example, label the primary output STAGE-PRES-01 and the backup output STAGE-PRES-02. Using static IP configurations for both presentation systems prevents dynamic DHCP reassignments from breaking connection routes during production.

3. Deploy an Intelligent Failover Receiver

Automated routing requires a destination device that detects signal loss. This can be accomplished through two main methods:

Software Switcher Watchdog: Production software such as vMix or OBS Studio (with the NDI plugin) can monitor the incoming primary NDI feed. By utilizing API scripting or tools like Central Control, the switcher can monitor NDI signal presence. If the primary stream drops for more than 300 milliseconds, an automated script switches the preview/program bus to the backup feed.
NDI Router with Signal Loss Triggering: Dedicated NDI routing appliances and software matrix routers can be configured with primary and secondary fallback hierarchies. When the primary connection disconnects or reports packet termination, the router reroutes the output destination to the secondary source within two frames.

Monitoring, Health Checks, and Testing the Rig

Automated systems must be rigorously validated before entering live production. Testing failover reliability requires simulating actual failure scenarios, not just graceful software shutdowns:

Hard Power-Cut Test: Disconnect the power cable from the primary presentation machine during full-screen video playback. The automated receiver should switch to the backup stream in under 100 milliseconds.
Network Disconnect Test: Unplug the primary Ethernet cable to verify that the monitoring software detects packet loss rather than waiting on an infinite buffer timeout.
Application Hang Simulation: Force a process freeze on the primary presentation application using Task Manager or Activity Monitor to confirm that the watchdog identifies frozen video frames or dropped heartbeat pings.

Zero-Downtime Confidence for Live Events

Live productions leave no room for single points of failure. By implementing dual presentation servers synchronized over local network protocols and routed via automated NDI failover, production teams replace panic with predictability. Investing the time to configure redundant IP streams guarantees that your screens stay lit, your audience stays engaged, and technical failures remain completely invisible.