Generic TSL-Compatible Switcher

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: v1.2.1

Overview

This integration receives Tally states and UMD labels from switchers that send TSL UMD v3.1 or v5.0. An optional TSL output sends dynamic Source labels back to the switcher.

Network Requirements

Connection Model: Inbound TSL to hi, with optional outbound dynamic-label delivery
Multicast / Unicast: Unicast only
Bandwidth: Control traffic only.
IP Version: IPv4 (IPv6 support varies by vendor - verify before relying on it)
Firewall: Allow inbound TCP or UDP to hi on port 31000 by default. If Dynamic Labels are enabled, allow outbound TCP or UDP to port 8901 by default.

Information

Send the switcher's TSL UMD output to the commissioned hi server address and this integration's listener Port. The default is 31000, and the permitted range is 31000 to 31999. If you change it, update the switcher's target and the firewall rule. The optional Dynamic-Label output uses a separate listener on the switcher, 8901 by default.

Standards Conformance

Standard	Conformance	Notes
TSL UMD Protocol v3.1 / v5.0	Inbound Tally and UMD plus optional outbound Dynamic Labels	Published TSL protocol implemented by the hi integration

Operator Workflow

UI Surface in hi: Tally, UMD, and Dynamic Labels
Capabilities: Inbound TSL Tally/UMD data and an optional separately configured dynamic-label output
Routing Semantics: The integration does not expose switcher routing or Crosspoint control.
Tally / UMD Relationship: hi receives switcher TSL UMD frames and reflects their Tally states and labels across Hardware Panels and Multiviewers.
Notes for Operators Familiar with the Vendor's Own Tooling: Configure production switching and TSL output in the vendor tooling; use hi for Tally, UMD, and dynamic-label workflows.

Connection Methods

Connection: Inbound TSL UMD

Connection Details

Property	Value
Protocol	TSL v3.1 / v5.0
Transport	TCP or UDP
Default Port	31000
Authentication	None at the TSL protocol layer
Encryption in Transit	None at the TSL protocol layer
Connection Model	TCP or UDP server for inbound TSL
Required License	hiBase
Traffic Flow	Inbound to hi

Connection: Optional Dynamic-Label Output

Connection Details

Property	Value
Protocol	TSL UMD v3.1 / v5.0
Transport	TCP or UDP
Default Port	8901
Authentication	None at the TSL protocol layer
Encryption in Transit	None at the TSL protocol layer
Connection Model	TSL client
Required License	hiBase
Traffic Flow	Outbound from hi

Required Configuration

Parameter	Description	Default
hi server Address	IP address of the hi server used as the switcher's TSL target	-
Tally Listening Port	Port on which hi receives TSL	31000
Dynamic-Label Address	Optional switcher address that receives TSL labels from hi	-
Dynamic-Label Port	Optional switcher TSL listening port	8901

Device-Side Setup

Follow Generic TSL-Compatible Switcher Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Tally States	Read-only input	Receive the Tally states supported by the selected TSL version.
UMD Label Text (TSL v3.1)	Read-only input	Receive legacy under-monitor display label messages.
UMD Label Text (TSL v5.0)	Read-only input	Receive screen/display-addressed variable-length label messages.
Dynamic Source Labels	Write-only output	Send Source labels through the optional, separately configured TSL output.

Device Coverage

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

A device-specific integration is also available for FOR-A HVS Series and Ross Video Carbonite Series.

Tested With

Barco Event Master E2
Guramex Broadster
Ross Video Acuity
Ross Video Carbonite Series
StudioCoast vMix

Potentially Compatible (Not Yet Verified)

Other switchers that send TSL v3.1 or TSL v5.0 Tally and UMD messages supported by this integration.

Known Limitations

The server receives TSL from the switcher. Dynamic-label output, when required, uses a separately configured client.
Tally-state interpretation depends on the selected TSL version and sending device implementation.
TSL UMD v3.1 addresses displays 0 to 126, carries a fixed 16-character label, and has four tally bits and a brightness field per display. TSL UMD v5.0 addresses a screen and a display with 16-bit indexes (65535 is reserved as a broadcast value) and carries variable-length text with separate left, text, and right tally indications. Neither version acknowledges messages, so the sender cannot confirm that a message was received.

What's Not Supported

Switcher routing, Crosspoint control, macro authoring, and ME setup.
Firmware updates, device configuration backup, panel calibration, and engineering configuration.

Trademarks

Note

TSL is a trademark of TSL Products Ltd.