Skip to main content

NDI discovery server

If you are trying to point the NDI output of Twenty-One Encoder to one or more NDI Discovery Servers, you have to change the appropriate parameter in the .ini configuration file in the Advanced setup:

Find and replace the line containing NDI_DISCOVERY= with the destination IP(s) of the NDI Discovery server(s). Use commas to separate multiple servers, e.g.,

NDI_DISCOVERY=192.168.101.55,192.168.101.56

Warning: When the NDI Discovery Server is set, the NDI output (sender) doesn’t propagate itself using mDNS, just to the Discovery Server. NDI input (receiver) receives traffic from both mDNS and Discovery Server. This is how NDI works and you can’t change it.

  • Q: I can’t discover Twenty-one encoder’s NDI output​

Check that your network interface is configured for “Input/Output” or “Input/Output and Administration” in the UI Setup. This effectively configures the firewall in the OS.

  • Q: I can discover Twenty-one encoder’s NDI output, but it doesn’t play​

Since NDI 5, NDI uses RUDP (Reliable UDP) as a communication protocol. Some network cards have problems with RUDP. In the NDI Access Manager application on your receiver device, you can set the “Receiver Mode” to “Single-TCP” and restart both the NDI output pipeline in Twenty-one encoder and the NDI application on your receiver device.