Blackmagic Design Videohub Integration Configuration
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.
Configuration Overview
The Videohub integration has one configuration. hi builds the matrix from the label blocks that the Videohub sends, so the address and the Port must match. Set Input Count and Output Count to the router size when you create the Node, because they cannot be changed later. Ports above the size that the Videohub reports stay in hi as unused Ports.
|
Configuration |
What hi Sees |
Use When |
|---|---|---|
|
Videohub Video Routing |
One video matrix with the input and output labels and the current video output routing. |
hi must route a Videohub or a Videohub Server. |
Before You Begin
-
Use Node admin and open Inventory > Nodes. See Manage Nodes.
-
Confirm the license and minimum hi version in Required Configuration.
-
Use Blackmagic Videohub Setup, or the front panel where the model has one, to read the network address of the Videohub.
-
Confirm the network access in Network Requirements.
-
The Videohub protocol has no authentication. Anyone who can reach the Port can route. Keep the Videohub on a routing-control network.
Configure Videohub Video Routing
Device Configuration
-
Connect the Videohub to the network and assign it a static IP address. On a Videohub 12G model with an LCD, press Menu, select Network, and confirm each field with the spin knob and Set. On a Smart Videohub model, including CleanSwitch 12x12, use Menu, the rotary knob, and Take to confirm the network fields. For Videohub Mini and Universal Videohub models, use Blackmagic Videohub Setup over USB.
-
For a Videohub Server or a Universal Videohub frame, confirm that the Videohub Server is running and reachable on the management network.
-
Confirm that the Videohub control interface is enabled and that the hi server can reach the Videohub on TCP Port
9990, the Videohub Ethernet Protocol Port. hi opens the connection, and the Videohub makes no connection to hi.
hi Configuration
-
Add the Videohub integration (manufacturer Blackmagic Design) in Inventory.
-
Enter the Videohub address. The template default Port is
9990. -
In the Port Settings group, enter the router size in Input Count and Output Count. The template defaults are
16and16. -
Create the Node. hi builds the Sources and Destinations from the input and output label blocks that the Videohub sends when hi connects.
-
After the Node is created, the Operations group shows Refresh Labels and Refresh Crosspoints. Use them to read the labels or the routing again without a restart.
Settings Summary
|
Setting |
Device Side |
hi Side |
|---|---|---|
|
Address |
Static IP address of the Videohub or the Videohub Server |
Videohub address |
|
Port |
TCP Port |
Port
|
|
Matrix size |
Inputs and outputs of the Videohub |
Input Count and Output Count |
Common Checks
|
Symptom |
Check |
|---|---|
|
The Node does not connect. |
Confirm the address and Port |
|
Labels are missing or out of date. |
Select Refresh Labels in the Operations group. |
|
A Crosspoint in hi differs from the Videohub. |
Select Refresh Crosspoints in the Operations group. |
|
A route from hi lands on the wrong input or output. |
Videohub numbers inputs and outputs from |
Verify the Configuration
Wait for the Node to report a connected state and for the input and output labels to appear in hi. If the Node does not connect, verify the address, the Port, the Videohub control service, and the network route between hi and the Videohub. Compare the input labels, the output labels, and several Crosspoints with the Videohub control software. Route a noncritical output from hi and confirm the change in the control software. Then change a route from the control software and confirm that hi shows it without a restart, because the Videohub reports changes to every connected client.