A signal entering the router.
Camera 1 → Source 1
The input label can identify the connected camera, player, graphics system, or another source.
DeviceJockey Interfaces
Blackmagic Videohub Interface
Build a routing panel for switching sources, identifying ports, and displaying the active signal path.
Video routing
Connect every destination to one selected source.
A Videohub is a video router. Sources enter the router through its inputs. Each destination output can be assigned to one of those sources. DeviceJockey keeps the reported input labels, output labels, and routing assignments available so a panel can show the current router state.
An output receiving a selected source.
Source 1 → Destination 4
The output label can identify the monitor, recorder, transmitter, or other destination.
Source and destination are different port types.
A routing command needs both values. It selects which source appears at a particular destination.
Connection
Add the router to the active scene.
1
Prepare the network
Connect DeviceJockey and the Videohub to networks that can reach each other.
2
Add Videohub
Add a Videohub interface to the scene containing your routing panels.
3
Enter host and port
Enter the router’s current IP address and its control port. The default in DeviceJockey is 9990.
4
Enable interfaces
Switch on interface connections and confirm that the Videohub reports as connected.
Host
The IP address or network name used to reach the Videohub.
Port
The TCP control port. DeviceJockey creates a new Videohub interface with port 9990.
Offline Mode preserves a setup without connecting.
Use it when the router is temporarily unavailable. Turn it off before testing commands and feedback.
Open the official Videohub Ethernet Protocol manual →Commands
Route signals and maintain useful port names.
Assign a selected source port to a selected destination port. This is the main routing command.
Change the label of an input source on the Videohub.
Change the label of an output destination on the Videohub.
Port numbers in DeviceJockey start with 1.
The app converts the displayed source and destination numbers to the Videohub protocol’s internal numbering when it sends a command.
Events and feedback
Make the panel follow the router.
Videohub events evaluate the router state held by the interface. The exact choices depend on the selected item and the property being configured.
Show the name reported for a selected source input.
Show the destination name, or the name of the source currently routed to that destination where the item supports it.
Switch an item light on when a selected destination is connected to the configured source, and off when it is not.
Switch on a supported item or trigger a buzzer tap when a selected source and destination become connected.
Feedback confirms the actual route.
Use a routing light together with the Set destination command so the button reflects the state reported by the Videohub.
Panel pattern
Build a source selector for one destination.
1
Choose the destination
Decide which router output this group of controls should manage.
2
Add one item per source
Give every button the same destination and a different source in VH Set destination.
3
Add routing feedback
Configure each button’s light for the same destination and its own source.
4
Add dynamic labels
Use source or destination label events when names should follow changes made on the router.
Swaps can make a routing panel reusable.
Source, destination, and label values support replacement through the active scene’s Swaps.
Troubleshooting
If the Videohub does not connect or route.
Check Offline Mode.
The interface does not establish its normal live connection while it is configured for offline use.
Verify the host.
Compare the configured address with the Videohub’s current network address.
Verify port 9990.
Use the router’s configured control port. DeviceJockey defaults to 9990.
Check network access.
Confirm that Wi-Fi, VLAN, firewall, and routing rules allow the iPhone or iPad to reach the Videohub.
Check source and destination order.
The first value identifies the destination to change. The second identifies the source to route to it.
Check the port range.
Use source and destination numbers that exist on the connected Videohub model.
Test feedback separately.
If routing works but the panel does not update, verify that the event uses the same interface, destination, and source as the command.