NDI Stream Discovery

to allow ndi stream discovery, you can use one of the following options mdns multicast discovery docid\ wbckncnlgzh7yncez0hcx ndi stream discovery docid\ wbckncnlgzh7yncez0hcx configuring ndi stream discovery using mdns multicast discovery on a local area network, ndi will use the mdns 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 ndi uses the mdns (bonjour / zeroconf) discovery mechanism to create a zero configuration environment for the discovery of ndi streams available on the lan through mdns, devices such as the zixi broadcaster can discover available ndi streams for processing the mdns (bonjour / zeroconf) discovery mechanism should be installed as required according to the system's os, as described in the os support docid\ wbckncnlgzh7yncez0hcx section os support the use of mdns requires operating system support as follows windows windows 10 has mdns support built in, which is necessary for any ndi applications running on windows linux (centos 7/rhel 9) the recommended platform for the zixi broadcaster is centos 7 mdns support is provided by the avahi package, which typically is not installed by default on centos 7 configuring mdns multicast discovery on a local area network on windows, the mdns service is pre installed and does not require additional steps for linux, follow the instructions below installing avahi on centos 7 to install avahi on centos 7 run the following commands on the server hosting the zixi broadcaster sudo yum update sudo yum install avahi avahi tools sudo systemctl enable avahi daemon sudo systemctl start avahi daemon to check if the avahi daemon is running, run the following command avahi browse at installing avahi on rhel 9 to install avahi on rhel 9 linux run the following commands on the server hosting the zixi broadcaster sudo dnf update sudo dnf install avahi avahi tools sudo systemctl enable avahi daemon sudo systemctl start avahi daemon to check if the avahi daemon is running, run the following command avahi browse at enabling multicast network support the mdns ethernet frame is a multicast udp packet that broadcasts to mac address 01 00 5e 00 00\ fb(for ipv4) ipv4 address 224 0 0 251 udp port 5353 you need to verify that the lan where ndi streams are present is multicast enabled and that all systems needing access to ndi streams, such as the zixi broadcaster, do not block mdns via their firewall configuring ndi stream discovery using ndi discovery server 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 instructions the configuration process requires modifying the ndi config file with the relevant settings, as explained below, and placing the new file in the relevant location on the server to configure the ndi config file locate the ndi config file on windows %programdata%\newtek\ndi\ndi config v1 json on linux $home/ newtek/ndi config v1 json 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 the ndi discovery server is working for example, if you have it working on 192 168 0 253, then your config will have this section "networks" {"ips" "","discovery" "192 168 0 253"}, set the unicast setting to ‘true’ "unicast" { "recv" { "enable" true }, "send" { "enable" true } set the tcp setting to ‘true’ "tcp" { "recv" { "enable" true }, "send" { "enable" true } save the config file if using linux, place the edited config file in the home directory of the user under which broadcaster is running as root thus, the file must be located at /root/ newtek/ndi config v1 json restart the zixibc service systemctl stop zixibc systemctl start zixibc config file configuration example { "ndi" { "groups" { "recv" "\\"public\\"", "send" "\\"public\\"" }, "multicast" { "recv" { "enable" false, "subnets" "" }, "send" { "enable" false, "netmask" "255 255 255 0", "netprefix" "239 192 136 100" } }, "networks" { "discovery" "22 127 94 57", "ips" "" }, "tcp" { "recv" { "enable" true }, "send" { "enable" true } }, "unicast" { "recv" { "enable" true }, "send" { "enable" true } } } }