This page owns NDI network visibility. Use the guided fields for normal changes and the JSON editor only when you understand the complete NDI configuration being imported.
Before you start
The IP addresses or discovery server names approved for the NDI network.
A maintenance window: saving NDI configuration restarts active NDI processes.
A copy of the current configuration before importing or editing JSON.
Settings explained
These are the controls an operator needs to understand. Internal field names and implementation events are intentionally omitted.
Network identity
Control how this Callaba instance participates in NDI discovery.
- Machine name
Name used by Callaba on the NDI network.
- Discovery addresses
NDI discovery server addresses used to find sources across the approved network.
- Network IPs
Interfaces or IP addresses Callaba should use for NDI traffic.
Full configuration
Advanced but UI-managed configuration.
- Import JSON or text
Load an approved NDI configuration into the editor.
- Live configuration editor
Review and edit the full NDI configuration before saving.
- Restore defaults
Return the editor to the Callaba default configuration.
Record the existing values before restoring.
Safe first workflow
- 01
Record the current machine name, discovery addresses and network IPs.
- 02
Enter only the interfaces and discovery endpoints required by the production network.
- 03
Review the generated configuration in the live editor.
- 04
Save during a maintenance window and wait for NDI processes to restart.
- 05
Refresh Discovered devices and confirm the expected sources return.
Workflow examples
Connect Callaba to a routed NDI environment
NDI sources live outside the default local discovery domain.
How to build it
- 1
Collect the approved local interface IPs and discovery server addresses.
- 2
Set the Callaba machine name, discovery addresses and network IPs.
- 3
Review and save the configuration during the maintenance window.
- 4
Refresh the discovered-device inventory and compare it with the expected source list.
Verify the result
- Saved values remain visible after reload.
- Expected devices reappear after NDI processes restart.
- Unapproved interfaces or discovery addresses are absent.
Troubleshooting
Sources disappear after saving
Check- Compare the saved interfaces and discovery addresses with the baseline.
- Wait for NDI processes to restart.
- Refresh device inventory.
Restore the last known configuration, save once, and verify discovery before changing adapters.