hi human interface®
hi human interface®
English
Breadcrumbs

TAG Video Systems Media Control System Integration Configuration

TAG Video Systems Media Control System 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

One TAG MCS Node in hi carries two independent outbound connections. The MCS API changes output layouts. TSL 5.0 sends UMD labels and Tally. Configure either or both. Each connection has its own Port and is verified separately.

Configuration

What hi Sees

Use When

MCS API

Outputs and layouts discovered from MCS, with layout selection per output.

Operators select layouts from hi.

TSL UMD

UMD labels and Tally states sent to MCS windows.

MCS windows must show hi labels and Tally.

Caution

The two connections use different Ports. The MCS API uses the HTTPS Port, and TSL uses the TSL listening Port configured in MCS. Do not enter one Port for both.

Before You Begin

  • Use Node admin and open Inventory > Nodes. See Manage Nodes.

  • Confirm the license and minimum hi version in Required Configuration.

  • Use the TAG Video Systems MCS administration tools for device-side steps. See the TAG Video Systems documentation for MCS.

  • Confirm the network access in Network Requirements.

Configure MCS API

Use this configuration to read outputs and layouts and to change an output layout.

Device Configuration

  1. Enable MCS API 5.1 over HTTPS. The MCS API needs no additional TAG license.

  2. hi signs in to MCS with a fixed account that cannot be configured in hi. Confirm with Riedel Customer Success that this account exists on the MCS system and can read outputs and layouts.

hi Configuration

  1. Add the Media Control System (MCS) integration in Inventory.

  2. Enter the MCS host or IP address and the HTTPS Port. The default is 443. Allow outbound HTTPS from hi to MCS.

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

  4. Confirm that the expected outputs and layouts are listed.

Configure TSL UMD

Use this configuration to send UMD labels and Tally to MCS.

Device Configuration

  1. Enable the TSL 5.0 input on MCS.

  2. Note the TSL listening Port.

hi Configuration

  1. For a TSL-only setup, add the Media Control System (MCS) integration in Inventory > Nodes, enter the MCS address and TSL listening Port, leave the MCS API connection disabled when it is not required, and create the Node with its TSL UMD connection. If the MCS API is already configured, open that Node instead.

  2. Enter the TSL listening Port of MCS. Allow outbound TCP from hi to MCS on this Port.

  3. Assign the UMD text and Tally Sources. See Configure UMD Labels.

Settings Summary

Setting

Device Side

hi Side

Protocol

TSL 5.0 input

TSL 5.0 UMD

Transport

TCP

TCP

Port

TSL listening Port

The same Port

Common Checks

Symptom

Check

Layouts are absent.

Confirm with Riedel Customer Success that the account that hi uses can read outputs and layouts through API 5.1.

UMD updates are absent.

Confirm the TSL listening Port separately from the HTTPS Port.

Verify the Configuration

Verify each connection that you configured. For the MCS API, select a test layout for a noncritical output and confirm that MCS applies it. For TSL UMD, change a UMD label and a Tally state in hi and confirm that the MCS window shows both.