NDI Mappable Node 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
An NDI Mappable Node has no device connection of its own. hi creates receiver Ports, and each Port is visible on the network as an NDI Source named <Node name> (<Port name>). An NDI receiver product selects that Source once. After that, routing in hi changes which NDI Source the named Source forwards, and the receiver follows without a change on the receiver.
Caution
A receiver selects the Source by its name. Choose the Node name and Port names before you set the receivers.
Before You Begin
-
Use Node admin and open Inventory > Nodes. See Manage Nodes.
-
Confirm the license and minimum hi version in Required Configuration.
-
Commission the NDI Core Integration first, and confirm that the required NDI Sources are visible in hi.
-
Confirm the network access in Network Requirements.
Configure Mappable Receivers
Use this configuration to give fixed NDI receivers a routable input in hi.
Device Configuration
-
Complete hi Configuration below first. Then, on each NDI receiver product, select the NDI Source named
<Node name> (<Port name>)for the matching receiver Port. Confirm with the receiver vendor how to select an NDI Source on that product.
hi Configuration
-
Select Inventory > Nodes, then select +, and add the NDI Mappable Node integration from the Add Nodes workflow.
-
Enter a Node name that no other NDI Source or Mappable Node uses. hi marks a Port and its Node as conflicting when an NDI Source with the same name already exists on the network.
-
In the Configuration group, set Amount of mappable receivers. The template default is
16. -
Create the Node.
-
Add or remove NDI input Ports as required.
-
In the Routing Matrix, route a discovered NDI Source to each receiver Port.
Settings Summary
|
Setting |
Device Side |
hi Side |
|---|---|---|
|
Source name |
NDI Source selected on the receiver |
|
|
Receiver count |
Number of receivers that use the Node |
Amount of mappable receivers
|
Common Checks
|
Symptom |
Check |
|---|---|
|
The receiver does not list the Source of a Port. |
Confirm that hi does not mark the Port or the Node as conflicting. hi does not create the Source when another NDI Source with the same name exists. Use a unique Node or Port name. |
|
The receiver does not list the Source of a Port, and the NDI Core Integration uses a Discovery Server. |
A sender configured for a Discovery Server does not announce through mDNS and is visible only to receivers that use the Discovery Server. Set the receiver to use the same Discovery Server. |
|
The receiver shows the wrong picture. |
Confirm the route of the receiver Port in hi, and confirm that the receiver selects the Source of the correct Port. |
Verify the Configuration
Route a noncritical NDI Source to one receiver Port and confirm that the receiver shows it. Route a different Source to the same Port and confirm that the receiver follows without a change on the receiver.