hi human interface®
English

Grass Valley K-Frame Series

Grass Valley K-Frame 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: v1.2.1

Overview

The Grass Valley® K-Frame™ integration receives program, preview, and key Tally states, dynamic Source labels, and ME bus status through GV Ethernet Tally.

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 configured GV Ethernet Tally Port on the switcher; hi defaults to 2012. hi keeps the whole Ethernet Tally session on the TCP connection that it opens to this Port, so the firewall needs no other Port. No callback to hi is used.

  • Frame Access List: The frame accepts Ethernet Tally connections only from IP addresses that you register on the frame. See Grass Valley K-Frame Series Integration Configuration.

Standards Conformance

Standard

Conformance

Notes

GV Ethernet Tally

Program
preview
key
and bus Tally with dynamic Source labels

Grass Valley protocol implemented by the hi integration

Operator Workflow

  • UI Surface in hi: Tally and Dynamic Labels

  • Capabilities: Program, preview, key, and bus Tally plus dynamic Source labels

  • Routing Semantics: The integration monitors switcher state and does not expose Crosspoint routing.

  • 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: Configure ME buses, AUX routing, macros, and production logic in the vendor tooling.

Connection Details

Property

Value

Protocol

GV Ethernet Tally

Transport

TCP

Default Port

2012 on the switcher by default
match its commissioned Ethernet Tally setting

Authentication

No credentials. hi sends the protocol's authentication request, and the frame accepts connections only from registered IP addresses

Encryption in Transit

None - plaintext TCP
no TLS defined by this protocol

Connection Model

TCP client

Required License

hiBase

Traffic Flow

Tally updates from the switcher over the TCP connection initiated by hi

Required Configuration

Parameter

Description

Default

Host / IP Address

IP address or hostname of the K-Frame switcher

-

Port

GV Ethernet Tally Port on the switcher

2012

Device-Side Setup

Follow Grass Valley K-Frame Series Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature

Access

Exposed Operation and Scope

Program/Preview/Key Tally

Read-only input

Receive supported Tally states.

Dynamic Source Labels

Read/write

Receive engineering Source names, and send hi labels to the frame as ECP engineering names, up to 16 for each message.

ME Bus Status

Read-only input

Monitor ME bus status; no ME setup or control is exposed.

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.

This integration supports the Grass Valley K-Frame range.

Tested With

  • Grass Valley K-Frame Series

  • Grass Valley Korona Series

Supported Product Range

  • Grass Valley K-Frame S-series

  • Grass Valley K-Frame V-series

  • Grass Valley K-Frame X-series

Potentially Compatible (Not Yet Verified)

  • Other switcher frames that send Tally through the Grass Valley Ethernet Tally protocol. Confirm the Ethernet Tally support of the exact frame and software release.

Known Limitations

  • Feedback is limited to Tally and Source-name messages received through the configured GV Ethernet Tally connection, and hi sends engineering Source names to the frame. No switcher control state is queried.

  • The frame sends Tally only to registered IP addresses. If the hi server address changes, for example after a failover to another server, register the new address on the frame.

  • The vendor protocol delivers Tally for the frame's suites. A frame with up to four suites needs a software release that supports the four-suite protocol version. Confirm the Tally of every suite that you use during commissioning. hi requests Ethernet Tally protocol version 3.0, which subscribes all four suites.

  • hi lists each Tally as Suite, ME, and output, for example Suite 1 PGM PgmA. The MEs are PGM and ME1 to ME4.

  • hi follows ME re-entries when it calculates Source Tally, and reports Tally only for engineering Sources that have a physical BNC input. The BNC number becomes the hi Source number.

What's Not Supported

  • Macro and shotbox authoring, ME setup, AUX control, panel calibration, and engineering configuration.

  • Firmware updates and device configuration backup.

  • Logical Source names, including panel, OLED, and menu names for each suite. hi writes engineering Source names only.

  • Tally of physical BNC outputs from the Output Tally map.

Trademarks

Note

Grass Valley and K-Frame are trademarks or registered trademarks of Grass Valley USA, LLC or its affiliated companies.

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