Nevion VideoIPath

A Nevion VideoIPath connection doesn't route through Levels the way most other router integrations do. Instead, Buttons discovers everything VideoIPath itself is already configured with: a set of independent resource types, each with its own sources, destinations, and disconnect option. This page explains how those types map to what you see in Routing, and how to keep only the ones you'll use.

VideoIPath groups its routable resources into types. Buttons has friendly names for five common ones (Junction, Vertex, Group, Tally Meta, and GPIO) and shows any other type your VideoIPath configuration defines using its own name.

Each type routes completely independently: a route within Junction has no effect on Vertex, Group, or any other type, and their sources and destinations aren't shared. This is different from a Level-based router, where the same source and destination numbering repeats across every Level; here, each type is its own separate set of sources and destinations.

Buttons shows every resource VideoIPath exposes, which is often far more than you'll route. Keep only the ones you actually use, and hide the rest in Routing → Ports Config with Visibility → Hide. See Hide ports you don't need.

A common pattern is to route with either Group resources or individual ports (such as Junction or Vertex), not both at the same time. Since the types route independently, showing both gives operators two ways to route the same signal, and the panels show more than they need.

Every resource type includes a built-in "None" source, labeled with the type's own name (for example, a "Junction" None source for the Junction type). This comes directly from VideoIPath's own Disconnect option: there's nothing to configure. Selecting it and taking a route clears that destination's active source, and the destination's active-source display then shows ---.

This module doesn't expose destination locking. No lock or unlock controls appear for its destinations in Buttons.