Set up NDI® network configuration in Callaba

Configure Callaba's NDI network layer from the authenticated dashboard rather than editing host files in a terminal. The basic fields cover the common setup; the built-in import and JSON editor expose the advanced NDI options when you need them. Start with the Callaba NDI product, then use this page for the exact UI workflow.

Option 1: Using predefined fields

For basic setups, Callaba provides predefined fields in the NDI® configuration section.

Here, you can input details like:

Machine Name: Assign a unique name to your device.
Discovery IP: Enter the discovery IP address that will allow Callaba to locate NDI® devices on your network.
Networks IPs (source IPs): enter the specific local interface addresses Callaba should bind for NDI. This is a list of explicit IP addresses, not a CIDR or address-range field.

These fields simplify the process, ensuring that even basic setups can be done quickly.

Option 2: Using the Live Editor

For more complex settings, you can directly edit your configuration in the live editor at the bottom of the panel. The live editor allows you to:

Edit or create custom configurations directly in JSON format.
Customize advanced settings such as send and receive groups, allowed network adapters, multicast and transport behavior.
Use NDI groups to scope discovery visibility. Groups are not user authentication, encryption or a firewall; dashboard authentication controls who can save the configuration, while network ACLs and segmentation remain the network-security boundary.

Option 3: Importing Configuration Files

If you already have a configuration file prepared, Callaba allows you to import it.

You can drag and drop a .json or .txt file into the live editor.

After importing, review the JSON and select Save. The host does not need a full system reboot, but saving the configuration restarts active NDI processes so the new settings can take effect. Schedule the change outside an active production window.

This is especially useful for deploying pre-configured environments or replicating setups across multiple devices.

Example Configuration

Illustration: Example Configuration

In the screenshot example:

The machine name is set as “very cool.”
The discovery IP is set to 172.32.213.96.
Source interface IPs are configured as 192.168.2.14 and 192.168.2.16.
The multicast setting is disabled, which can be easily adjusted by changing the enable field to true.