TAG Video Systems Media Control System

Driver Maturity

Production

Recommended for normal production use.

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.

Minimum hi Version: v2.7.7

Overview

The TAG Video Systems^® Media Control System combines HTTPS layout control with outbound TSL 5.0 UMD messaging. hi polls output and layout data every 30 seconds, so layout changes made on MCS can take up to 30 seconds to appear in hi. hi changes output layouts, and sends UMD labels and Tally states.

Network Requirements

Connection Model: Outbound from hi
Multicast / Unicast: Unicast only
VLAN / IGMP: No multicast configuration is required.
Bandwidth: Control traffic only.
IP Version: IPv4 (IPv6 support varies by vendor - verify before relying on it)
Firewall: Allow outbound HTTPS from hi to MCS on Port 443. Allow outbound TCP to the configured TSL listening Port.

Standards Conformance

Standard	Conformance	Notes
TAG MCS API 5.1	Authentication output and layout discovery polling and output layout selection	Vendor API implemented by the hi integration
TSL UMD Protocol v5.0	Outbound label and Tally messaging	Published TSL protocol widely implemented by Multiviewers

Operator Workflow

UI Surface in hi: Inventory, Parameter Control, and UMD settings
Layers Controlled: Multiviewer parameters, Tally, and UMD labels
Routing Semantics: hi exposes each discovered MCS output and its available layout selections.
Notes for Operators Familiar with the Vendor's Own Tooling: Use the vendor tooling for engineering setup; use hi for the operational control surface exposed by this integration.

Connection Methods

hi configures two outbound surfaces: MCS API 5.1 and TSL 5.0 UMD.

Connection: TAG MCS API

Connection Details

Property	Value
Protocol	TAG MCS API 5.1
Transport	HTTPS
Default Port	443
Authentication	MCS sign-in with a bearer-token session. hi signs in with a fixed account that cannot be configured in hi. Contact Riedel Customer Success to confirm the account that the MCS system must provide.
Encryption in Transit	TLS (HTTPS). hi does not validate the MCS server certificate.
Connection Model	HTTPS request/response with periodic state polling
Required License	hiBase
Traffic Flow	Outbound from hi

Required Configuration

Parameter	Description	Default
Host / IP Address	IP address or hostname of TAG MCS	-
Port	HTTPS API Port	443

Supported Features

Feature	Access	Exposed Operation and Scope
Model Discovery	Read-only	Read the devices, outputs, and layouts exposed by the MCS API.
Output Layout Selection	Read/write	Read the current layout selection and change the layout assigned to an output through the MCS API.

Known Limitations

API control is limited to output layout selection.

Connection: TSL 5.0 UMD

Connection Details

Property	Value
Protocol	TSL 5.0 UMD
Transport	TCP
Default Port	hi pre-fills `443`. Replace it with the TSL listening Port configured in MCS.
Authentication	None - the TSL UMD protocol does not define authentication unidirectional display protocol
Encryption in Transit	None - TSL UMD uses plaintext TCP
Connection Model	TCP client
Required License	hiBase
Traffic Flow	Outbound from hi

Required Configuration

Parameter	Description	Default
Host / IP Address	IP address or hostname of TAG MCS	-
Port	TSL listening Port. hi pre-fills `443`, which is the HTTPS port, so replace it.	443

Supported Features

Feature	Access	Exposed Operation and Scope
Tally States	Write-only output	Send configured Tally states to each display; the TSL connection does not read display state.
UMD Label Text	Write-only output	Send TSL 5.0 under-monitor display text to MCS.

Known Limitations

TSL provides outbound UMD and Tally display messaging only; use the MCS API surface for layout selection.

Required Configuration

Each connection has its own required configuration. See Connection: TAG MCS API and Connection: TSL 5.0 UMD.

Device-Side Setup

Follow TAG Video Systems Media Control System Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Connection	Access	Exposed Operation and Scope
TAG MCS API 5.1	Read-only discovery and read/write layout selection	Read exposed devices, outputs, and layouts; read or change an output's selected layout.
TSL 5.0 UMD	Write-only output	Send configured Tally states and UMD label text to MCS; no device-state feedback is read over this connection.

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies devices that use the same protocol or connection method but have not been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

Tested With

TAG Video Systems Media Control System (MCS)

Potentially Compatible (Not Yet Verified)

Other TAG Video Systems products that expose the supported MCS API or TSL 5.0 UMD surface.

Known Limitations

Product firmware compatibility must be verified during commissioning.
hi uses only the operations listed under Supported Features. The TAG API covers more areas, such as monitoring and notifications.
If layouts are absent, confirm with Riedel Customer Success that the account that hi uses can read outputs and layouts through API 5.1.
If UMD updates are absent, verify the configured TSL listening Port separately from the HTTPS API Port.
MCS supports up to 100 tiles per mosaic output and up to 8 UMDs per tile. Tally and UMD text reach a tile through TSL or the TAG API.

What's Not Supported

Firmware updates and engineering-level configuration remain in the vendor tooling.

Trademarks

Note

TAG Video Systems and MCS are trademarks of TAG Video Systems Ltd.

All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.

RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with TAG Video Systems unless explicitly stated.