Both integrations treat their router as a single-level device: video, audio, and data move together as one port, so there is no Levels field to configure and no way to break away one signal type while keeping the rest. Buttons can help you confirm the locking and labeling differences between the two before you rely on either in a position.
Before you begin#
- A VideoHub or AJA KUMO connection already added and connected. See Update a connection's module safely if you need to check or change the installed module version.
- Access to Connect → Connection to check configuration, and to Routing to take and verify routes.
Choose a black or silent "None" source (VideoHub only)#
Neither router has a native disconnect command, but VideoHub lets you nominate a physical input as the stand-in for one. Open the connection's configuration and set None / black / silent source to First input or Last input, matching whichever input on the VideoHub is actually wired to black or silence. Leave it Off if no input is dedicated this way.
Once set, that input is flagged as the router's "None" source: when it's the active source for a destination, the destination's active-source display shows --- instead of an input name.
AJA KUMO doesn't offer this setting: its module has no configuration fields at all, so there's no equivalent input designation.
Lock and unlock destinations#
Both modules support destination locking, so lock and unlock controls appear on their destinations wherever locking is enabled in a Router Section: see
Manage locking and
Understand route status for the controls and lock icons themselves. What each router reports back differs:
- VideoHub reports three states (Unlocked, Locked, and Owned), which Buttons shows as no lock, a hard lock, and a user lock respectively. Locking a destination from Buttons always sets the user-lock state; unlocking always clears it.
- AJA KUMO reports only a plain locked/unlocked state, which Buttons always shows as a user lock: it never reports a distinct hard or device lock.
Note
VideoHub's unlock action can't force-clear a lock another controller placed directly on the router (a hard lock). If a destination stays locked after you unlock it from Buttons, clear the lock on the VideoHub itself.
If you get stuck#
What you see | What to try |
|---|
A VideoHub destination stays locked after you select Unlock. | The lock may have been set directly on the VideoHub rather than through Buttons: clear it there. |
You expected a "None" input option on AJA KUMO but don't see one. | AJA KUMO has no configuration fields, including the None-source designation available on VideoHub. |
Where to go next#
