Skip to content
Callaba
PricingSign inDeploy NDI streaming
Product user guide

NDI discovered devices

See which NDI sources Callaba currently discovers and confirm source identity and activity before using them in production.

Find it in CallabaNDI® Tools → NDI® discovered devices
What this module does

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.

Continue this workflow in Callaba

Callaba Cloud NDI

The production module uses a source whose network visibility and identity were verified first.

See how the product works

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

  1. 01

    Start the NDI source and confirm it advertises the intended name.

  2. 02

    Refresh the discovered-device list.

  3. 03

    Match the device name and activity to the expected production source.

  4. 04

    Only then select it in an NDI adapter or supported Multiview input.

Workflow examples

Use this when

Preflight an NDI source before production

A new camera, decoder or software output has joined the NDI network.

NDI sourceAdvertised name
Discovery configInterfaces + discovery
Device inventoryVisible + active
Production moduleSelect source
Animated workflow diagram: Preflight an NDI source before production

How to build it

  1. 1

    Verify the source on the intended network and record its advertised name.

  2. 2

    Refresh Callaba discovery and locate that exact source.

  3. 3

    Confirm recent activity before selecting it downstream.

  4. 4

    Monitor the selected source in the adapter or Multiview workflow.

Use this when

Recover discovery after a network change

A known NDI source disappears after an interface, VLAN or discovery-server change.

Known sourceExpected identity
NDI configurationCompare baseline
Device inventoryRefresh discovery
Adapter or MultiviewRestore selection
Animated workflow diagram: Recover discovery after a network change

How to build it

  1. 1

    Confirm the source is still advertising the same name on the intended network.

  2. 2

    Compare Callaba network IPs and discovery addresses with the last working configuration.

  3. 3

    Restore the reviewed values, save once and wait for NDI processes to restart.

  4. 4

    Refresh discovery and verify the same source identity before reopening downstream output.

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.
Then do this

Correct NDI network configuration, save it, then refresh discovery before changing downstream modules.

Related product and API

API referenceList discovered NDI devicesAPI referenceRead NDI discovery activity