NDI output
KRZN Live can publish every stream path as its own NDI® source on the local network. vMix, OBS (with DistroAV), TriCaster, NDI Studio Monitor and any other NDI receiver find the sites by name, for example CENTRAL-PC (KRZN Live - North Site), with no URL to type, low latency and frame-accurate switching.
NDI® is a registered trademark of Vizrt NDI AB. More information: ndi.video.
site --SRT/RTMP--> KRZN Live path "north" --> decoder (GPU) --> NDI source "KRZN Live - North Site" ==LAN==> vMix, OBS, monitors
NDI output is available on Windows.
Requirements
- The NDI runtime, included in NDI Tools (ndi.video/tools). Installing NDI Tools on the central computer is the simplest way. The runtime library can also be put next to
krznlive.exe(Processing.NDI.Lib.x64.dll, withProcessing.NDI.Lib.Licenses.txt). - ffmpeg, used to decode the feeds:
ffmpeg.exenext tokrznlive.exe, or inPATH, or set in the settings. - A wired gigabit network between the central computer and the receivers.
Install NDI and FFmpeg.bat, in the folder of krznlive.exe, installs both: it downloads the official NDI 6 Runtime installer (and runs it only if it is signed by Vizrt), and puts FFmpeg in the ffmpeg folder next to krznlive.exe, after checking its SHA-256. It's the LGPL build with shared libraries of BtbN/FFmpeg-Builds, which can be given away with KRZN Live (its license and where to get its source code are in that folder). That build has no x264: the NDI input encodes with the graphics card (AMD, NVIDIA, Intel or Windows Media Foundation), or with OpenH264. What is already installed is skipped. Restart KRZN Live after installing the NDI runtime.
The Settings page of the dashboard checks the runtime and ffmpeg, and Test NDI on this computer publishes a test source (color bars, with a white flash and a beep at the start of every second, to check lip sync) for 10 seconds and receives it.
Enable it
- In Settings → NDI output, turn on Enable NDI output and apply.
- In Stream Paths, turn on Publish as NDI source on each site.
Or in the configuration file:
ndi: true
ndiNamePrefix: KRZN Live
paths:
north:
label: North Site
ndi: true
ndiFormat: 1080p30
The source is named <ndiNamePrefix> - <label>: renaming the label renames the source, without disconnecting the site. Turning NDI on or off, or changing its settings, never disconnects the site either.
What receivers see
The source exists as soon as NDI output is enabled on the path, even before the site sends anything:
| The site | The NDI source shows |
|---|---|
| hasn't sent anything yet | black, or with the slate on, a slate "Waiting for the feed", so that vMix inputs can be prepared before the service |
| is sending | the feed |
| stops sending | the last picture for 2 seconds (ndiOfflineHold), then black, or with the slate on, a slate "Reconnecting… Signal lost at 19:42:10" |
| comes back | the feed again, by itself |
The source never freezes or disappears, and keeps sending silence when there is no sound, so vMix inputs never turn black and need no action. Slates have a small moving indicator, so that operators can see that the source is alive. With the reconnecting slate of the server enabled on the same path, the NDI source still shows its own slate.
The slate is off by default (ndiSlateOn: false): the source sends black, with silence, while the site is offline. Turn it on in Stream Paths > NDI output > Slate, where its title (ndiSlateTitle, empty: the name of the site) and its message (ndiSlateText, empty: "Reconnecting…") can be changed.
Each site can have its own slate image (ndiSlate, a PNG or JPEG, ideally 1920x1080), for instance its logo or "We'll be right back": in Stream Paths, Offline slate > Choose image. The image is scaled to the format of the source, with black bars when the proportions differ, and a bar at the bottom tells the state ("Reconnecting… · Signal lost at 19:42:10") above the moving indicator. Images are saved in the slates folder next to the configuration. When the image can't be read, the standard slate is shown and an event tells why.
Settings of a path
| Setting | Default | Use |
|---|---|---|
ndiFormat |
source |
source keeps the size and the frame rate of the feed. A fixed format (1080p30, 1080p2997, 1080p25, 720p30, 2160p30, ...) scales the picture, adds black bars when its shape differs, and converts the frame rate, so that every site matches the vMix project. Recommended for production. Interlaced feeds are deinterlaced. |
ndiOfflineHold |
2s |
how long the last picture is kept before the slate (0 to 30 s) |
ndiSlateOn |
false |
shows the slate while the site is offline; off: black, with silence |
ndiSlateTitle |
title of the standard slate (empty: the name of the site) | |
ndiSlateText |
message of the slate (empty: "Reconnecting…") | |
ndiSlate |
image shown instead of the standard slate (PNG or JPEG) | |
ndiAudioDelay |
0s |
corrects lip sync, from -500 ms to 500 ms (positive = audio later) |
ndiBackup |
none | another path, used while this one is offline (see below) |
Backup feed (failover)
With ndiBackup, a site can have a second feed, for example a second encoder or a phone on another connection, published to another path:
paths:
north:
ndi: true
ndiBackup: north-backup
north-backup:
Both feeds are decoded all the time. When the main feed stops for 1 second, the NDI source sends the backup feed (the last picture is kept meanwhile: no slate, no black). When the main feed has been running again for 5 seconds, the source goes back to it. vMix sees a single input that never stops. Using the same ndiFormat on both is recommended.
Tally
When the source is on program or on preview in vMix (or another NDI switcher that sends tally), the dashboard shows a red LIVE in vMix or a green PREVIEW tag on the path card and on the multiviewer tile, and an event is written.
Global settings
| Setting | Default | Use |
|---|---|---|
ndi |
false |
enables NDI output on this computer |
ndiNamePrefix |
KRZN Live |
prefix of the source names |
ndiHardwareDecode |
auto |
auto uses the GPU (Direct3D 11) and falls back to the CPU by itself; d3d11va, dxva2, qsv, cuda force a GPU API; software uses the CPU |
ndiGroups |
empty | NDI groups of the sources (comma separated) |
ndiDiscoveryServer |
empty | NDI Discovery Server (host:port, comma separated). The settings of NDI Access Manager on this computer are kept: KRZN Live uses its own copy with the server added. |
ndiRuntimePath |
empty | folder of the NDI runtime library, when it's not the installed one |
ndiFFmpegPath |
empty | path of ffmpeg |
How it works
Each source is published by its own process (krznlive.exe ndi-worker), supervised by the server:
- the server reads the path from inside (it uses no network port, and isn't affected by stream keys) and sends it to the worker as MPEG-TS. If the worker is slow, frames are dropped for the NDI source only: the server, the site and the other viewers are never slowed down;
- the worker decodes video and audio with two ffmpeg processes (the GPU decodes the video when possible), synchronizes them by their timestamps with a small adaptive buffer that absorbs network jitter and encoders that send audio in groups, and sends them with the NDI runtime as full NDI (High Bandwidth, SpeedHQ);
- if a worker crashes or stops responding, it's restarted in about a second, and receivers reconnect by themselves. A worker that keeps failing is paused for a minute and shown as an error, with its log, in the dashboard. Workers and decoders are closed with the server, and each process is limited to 2 GB of memory.
The Status page lists the sources, their state, picture, receivers, tally, decoder, CPU and memory. Sources going to the slate and back, failovers, tally changes and worker restarts are written in the events, and sent as alerts according to the alert level.
Bandwidth and capacity
Full NDI uses about 100 to 150 Mbit/s per receiver for 1080p30, and twice that for 1080p60. Six sites sent to one vMix computer use most of a gigabit link: use a wired network, ideally with a network card or a switch dedicated to production, and no Wi-Fi receivers.
Each 1080p30 source uses the GPU to decode, and the CPU to compress NDI (about a fifth of a core). For six sites, a dedicated central computer with 6 cores or more and a GPU is recommended, especially if vMix runs on the same computer.
Supported feeds
H.264, H.265, MPEG-4 and MPEG-2 video, with AAC, Opus, MP2 or AC-3 audio (the audio is converted to 48 kHz stereo). VP9 and AV1 feeds (some WebRTC publishers) can't be sent to NDI yet.