Grass Valley Kahuna / Kula 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.1.0

Overview

The Grass Valley^® Kahuna^™ and Kula^™ integration receives Source Tally through GV Kahuna Tally. It sends dynamic Source labels through a separate TSL UMD connection.

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 from hi on port 50001 for Tally, and outbound TCP or UDP, as set in Label Transport, on port 50014 for Dynamic Labels. No callback to hi is used.

Standards Conformance

Standard	Conformance	Notes
GV Kahuna Tally	Source Tally delivery	Grass Valley protocol implemented by the hi integration
TSL UMD Protocol v3.1 / v5.0	Outbound dynamic Source labels	Published TSL protocol implemented by the hi integration

Operator Workflow

UI Surface in hi: Tally and Dynamic Labels
Capabilities: Source 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 production switching, AUX buses, macros, and ME setup in the vendor tooling.

Connection Methods

Connection: GV Kahuna Tally

Connection Details

Property	Value
Protocol	GV Kahuna Tally
Transport	TCP
Default Port	50001
Authentication	None
Encryption in Transit	None the connection uses plaintext TCP
Connection Model	TCP client
Required License	hiBase
Traffic Flow	hi initiates the connection Tally flows from the switcher to hi

Connection: TSL UMD Dynamic Labels

Connection Details

Property	Value
Protocol	TSL UMD v3.1 / v5.0
Transport	TCP (default) or UDP set in Label Transport
Default Port	50014
Authentication	None at the TSL protocol layer
Encryption in Transit	None labels are sent in plaintext over TCP or UDP
Connection Model	TSL client
Required License	hiBase
Traffic Flow	Outbound from hi

Required Configuration

Parameter	Description	Default
Host / IP Address	IP address or hostname of the Kahuna/Kula switcher	-
Tally Port	GV Kahuna Tally connection	50001
Dynamic Label Port	TSL dynamic-label connection	50014
Label Protocol	TSL variant that the switcher uses to receive labels	TSL31
Label Transport	Network transport that the switcher uses to receive labels	TCP

Device-Side Setup

Follow Grass Valley Kahuna / Kula Series Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Source Tally	Read-only input	Receive Now, Next, and ISO 1 to ISO 30 Tally for each Source, with the Source name that the switcher sends.
Dynamic Source Labels	Write-only output	Send dynamic Source-name labels through TSL 3.1 or TSL 5.0.

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 Kahuna and Kula range.

Tested With

Grass Valley Kahuna Series
Grass Valley Kula Series

Supported Product Range

Grass Valley Kahuna 9600
Grass Valley Kahuna 6400

Potentially Compatible (Not Yet Verified)

Other switchers that send Tally and labels through the Grass Valley Kahuna Tally protocol. Confirm the Kahuna Tally support of the exact switcher and software release.

Known Limitations

Feedback is limited to the Tally and label messages listed under Supported Features; the integration does not query switcher configuration or control state.
External video inputs keep their switcher input number in hi. Internal Sources get offset numbers: stores start at 3001 and ME re-entries at 4001, with 100 added for each ME after ME 1. Sources of Switcher 2 and later add 10000 for each switcher.

What's Not Supported

Switcher routing, Crosspoint and AUX-Bus control, macro authoring, and ME setup.
Firmware updates, device configuration backup, panel calibration, and engineering configuration.
Bus Tally and Output Tally. The Kahuna Tally protocol sends them, and hi does not use them.

Trademarks

Note

Grass Valley, Kahuna, and Kula 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.