Blackmagic Design Videohub

Blackmagic Design Videohub

Minimum hi Version: v2.3.0

Overview

The Blackmagic Design^® Videohub integration reads input and output labels, monitors routing state, and sets video Crosspoints over TCP.

Network Requirements

• Allow outbound TCP from hi to the Videohub on Port 9990 by default.

• No callback or inbound connection to hi is used.

• Keep the unauthenticated plaintext control interface on a trusted management network.

Standards Conformance

Operator Workflow

• UI Surface in hi: Routing Matrix and Inventory

• Layers Controlled: Video routing

• Routing Semantics: hi builds Sources and Destinations from the label blocks that the device sends.

• Notes for Operators Familiar with the Vendor's Own Tooling: Use the vendor tooling for labels, locks, monitoring/serial routing, and engineering configuration. Use hi for video routing and label display.

Connection Details

Required Configuration

Device-Side Setup

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

Supported Features

Device Coverage

Tested With identifies devices that have been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

This integration supports the Blackmagic Design Videohub range.

Tested With

• Blackmagic Videohub 10x10 12G

Supported Product Range

Networked Videohub models that expose the supported TCP control surface are in range. The Videohub Ethernet Protocol also covers the Smart Videohub, Compact Videohub, Micro Videohub, Universal Videohub, and Workgroup Videohub families. Videohub control panels, such as Videohub Master Control Pro and Videohub Smart Control Pro, are clients of a Videohub and are not routers. Do not add them as routing devices.

• Blackmagic Videohub 10x10 12G

• Blackmagic Videohub 20x20 12G

• Blackmagic Videohub 80x80 12G

• Blackmagic Videohub Mini 4x2 12G

• Blackmagic Videohub Mini 6x2 12G

• Blackmagic Videohub Mini 8x4 12G

• Smart Videohub CleanSwitch 12x12

• Universal Videohub 288

Known Limitations

• The protocol is text-based and does not support encryption or authentication; network-level security measures are recommended.

• hi builds Sources and Destinations from the input and output label blocks that the device sends.

• Several clients can connect to a Videohub at once. A route or label that another control surface changes appears in hi when the device reports the change.

• The Videohub protocol numbers inputs and outputs from 0. hi numbers Sources and Destinations from 1, so Videohub input 0 appears as Source 1 in hi.

• hi sends a batch of Crosspoint changes in groups of eight routes, with a 100 ms pause between groups.

• A Videohub output that is locked on the front panel accepts no new route until it is unlocked. hi does not read the lock state, so a route from hi to a locked output does not take effect.

What's Not Supported

• Label editing, output locking, and monitoring, serial, or frame control.

• Engineering-level configuration (level naming, port labels, redundancy setup) - use the vendor's native router-control tool.

• Firmware updates - use the vendor's native update utility.

• Hardware diagnostics and SFP-level health - surfaced by the device's own management plane, not this integration.

• Reading the device model, input and output counts, and routing levels. hi builds Sources and Destinations from the label blocks that the device sends.

Trademarks