NDI® Router

The NDI® Router turns Laika into a software crosspoint matrix for your NDI® network. It creates virtual NDI® outputs that redirect receivers to real sources — without any video data passing through Laika itself.

Routes and virtual outputs persist across restarts. Your entire routing configuration is saved automatically — outputs, names, and all crosspoint assignments are restored exactly as you left them every time Laika starts. Build your routing matrix once and it is always ready.

Why the Router Matters

Traditional video routers are expensive hardware. NDI® routing in software gives you the same crosspoint switching capability at zero additional bandwidth cost. When Laika routes a source to a virtual output, it tells receivers “go connect to that source directly” — the video data flows peer-to-peer between sender and receiver, never touching Laika’s CPU or network interface.

This means you can:

• Build a full routing matrix without hardware routers
• Switch sources across your entire NDI® network from one control point
• Route the same source to dozens of destinations with no bandwidth overhead on the routing machine
• Integrate routing control with your existing Laika multiviewer workflow

Opening the Router

Menu → View → Show Router

The Router opens as a matrix view within Laika. Rows represent NDI® sources discovered on the network. Columns represent virtual outputs you create.

Creating Virtual Outputs

1. Click the + Add Output button
2. Enter a name for the virtual output (e.g., “Program Monitor”, “Record Feed”, “Studio B Return”)
3. The new output appears as a column in the routing matrix
4. The output is immediately visible as an NDI® source on the network

Other NDI® receivers (vMix, OBS, hardware decoders, other Laika instances) can connect to these virtual outputs like any other NDI® source. When you change what a virtual output is routed to, all connected receivers switch seamlessly.

Routing Sources

Click any cell in the matrix where a source row intersects an output column to create a route. That virtual output now redirects any connected receivers to the selected source.

Color coding in the matrix:

• Cyan highlights the source row you’re hovering over
• Green marks cells where a route is actively assigned

To change a route, click a different cell in the same output column. To clear a route, click the currently active (green) cell again.

Connection Count Badges

Each virtual output column header shows a connection count badge indicating how many receivers are currently connected to that output. This gives you immediate visibility into which outputs are in use and how many endpoints depend on each route.

A badge showing “0” means the output exists on the network but nothing is receiving it — useful for pre-building routes before a show goes live.

Renaming Outputs

Double-click any virtual output column header to rename it inline. The output is immediately re-advertised on the network with the new name. Receivers that are already connected will need to reconnect using the new name.

Deleting Outputs

Each virtual output column header contains a delete button (trash icon). Clicking it removes that output from the matrix and stops advertising it on the network. Any receivers connected to the output will lose their signal.

Include Routes as Sources

The matrix has a toggle to control whether virtual router outputs appear as selectable sources in the viewer grid and source picker.

When enabled: Router outputs are visible alongside real NDI® sources. You can assign a virtual output as a source in a viewer tile, which lets you monitor what receivers of that route would see.

When disabled (Default): Router outputs are hidden from the viewer source list, keeping the source picker clean.

Web API Control

The Router can be controlled programmatically via Laika’s Web API, enabling integration with:

• Stream Deck buttons for one-touch route changes
• Custom control panels and automation systems
• External routing control surfaces
• Scheduled route changes via scripting

See the Web Control API page for endpoint documentation.

Use Cases

Route cameras to different monitoring feeds: Create virtual outputs named “Director Mon”, “Engineering Mon”, and “Talent Mon”. Route different camera combinations to each, giving every station the feeds they need without dedicated hardware routers.

Create virtual program/preview outputs: Set up outputs named “PGM” and “PVW” that follow your switcher’s program and preview selections. Downstream systems connect to these virtual outputs and automatically receive whichever source is currently routed — no manual switching required at the receiver end.

Facility-wide source distribution: In a multi-studio facility, create virtual outputs that aggregate sources from different studios. Route “Studio A - CAM 1” to a shared output that any control room can subscribe to, then re-route it to “Studio B - CAM 1” when the production moves.

Backup and failover routing: Pre-configure backup routes. If a primary source goes down, click one cell in the matrix to redirect all connected receivers to the backup source simultaneously.

---