NDI

NDI input and output with zero packaged dependencies - VSK talks directly to the NDI runtime DLL if it’s installed, and degrades gracefully if not. Field-verified 2026-08-03: a Mac’s screen shared into the Video Hub, and the program feed viewed live in NDI Video Monitor on the same Mac.

Input

Discovered NDI sources appear automatically in the Video Hub pickers, cut banks and the web remote’s TV dropdowns as NDI:<source name>. One receiver per source, auto-reconnecting, at highest bandwidth.

The verified workflow: run NDI Tools on the source machine (e.g. Screen Capture / Scan Converter to share its display), the source appears in the pickers within seconds, and you route it onto any screen or TV exactly like an SDI camera. Receivers auto-connect even if the source starts broadcasting later (~1 s rescan); a routed source shows black until its first frame arrives.

macOS gotcha - the first launch of the capture app needs the Screen Recording permission (System Settings ▸ Privacy & Security), then relaunch the app - no OS restart.

Output

The program feed publishes as an NDI sender (default name “VSK Program”) - any NDI-aware device on the LAN can take the show feed without a capture card. Enable + name live in VSK Project ▸ NDI; both travel in the show file. The stream is an opaque BGRX picture paced at the project frame rate.

The status line tells you what’s actually flowing: ”● SENDING - N frames” (green) means receivers are getting the live program; ”● SENDING - waiting for Play” (amber) means the sender is up but program frames only flow during a Play session - a receiver connected while the session is stopped sees the source with black/paused video. That’s expected, not a fault; the sender deliberately survives session stop so receivers keep their connection.

Video-only for now - NDI audio embed is next on the roadmap, unblocked by the audio system’s acceptance.