NDI Mappable Node

Driver Maturity

Production

Recommended for normal production use.

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.

Minimum hi Version: v2.7.3

Overview

An NDI^® Mappable Node creates operator-defined NDI receiver endpoints in hi. Operators select how many receiver Ports to create and then route discovered NDI Sources to those Ports.

Network Requirements

Connection Model: This configuration-only integration creates receiver Ports in hi and does not open an independent network connection.
Multicast / Unicast: Not applicable to the template itself.
VLAN / IGMP: Follow the NDI Core Integration requirements.
Bandwidth: The template adds no network traffic. Routed NDI Sources retain their normal media bandwidth.
IP Version: Not applicable to the template itself.
Firewall: The template needs no separate rule. Follow the NDI Core Integration and receiver requirements.

Standards Conformance

Standard	Conformance	Notes
NDI	Implemented through the NDI SDK	Vendor-defined protocol

Operator Workflow

UI Surface in hi: Inventory > Nodes, Routing Matrix, and the Mappable Node's add-Port controls
Resources Controlled: Operator-created NDI receiver Ports
Routing Semantics: Each receiver Port appears on the network as an NDI Source named <Node name> (<Port name>). Set the NDI receiver product to that Source. Routing in hi changes the NDI Source that this named Source forwards.
Discovery Behavior: The Mappable Node does not discover receivers.

Connection Details

Property	Value
Protocol	NDI
Transport	None no independent network connection is opened
Default Port	Not applicable
Authentication	Not applicable
Encryption in Transit	Not applicable
Connection Model	Operator-created receiver endpoints configured in the hi system
Required License	hiNDI
Traffic Flow	Routing control from hi media flows between NDI endpoints

Required Configuration

Parameter	Description	Default
Amount of mappable receivers	Number of NDI receiver Ports created with the Node, in the Configuration group; set when the Node is created. Each receiver Port is visible on the network as an NDI Source.	16

Device-Side Setup

Follow NDI Mappable Node Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Mappable Receiver Creation and Port Management	hi-side configuration	Create a configurable receiver Node and add its NDI input Ports in hi.
Source Assignment	Read/write	Assign a discovered NDI Source to a receiver Port.

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies devices that use the same protocol or connection method but have not been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

Tested With

Kiloview Multiview Player
NDI Tools
OBS Studio

Potentially Compatible (Not Yet Verified)

Other NDI senders and receivers, including software applications, that can send to or receive from the Sources this integration publishes.

Known Limitations

Receiver Ports are configured in hi; they are not discovered as receiver devices.
Validate the Port count and receiver mapping against the target NDI products before production use.
hi does not create the routed Source of a Port when another NDI Source with the same name already exists on the network. hi marks the Port and its Node as conflicting. Use a unique Node or Port name.

What's Not Supported

Automatic discovery of receiver products by the Mappable Node Template.
Firmware updates or receiver-device administration.

Trademarks

Note

NDI is a registered trademark of Vizrt NDI AB.

All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.

RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Vizrt NDI AB unless explicitly stated.