NDI Core Integration Configuration

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Configuration Overview

hi finds NDI Sources either through local mDNS-SD or through one or more NDI Discovery Servers. The NDI Discovery Server Host setting selects the method.

Configuration	What hi Sees	Use When
Local Network Discovery	NDI Sources on the local network segment.	All Sources are reachable by multicast from the hi server.
External Discovery Server	NDI Sources registered with the listed Discovery Servers.	Sources are on other network segments, or the site uses a Discovery Server.

Caution

Discovery supplies Sources only. Create and map receiver Nodes and input Ports manually. See NDI Mappable Node.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and hi version in Required Configuration.
Confirm the network access in Network Requirements.

Configure Local Network Discovery

Use this configuration when no Discovery Server is used.

Device Configuration

Enable NDI output on the Source systems. See the vendor documentation.
Make sure the Source systems and the hi server share a network segment that passes mDNS multicast.
Where the NDI product uses access groups, make sure the Source is in the default NDI group (public). hi discovers Sources only in that group. See the NDI documentation.

hi Configuration

Add the NDI Core Integration in Inventory. Only one NDI Core Integration Node can exist in a system.
Leave NDI Discovery Server Host empty.
Create the Node and wait for it to initialize.

Settings Summary

Setting	Device Side	hi Side
Discovery method	NDI output is enabled on the same segment.	NDI Discovery Server Host is empty.

Configure External Discovery Server

Use this configuration when Sources register with an NDI Discovery Server.

Device Configuration

Enable NDI output on the Source systems and point them at the Discovery Server. See the NDI documentation for the Discovery Server setting.
Record the address of each Discovery Server. The Discovery Server uses TCP port 5959 by default; permit it from the hi server. The Discovery Server is an external NDI component; hi does not host one.

hi Configuration

Add the NDI Core Integration in Inventory. Only one NDI Core Integration Node can exist in a system.
Enter the Discovery Server address in NDI Discovery Server Host. Separate several servers with commas. Each entry can include a port, for example 192.0.2.10:5959. Port 5959 applies when an entry has no port.
Create the Node and wait for it to initialize.

Settings Summary

Setting	Device Side	hi Side
Discovery Server	Address of the Discovery Server	NDI Discovery Server Host

Common Checks

Symptom	Check
No Sources appear.	Confirm whether NDI Discovery Server Host is empty (mDNS-SD) or lists the Discovery Server, and that the matching network access is open.
Sources on other segments are missing.	Local mDNS-SD (NDI service type `_ndi._tcp`) does not cross segments that block multicast. Use an external Discovery Server.
Sources that use a Discovery Server are missing while NDI Discovery Server Host is empty.	A sender configured for a Discovery Server stops announcing through mDNS and is visible only to receivers that use the Discovery Server. Enter the same Discovery Server in NDI Discovery Server Host.
Receivers are missing.	Receiver products are not discovered. Create them with NDI Mappable Node .

Verify the Configuration

Confirm that the expected NDI Sources appear in hi. Route one Source to a test receiver Port and confirm the assignment on both systems.

NDI Mappable Node to create receiver Nodes and input Ports.