A Ross Video NK router connection lets Buttons take routes on an NK router. Each source and destination is a single port, routed on the router's SDI Video level.
Before you begin#
- A Ross Video NK router connection already added and connected, running module version 1.0 or 2.0. See Update a connection's module safely if you need to check or change the installed module version.
- The router must have a level called SDI Video. Buttons takes every route on that level.
- Access to Connect → Connection to check configuration, and to Routing to take and verify routes.
Sources, destinations and names#
Buttons reads the router's inputs and outputs from the module. They appear as In 1, Out 1 and so on, with the names set on the router shown next to them.
Routes taken elsewhere aren't shown#
Buttons doesn't read the current routes back from an NK router. The Routing view and route feedbacks only know the routes Buttons itself sent. If someone takes a route from a Ross panel or another controller, Buttons doesn't see it, and the route status in Buttons can be wrong until the route is taken again from Buttons.
Keep this in mind before you rely on route status for an NK router in a position.
Locking and None source#
The Ross Video NK router integration doesn't support destination locking, so no lock or unlock controls appear on its destinations. It also has no None source for clearing a route.
If you get stuck#
What you see | What to try |
|---|
The connection has no sources or destinations in the Routing view. | Check that the router has a level called SDI Video, and that the connection is connected. |
The route status in Buttons doesn't match the router. | Expected when a route was taken outside Buttons. Take the route again from Buttons. |
No lock control appears on a destination. | Expected: this integration doesn't support locking. |
Where to go next#