EVS DYVI Series

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.2.0

Overview

The EVS^® DYVI^™ integration uses Ember+ to receive the states of the DYVI tally systems, to read Source names, and to send dynamic Source labels.

Network Requirements

Connection Model: Outbound from hi
Multicast / Unicast: Unicast only
Bandwidth: Control traffic only.
IP Version: IPv4 (IPv6 support varies by vendor - verify before relying on it)
Firewall: Allow outbound TCP connections from hi to the DYVI Ember+ provider on port 9000. DYVI does not open connections to hi.

Standards Conformance

Standard	Conformance	Notes
Ember+ (Lawo)	Glow DTD parameter tree per Ember+ spec	Open community specification used as a de facto standard widely adopted

Operator Workflow

UI Surface in hi: Tally and Dynamic Labels
Capabilities: Tally system states, Source names, and dynamic Source labels
Routing Semantics: The integration does not expose Crosspoint routing or AUX control in the hi web interface.
Tally / UMD Relationship: Tally state is sourced from the switcher's own Tally engine; hi reflects the switcher's Tally state into the wider system.
Notes for Operators Familiar with the Vendor's Own Tooling: Continue to configure productions, transitions, Snapshots, macros, and routing in the vendor tooling.

Connection Details

Property	Value
Protocol	EVS DYVI (Ember+)
Transport	TCP
Default Port	9000
Authentication	None - the Ember+ protocol does not define authentication access control must be managed at the network level
Encryption in Transit	None - Ember+ uses plaintext TCP no TLS defined
Connection Model	Ember+ consumer (TCP client)
Required License	hiBase
Traffic Flow	Outbound from hi

Required Configuration

Parameter	Description	Default
Host / IP Address	IP address or hostname of the DYVI switcher	-
Port	Ember+ Port	9000

Device-Side Setup

Follow EVS DYVI Series Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Tally Systems	Read-only updates	Receive Tally System 1 through Tally System 31, which the DYVI Production assigns.
Source Names	Read-only updates	Read the DYVI Source names. hi uses the name of the assigned Global Source, or the SDI-input name when no Global Source is assigned.
Dynamic Source Labels	Write-only output	Write the hi label to both the SDI-input name and the assigned Global Source name. hi skips SDI inputs that have no Global Source assigned.

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.

Tested With

EVS DYVI

Potentially Compatible (Not Yet Verified)

EVS switchers that expose a compatible Ember+ Tally surface.

Known Limitations

Tally and label feedback is limited to the Parameters exposed by the configured Ember+ provider.
The DYVI Ember+ tree depends on the system topology and the loaded DYVI Production. Only a few top-level Nodes are always present; confirm the exposed Nodes after you load a Production.
The Ember+ interface exposes tally systems 1 to 31. Tally system 32 is not available.
Source-name labels written through the Ember+ interface are temporary overrides. They are not stored with the DYVI Production and last until a new Production is loaded.
When a different Production is loaded, hi reads the Ember+ tree again and updates its Sources and Tally.
hi sends an Ember+ keep-alive request every 5 seconds, and it disconnects when the provider does not answer within 10 seconds. hi requires the provider to answer keep-alive requests.

What's Not Supported

Source routing, transitions, AUX-Bus control, Snapshot recall, macro control, and ME setup.
Firmware updates, device configuration backup, panel calibration, and engineering configuration.
Multiviewer window source, label, layout, and Tally settings; Tally-system assignment to SDI outputs; and renaming of Productions, scenes, stages, and transitions. The DYVI Ember+ interface provides them, and hi writes only Source names.
The DYVI PixTally protocol for switcher Tally. PixTally is a separate DYVI Tally interface, and hi reads Tally through Ember+ only.
Ember+ Functions, including Qualified Functions, and function invocation. The Ember+ specification defines them from Glow 2.20, and hi never sends an Invoke command.
Ember+ Templates, including Qualified Templates, and template references. The specification defines them from Glow 2.40. hi requests all fields of each element, and it does not resolve template references.

Trademarks

Note

EVS and DYVI are trademarks of EVS Broadcast Equipment SA.

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