hi human interface®
hi human interface®
English
Breadcrumbs

Blackmagic Design HyperDeck Series

Blackmagic Design HyperDeck 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.5.1

Overview

The Blackmagic Design® HyperDeck™ integration uses the HyperDeck Ethernet Protocol. hi loads clip and transport state, manages the playlist, and provides play, pause, cue, and stop actions.

Network Requirements

  • Connection Model: Outbound from hi

  • Multicast / Unicast: Unicast only

  • Firewall: Allow outbound TCP from hi to the HyperDeck on Port 9993.

  • Callback: No inbound connection to hi is used; notifications return over the established control session.

  • Security: Keep the plaintext control connection on a trusted management network.

Standards Conformance

Standard

Conformance

Notes

Blackmagic HyperDeck Ethernet Protocol 1.3

TCP control
state readback
and notifications

Vendor protocol implemented by the hi integration

Operator Workflow

  • UI Surface in hi: Control Panel, Routing Matrix, and Inventory

  • Resources Exposed: Clips, playlist items, storage slots, and transport state

  • Routing Semantics: The integration exposes the input and output Ports set by Input Count and Output Count, one of each by default, for Topology and routing workflows.

  • Tally / UMD Relationship: Derived playback state is available to hi Tally workflows. This does not replace production-switcher Tally or UMD signaling.

Connection Methods

Connection: Blackmagic HyperDeck Ethernet Protocol 1.3

Property

Value

Protocol

Blackmagic HyperDeck Ethernet Protocol 1.3

Transport

TCP

Default Port

9993

Authentication

hi sends no credentials. Configure the HyperDeck Ethernet Protocol to accept connections without authentication.

Encryption in Transit

hi uses plaintext TCP and does not negotiate an encrypted HyperDeck session.

Connection Model

Persistent TCP

Required License

hiBase

Traffic Flow

Outbound from hi

Connection: HyperDeck Tally Workflow

hi makes derived playback state available to Tally workflows. No additional network endpoint is required.

Connection: HyperDeck Static Crosspoint Model

The integration creates the input and output Ports set by Input Count and Output Count, one of each by default, for hi Topology and routing workflows. This is a local model and does not send a second protocol to the HyperDeck.

Required Configuration

Parameter

Description

Default

Host / IP Address

IP address or hostname of the HyperDeck

-

Port

BMD Ethernet Protocol port

9993

Input Count

Number of input Ports created for the Node
available only when the Node is created

1

Output Count

Number of output Ports created for the Node
available only when the Node is created

1

Device-Side Setup

Follow Blackmagic Design HyperDeck Series Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature

Access

Exposed Operation and Scope

Clip
Disk
and Transport State

Read-only

Read clips, disk slots, and transport state from the active device slot.

hi Playlist

hi-side configuration

Build and reorder the playlist in hi from clips reported by the device; this does not ingest or transfer media.

Play
Pause
Cue
and Stop

Write-only commands

Start, pause, cue, or stop playback. Stop halts playback and returns to the first clip on the timeline; Pause halts at the current position. Recording, jog, shuttle, and manual slot selection are not exposed.

State Notifications

Read-only updates

Update hi when clip, slot, or transport state changes.

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 Blackmagic Design HyperDeck range.

Tested With

  • Blackmagic Design HyperDeck Studio Mini

  • Blackmagic Design HyperDeck Studio

Supported Product Range

  • Blackmagic Design HyperDeck Studio

  • Blackmagic Design HyperDeck Studio Mini

  • Blackmagic Design HyperDeck Studio HD Mini

  • Blackmagic Design HyperDeck Studio HD Plus

  • Blackmagic Design HyperDeck Studio HD Pro

  • Blackmagic Design HyperDeck Studio 4K Pro

  • Blackmagic Design HyperDeck Shuttle HD

  • Blackmagic Design HyperDeck Extreme 8K HDR

Potentially Compatible (Not Yet Verified)

  • Blackmagic Design HyperDeck Studio Pro

  • HyperDeck models not listed under Supported Product Range that support HyperDeck Ethernet Protocol 1.3.

Known Limitations

  • The hi v3.0.0 integration uses HyperDeck Ethernet Protocol 1.3 on TCP Port 9993.

  • Validate clip, slot, timeline, and transport behavior on the installed device.

  • The HyperDeck Ethernet Protocol lets a device require authentication. hi does not configure credentials for this integration, so confirm that the HyperDeck accepts the connection without them.

  • Supported commands and storage formats vary by HyperDeck model and firmware. Confirm the clips and slots that hi reports against the device.

  • Cue and Play replace the HyperDeck timeline. hi clears the timeline and adds the selected clip, so a timeline built on the deck is lost.

  • hi polls the transport state every 250 ms and the disk list every 30 seconds. New clips on the media can take up to 30 seconds to appear in hi.

  • hi subscribes to transport and slot notifications only. The HyperDeck Ethernet Protocol offers further notification classes, such as configuration and remote state, and hi does not use them.

  • hi connects to one HyperDeck address and does not use a redundant connection.

What's Not Supported

  • This integration does not use the separate HyperDeck REST API; it controls the device through the Ethernet Protocol listed above.

  • Recording, jog, shuttle, and manual slot selection are not available as operator actions.

  • Clip ingest, transcoding, timeline authoring, and direct media-file transfer.

  • Arbitrary device configuration, firmware updates, and device configuration backup.

  • Input and file-format configuration, variable-speed play, preview mode, play ranges, and media formatting. The HyperDeck Ethernet Protocol provides them, and hi does not use them.

Trademarks

Note

Blackmagic Design and HyperDeck are trademarks of Blackmagic Design Pty Ltd.

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