By default, NDI uses the mDNS (Bonjour / Zeroconf) discovery mechanism to advertise sources on a local area network, such that the NDI receiving device, which in this case is Zixi Broadcaster, can automatically discover and offer those sources.
This means that there are different requirements depending on the type deployment:
Using NDI within a local area network – on a local area network NDI will use the discovery mechanism to advertise the sources and Zixi Broadcaster will automatically discover these streams, while listing them in the Stream parameter of the NDI input stream.
Using NDI in the cloud – to make the streams discoverable in the cloud, you need to deploy an NDI Discovery Server and configure the NDI plug-in with the settings included in the following example:
On Windows: %PROGRAMDATA%\NewTek\NDI\ndi-config.v1.json
On Linux: $HOME/.newtek/ndi-config.v1.json
On Linux the NDI config files should be placed in the home directory of the user which Broadcaster is running as root. Thus, the file must be located at /root/.newtek/ndi-config.v1.json
Specifying the NDI Discovery Server
To specify NDI Discovery Server:
Open ndi-config.v1.json.
In the "networks" section, under "discovery" add the discovery server’s IP, which is the address of a host where NDI Discovery Server is working. For example, if you have it working on 192.168.0.253, then your config will have this section: