Discovery is the evidence layer between NDI network configuration and a production adapter or Multiview input. If the device is absent here, downstream selection cannot repair discovery.
Before you start
NDI devices reachable from the configured Callaba interfaces and discovery addresses.
A unique, recognizable NDI source name.
Settings explained
These are the controls an operator needs to understand. Internal field names and implementation events are intentionally omitted.
Inventory
Read the sources currently visible to Callaba.
- Device name
NDI source identity advertised on the network.
- Activity
Recent discovery/process state used to distinguish visible and stale devices.
- Refresh
Update the discovered-device inventory after a network or source change.
Safe first workflow
- 01
Start the NDI source and confirm it advertises the intended name.
- 02
Refresh the discovered-device list.
- 03
Match the device name and activity to the expected production source.
- 04
Only then select it in an NDI adapter or supported Multiview input.
Workflow examples
Preflight an NDI source before production
A new camera, decoder or software output has joined the NDI network.
How to build it
- 1
Verify the source on the intended network and record its advertised name.
- 2
Refresh Callaba discovery and locate that exact source.
- 3
Confirm recent activity before selecting it downstream.
- 4
Monitor the selected source in the adapter or Multiview workflow.
Verify the result
- The expected NDI name appears after refresh.
- Activity is recent while the source is running.
- The same source identity appears in downstream selectors.
Troubleshooting
The device does not appear
Check- Confirm the source is advertising.
- Review Callaba interfaces, discovery addresses and network reachability.
Correct NDI network configuration, save it, then refresh discovery before changing downstream modules.