Multi Device Signal Flow

Multi Device Signal Flow is a Pro-tier feature that enables visualization and analysis of signal routing across multiple interconnected Behringer WING digital mixing consoles, stageboxes, hubs, and personal monitor stations.

Overview

Complex productions often involve multiple WING consoles working together - FOH, monitors, broadcast, recording, etc. This tool allows you to:

• Visualize the entire system topology as an interactive diagram
• Trace signal paths across mixer boundaries
• Filter by channel tags to focus on specific signal types
• Inspect cross-mixer AES50 and StageConnect routing at a glance

The mixer layout, connections, and per-mixer snapshots are all configured in the Project Editor (Define mode). The Multi Device Flow view (Inspect mode) is read-only - it derives its diagram from the project topology you have already authored.

Getting Started

Requirements

• Pro subscription required
• Pro Project - select "Pro" when creating a new project

Creating a Pro Project

1. Navigate to Projects page
2. Click New Project
3. Enter a project name and description
4. Select Pro Project in the Project Type section
5. Click Create Project

Accessing Multi Device Flow

1. Open a Pro project from the Projects page
2. The project opens in Define mode (Project Editor)
3. Author your mixer topology and assign snapshots there (see Projects)
4. Click Inspect in the Define ⇄ Inspect toggle (top of the page) to switch to the read-only Multi Device Flow diagram

You can also open Multi Device Flow directly via Tools menu > Multi Device Flow, then select a project from the project picker.

Define ⇄ Inspect Toggle

A persistent toggle at the top of the page lets you switch between the two complementary views of a project:

Changes made in Define mode are immediately reflected when you switch to Inspect mode.

Demo Mode

A read-only demo is available without logging in. It loads a built-in example topology so you can explore the diagram features before creating an account. The demo is view-only and cannot be edited.

Using the Diagram

Mixer Nodes

Each mixer in your project topology is represented as a node showing:

• Mixer name and color border
• Port indicators (A, B, C, SC) on edges
• Connection status for each port
• Expand/collapse button

Expanded Mixer View

Click the expand button on a mixer node to see its routing summary:

The summary provides a quick overview without needing to open the full Signal Flow visualization.

Devices in the Diagram

Besides mixers, the diagram also renders every stagebox, P24Hub, and personal monitor station (P16-M / P24) from your project topology as its own node, cabled with transport-coloured cables — the same devices you laid out in the Project Editor.

Connections

Cables are colour-coded by transport, matching the Project Editor:

Interacting with the Diagram

Live Read (Pro)

Live read lets you connect to one or more WING consoles and pull their current routing into the diagram on demand — without uploading a snapshot file first.

Connecting to Your Consoles

Open a mixer's Read live control; when no consoles are connected yet it offers Connect a console…, which opens the connection dialog. Select every console you want to use — each entry shows the console name and IP address, and you can check multiple boxes to connect to several mixers at once. Connections are maintained for the session and shared across all mixers.

Note: The Connect dialog uses the same OSC/native transport configuration as the single-mixer Signal Flow view. Consoles must be reachable on your network.

Reading a Mixer Live

Each mixer node in the Inspect diagram has a Read live control. When you open it:

1. Choose which connected console to read from (one console at a time per mixer).
2. Click Read — the diagram replaces that mixer's routing with the live data from the desk.
3. A LIVE badge appears on the mixer node to indicate it is showing live routing.

The read is a point-in-time snapshot of the desk's routing at the moment you click Read. The diagram does not continuously update; re-read manually whenever the desk changes.

Tip: You can read multiple mixers live at the same time, each from a different connected console.

Mixers Without a Stored Snapshot

You do not need a stored snapshot assigned to a mixer in the Project Editor to use live read. If no snapshot is assigned, the mixer shows no routing data by default — but you can still read it live. The LIVE badge appears and the mixer's routing is populated from the desk for the duration of the session.

Reverting to the Stored Snapshot

To go back to the saved snapshot data, click Use snapshot on the mixer node. The LIVE badge disappears and the stored snapshot routing is restored.

If no snapshot is assigned, the mixer returns to its empty (unassigned) state.

Live Data Is Not Saved

Live reads are session-only and are never written back to the project. Reloading the page clears all live data; you must re-read each mixer if needed. To make a live routing permanent, use the standard snapshot upload flow in the Project Editor (Define mode).

Warning: Do not rely on live reads as a substitute for saving snapshots before a show. Live data is lost when you reload or navigate away.

Signal Tracing

Enabling Trace Mode

1. Click the Trace button in the toolbar
2. The diagram enters trace mode (indicator appears)
3. Click any input/output on a mixer to start tracing

Trace Results

A trace follows the signal through every device it physically passes — including stageboxes, P24Hubs, and monitor stations, not just mixers. For example, tracing an output can follow a signal from a mixer, through a P24Hub, to the specific fader on a P24 personal monitor station behind it.

When tracing, the diagram highlights:

• Gold border on nodes in the signal path
• Gold lines on connections carrying the signal
• Statistics panel showing nodes, mixers, and connections traversed

Note: The mixers crossed count in the statistics panel counts only real consoles — stageboxes, P24Hubs, and monitor stations on the path are not counted as mixers, even though they appear as nodes in the diagram.

Note: Talkback is a separate signal from the audio path and is never highlighted when tracing an audio route — for example, tracing signal through a P24Hub does not also light up its Talkback output.

Trace Directions

When starting a trace, you can choose the direction:

Trace Results Panel

The trace results panel shows:

• Nodes traversed: Total signal points in the path
• Mixers involved: Which mixers the signal passes through
• Cross-connections: Number of AES50/StageConnect links used
• Path summary: Visual breadcrumb of the signal chain

Clearing Trace

Click Clear Trace button or toggle trace mode off.

Filter In/Out (Physical Groups)

Separately from tag filtering, a Filter In/Out dialog lets you hide entire physical I/O groups (LCL, AES50-A, USB, etc.) from the diagram, aggregated across all mixers in the project. Input and output groups are filtered independently — hiding an input group (e.g. "AES50-A" inputs) does not also hide the same-named output group, since inputs and outputs are tracked separately even when they share a group name.

Tag-Based Filtering

Filter the signal flow by channel tags to focus on specific signal types.

Available Tags

Tags are extracted from your snapshot files based on channel names:

Using the Filter Panel

1. Click Filter in the toolbar to open the filter panel
2. Click tags to cycle through states:
   • Green (Include): Only show channels with this tag
   • Red (Exclude): Hide channels with this tag
   • Gray (None): No filtering for this tag
3. Toggle Show Untagged to include/exclude channels without tags
4. Toggle Highlight Only to dim (instead of hide) non-matching channels

Filter Indicators

When filters are active:

• Mixer nodes show a badge with filtered/total channel count
• Mixers with no matching channels appear dimmed
• The toolbar shows an active filter indicator

Common Filter Scenarios

"Show only monitor paths":

• Include: IEM, Wedge
• Result: Only monitor sends and their source signals visible

"Hide click and talkback":

• Exclude: Click, Talkback
• Result: Focus on actual program audio

"Find all drum routing":

• Include: Drums
• Result: See complete drum signal chain across all mixers

Toolbar Controls

Each mixer node also has its own Read live / Use snapshot controls (visible when expanded or on hover).

Tips and Best Practices

Naming Conventions

Use clear, consistent names for your mixers in the Project Editor:

• FOH (Front of House)
• MON (Monitors)
• BC (Broadcast)
• REC (Recording)

Color Coding

Assign distinct colors to different mixer roles in the Project Editor:

• Blue for main/FOH
• Green for monitors
• Orange for broadcast
• Purple for recording

Organizing Layout

Position mixers in the Project Editor to reflect physical or logical relationships:

• Group related consoles (e.g., stage left/right monitor mixers)
• Use vertical/horizontal alignment for clarity
• The Inspect view preserves the layout you defined

Using Trace with Filters

Combine trace mode with tag filtering for powerful analysis:

1. Filter first: Set up tag filters to show only relevant channel types
2. Enable trace: The trace picker shows only filtered channels
3. Start trace: Signal path highlights across the filtered view

Example workflow - "Trace all IEM paths":

1. Include the "IEM" tag in the filter
2. Enable trace mode
3. Click any IEM output to see its complete source chain
4. The path shows which inputs feed each performer's ears

Limitations

Current Limitations

• Expanded mixer view: Shows routing summary instead of full embedded signal flow diagram
• Cross-mixer tracing: Requires snapshots assigned for all mixers in path (done in Project Editor)
• Tag detection: Limited to pattern matching in channel names (explicit tags coming soon)

Coming Soon

• Full embedded signal flow diagrams in expanded mixer view
• Advanced loop detection with severity levels
• Signal latency calculations across paths
• Export topology as image/PDF

Troubleshooting

Live Read Not Working

• Open the Connect dialog and confirm the console shows as connected (green indicator)
• Ensure the console is reachable on the same network (ping the IP; check firewall rules)
• If the read times out, try again — OSC reads are a single point-in-time request and can be retried immediately
• Verify that no other application is exclusively occupying the console's OSC/TCP port

Live Data Disappeared After Reload

Live reads are session-only and are always lost on page reload. Re-read each mixer from the Connect dialog after returning to the page.

Mixer Not Showing Routing Data

• Verify a snapshot is assigned to the mixer in the Project Editor (Define mode), or use Read live to pull data directly from a connected console
• Check that the snapshot file is valid
• Switch back to Inspect mode after making changes in Define mode

Connections Not Visible

• Check that connections between mixers are defined in the Project Editor
• Verify that the connection type and ports match your physical setup

Trace Not Working

• Ensure snapshots are assigned for all mixers in the potential path (via Project Editor)
• Wait for "Graph ready" indicator (visible in debug mode)
• Clear existing trace and try again

Tags Not Appearing

• Tags are auto-detected from channel names in your snapshots
• Use standard naming conventions (see Source Tags Reference)
• Channels without recognizable patterns appear as "untagged"
• Toggle "Show Untagged" in the filter panel to include/exclude them

Filter Shows No Channels

• Check that at least one mixer has channels matching your filter
• Verify snapshots are assigned in the Project Editor (tags come from snapshot data)
• Try clearing filters and starting with a single include tag

Related Documentation

• Signal Flow - Single-mixer signal flow visualization
• Projects - Project management, layout authoring, and snapshot assignment
• Source Tags Reference - Channel naming conventions for tag detection
• Reference - Complete feature reference