hi human interface®
English

AMWA NMOS Core Integration Configuration

AMWA NMOS Core Integration Configuration

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.

Configuration Overview

The NMOS Core Integration needs an IS-04 registry. Choose how it finds the registry, and decide whether hi also creates its own NMOS Registry.

Configuration

What hi Sees

Use When

Auto Discovery

hi finds a registry on its own and ignores the Registry URL setting.

The registry is advertised on the network.

Manual Registry URL

hi connects to the registry at the URL you enter.

The registry is not advertised, or you must select a specific registry.

hi NMOS Registry

The Core Integration creates the hi NMOS Registry together with itself.

NMOS Nodes should register with hi.

Caution

Automatic RTP and Master Enable Management is on by default. Set it to No when the connected devices or media network must control Master Enable and RTP Enable states externally.

Before You Begin

Configure Auto Discovery

Use this configuration when the registry is advertised on the network.

Device Configuration

  1. Enable the IS-04 and IS-05 services on the participating NMOS Nodes. Each Node registers its IS-04 resources with the registry and advertises its IS-05 Connection API in its IS-04 Node resource.

  2. Make sure the registry advertises the IS-04 Query service (_nmos-query._tcp) through multicast DNS on a network segment that reaches the hi server. A registry that does not advertise this service needs the Manual Registry URL configuration.

hi Configuration

  1. Add the NMOS Core Integration in Inventory, and create the Node.

  2. Open the Node and confirm that Auto Discovery is Yes. This setting is available after the Node is created.

  3. Wait for the Node to initialize.

Settings Summary

Setting

Device Side

hi Side

Registry location

The registry is advertised on the network.

Auto Discovery is Yes; Registry URL is ignored.

Configure Manual Registry URL

Use this configuration when automatic discovery does not find the registry you want.

Device Configuration

  1. Record the full registry URL, including http:// or https://, the host, and the port.

hi Configuration

  1. Add the NMOS Core Integration in Inventory, and create the Node.

  2. Open the Node and set Auto Discovery to No. These settings are available after the Node is created.

  3. Enter the registry address in Registry URL.

  4. Save the Node and wait for it to initialize.

Settings Summary

Setting

Device Side

hi Side

Registry location

Full registry URL

Registry URL with Auto Discovery set to No

Configure hi NMOS Registry

Use this configuration when hi should provide the registry that NMOS Nodes register with.

Device Configuration

  1. Configure the NMOS Nodes to register with the hi registry. See NMOS Registry for the endpoint and settings.

hi Configuration

  1. Add the NMOS Core Integration in Inventory.

  2. Set Create NMOS Registry to Yes. Create NMOS Registry is available only when the Node is created. To add the hi NMOS Registry later, add the NMOS Registry in Inventory.

  3. Create the Node and wait for it to initialize.

  4. Open the hi NMOS Registry Node and select its network Interface. See NMOS Registry.

Common Checks

Symptom

Check

No NMOS resources appear.

Confirm that the Nodes are registered with the registry that hi uses, for example by querying its IS-04 Query API. Confirm whether Auto Discovery is Yes or No. With No, confirm that Registry URL is a full http:// or https:// URL. With Yes, the Registry URL is ignored.

With Auto Discovery set to Yes, hi uses a different registry than expected.

hi selects the advertised IS-04 Query service with the lowest pri value. AMWA defines 0 to 99 as production priority values, with 0 as the highest priority, and reserves 100 and higher for development. Set the priority of the registries, or use the Manual Registry URL configuration.

hi changes Master Enable or RTP Enable states that another system controls.

Set Automatic RTP and Master Enable Management to No. hi then leaves the states unchanged and hides the Node-level management settings.

The Node-level Manage Master Enable, Manage Primary RTP Enable, or Manage Secondary RTP Enable settings are missing.

Confirm that Automatic RTP and Master Enable Management is Yes and that the NMOS Node is eligible.

Verify the Configuration

Confirm that the advertised Query, Node, and Connection API URLs are reachable from the hi server. Confirm that discovered NMOS Nodes and their Ports appear in hi and that updates arrive without a manual refresh. Apply one test IS-05 connection in a non-production setting and confirm the active transport parameters on the sender and receiver.