NDI (Network Device Interface)

The technical trade-off: NDI sacrifices timing precision for flexibility. SMPTE 2110 guarantees every frame arrives at exactly the right moment. NDI best-effort delivery works for real-time applications but doesn't guarantee sample-perfect audio sync or frame-accurate timing across sources. For professional broadcast, this matters less than equipment makers admit, but for highly synchronized multi-camera work, SMPTE 2110 is more robust.

For Creative Broadcast Agency productions, NDI shines in remote speaker integration and hybrid event streaming. A remote speaker joining via NDI feed from their office WiFi is simpler than setting up SRT connections. A camera in a venue sending NDI over the corporate network is easier than deploying dedicated networking infrastructure.

NDI is also software-friendly. Most switching, graphics, and video software supports NDI ingestion natively. This means designers and technical directors without broadcast equipment experience can participate in production.

However, NDI over WiFi introduces latency variability. The latency might be 100ms on a good connection, 500ms if network congestion occurs. For monitoring purposes (return feeds to talent, confidence monitoring), this variability isn't disruptive. For synchronized playback (multiple sources feeding a vision mixer), variable latency is problematic.

NDI also generates significant network traffic. A 1080p60 NDI feed consumes roughly 500 Mbps on the network. A large event with 10 concurrent feeds consumes 5 Gbps. not practical on typical office networks. Compression modes (visually lossless compression) reduce this, but add latency.