Routing Generator
The Routing Generator creates professional PDF documentation from your WING mixer snapshots. Get detailed tables of inputs, outputs, channels, and routing - plus optional routing matrices and device labels.
Overview
The Routing Generator produces:
- Full Routing PDF: Complete documentation of your mixer configuration
- Device Labels PDF: Printable labels for your stageboxes and mixer
Both output formats are available from the same tool, with different configuration options.
Uploading Snapshot Files
Supported File Formats
Wing Tools supports Behringer Wing snapshot files with these extensions:
.snap- Standard snapshot formatsnapshot.9- Firmware version 9 snapshotssnapshot.10- Firmware version 10 snapshots (most common)snapshot.11- Firmware version 11 snapshots
If you upload an unsupported or untested snapshot version, Wing Tools will:
- Still process the file
- Display a warning banner in the PDF
- Mark the output as potentially incomplete
Upload Methods
Drag and Drop:
- Locate your
.snapfile on your computer - Click and drag the file to the Wing Tools upload area
- Release to upload
- Progress bar shows upload status
- PDF opens automatically when ready
Browse and Select:
- Click the upload area or "Browse" button
- Navigate to your
.snapfile - Select the file and click "Open"
- Upload proceeds automatically
Browse Library (logged-in users):
- Click Browse Library to access stored files
- Navigate to your file in My Files
- Select and confirm
- File loads without re-uploading
Commercial Use Declaration
Wing Tools asks you to declare whether you're using the tool commercially:
Non-commercial use includes:
- Personal practice and learning
- Rehearsals for unpaid performances
- Educational purposes
- Hobby projects
- Testing and evaluation
Commercial use includes:
- Paid live performances
- Studio recording sessions
- Corporate events
- Theater productions
- Any work you're being compensated for
Upload Errors and Solutions
| Error Message | Cause | Solution |
|---|---|---|
| "Only .snap files allowed" | Wrong file type | Verify file has .snap extension |
| "File size exceeds limit" | File too large | Check your tier's file size limit |
| "Terms must be accepted" | Terms checkbox unchecked | Check the terms acceptance box |
| "Rate limit exceeded" | Too many uploads | Wait until tomorrow or upgrade tier |
| "Failed to process file" | Corrupted or invalid snapshot | Try re-exporting from Wing console |
Understanding the Generated PDF
PDF Structure Overview
Every Wing Tools PDF contains these sections in order:
- Metadata Page (Portrait)
- INPUTS Section (Mixed portrait/landscape)
- OUTPUTS Section (Mixed portrait/landscape)
- CHANNELS Section (Portrait)
- ROUTING TABLE (Portrait, if enabled)
- Routing Matrix (Basic+, if enabled)
Section 1: Metadata Page
The metadata page provides essential snapshot information at a glance.
Mixer Information:
Mixer: WING-PP-14091119
Model: wing-rack
Created: 2025-06-18 14:43:28
Firmware: snapshot.10
Summary Statistics:
Total Inputs: 152
Total Outputs: 134
Total Channels: 48
Active Routes: 156
This helps you quickly verify:
- Which mixer the snapshot came from
- When it was created (useful for version control)
- The firmware version (important for compatibility)
- Configuration complexity at a glance
Section 2: INPUTS (Sources)
The INPUTS section documents every physical input source, organized by input group.
Input Groups and Processing Order
Inputs appear in this canonical order:
- LCL - Local physical inputs on the mixer itself (8-24 channels depending on model)
- AES50 A/B/C - AES50 digital audio ports for stage boxes (48 channels each)
- AUX - Auxiliary inputs (typically 8 channels)
- SC - StageConnect protocol inputs (if applicable)
- USB - USB audio interface (32 channels)
- CRD - Expansion card inputs
- MOD - Modular expansion inputs
- USR - User-defined virtual inputs
- OSC - Internal test oscillators
- AES - AES3 (AES/EBU) digital inputs
- PLAY - Playback channels
Input Table Columns
| Column | Description | Example |
|---|---|---|
| Group | Physical input group identifier | AES50 A, LCL, USB |
| Number | Channel number within group | 1-48 |
| Source Name | User-assigned name at console | "Kick Drum" |
| Mode | Blank for mono, "ST" for stereo | ST |
| Gain (dB) | Microphone preamp gain | 12.5 |
| +48V | Phantom power status | ON |
| Used By | Channels using this input | CH 1, BUS 3 |
Understanding the "Used By" Column
The "Used By" column shows which mixer channels, buses, and outputs reference each input source.
Free Tier Behavior:
Used By: CH 1, CH ...
Truncated to 10 characters with "..." indicating more content exists.
Premium Tier Behavior:
Used By: CH 1, CH 15, BUS 3, LCL.5, AES50 A.17
Complete list of all references, making it easy to trace signal flow.
Complete Input Usage Column (Basic+)
Basic tier and above unlocks the full "Used By" column in the INPUTS section.
Why This Matters:
The complete usage information helps you:
- Identify dependencies: See all channels that would be affected if you change this input
- Trace signal flow: Follow a signal from input through all its destinations
- Find unused inputs: Empty "Used By" cells indicate available inputs
- Verify direct patches: See physical outputs directly patched to inputs
Information Shown:
- Channel assignments: CH 1, CH 15, A3
- Bus/matrix references: BUS 3, MTX 2
- Direct output patches: LCL.5, AES50 A.17
- FX returns: FX 1 RETURN
Oscillator Inputs (OSC Group)
Test oscillator inputs use different columns:
| Group | Number | Source Name | Mode | Waveform | Level |
|---|---|---|---|---|---|
| OSC | 1 | PINK | - | PINK | -10.0 dB |
| OSC | 2 | SINE | - | SINE | -10.0 dB |
Waveform types: SINE, PINK, WHITE
Layout Intelligence
Wing Tools automatically adapts page layout:
- Small groups (8 or fewer inputs): Portrait mode, single column
- Large groups (more than 8 inputs): Landscape mode, 2-column layout with even split
This ensures readability even for snapshots with 48-channel stage boxes.
Section 3: OUTPUTS (Physical)
The OUTPUTS section documents every physical hardware output and what it's connected to.
Output Table Columns
| Column | Description | Example |
|---|---|---|
| Group | Physical output group | LCL, AES50 A, USB |
| Number | Channel number within group | 1-48 |
| Type | Routing type | Mixer, Direct |
| Connected To | Mixer output or input source | BUS.1L, AES-A.5 |
| Source Name | Actual signal name | "IEM Drum (L)" |
Output Types Explained
Mixer Outputs: Signals that pass through the Wing's mixing engine (buses, matrices, mains).
Example:
Group: AES50 A
Number: 9
Type: Mixer
Connected To: BUS.1L
Source Name: IEM Drum (L)
This shows AES50 A output 9 is carrying the left channel of Bus 1, which the user named "IEM Drum".
Direct Patches: Signals that bypass the mixer entirely, going straight from input to output.
Example:
Group: AES50 B
Number: 3
Type: Direct
Connected To: LCL.1
Source Name: Kick
This shows AES50 B output 3 is directly patched to Local Input 1 (named "Kick"), with no processing.
Understanding Stereo Outputs
The Wing uses an internal channel-based numbering system for stereo outputs:
- Odd numbers (1, 3, 5...) = Left channel
- Even numbers (2, 4, 6...) = Right channel
Example for Bus 1:
AES50 A.9 -> BUS.1L (IEM Drum L) - Internal BUS1
AES50 A.10 -> BUS.1R (IEM Drum R) - Internal BUS2
Bus 1 uses two consecutive output channels to carry stereo audio.
Unpatched Outputs
Wing Tools shows ALL outputs, including unpatched ones:
Group: LCL
Number: 5
Type: (blank)
Connected To: OFF.1
Source Name: (blank)
This comprehensive view helps you:
- Identify available outputs
- Document unused connections
- Take notes about future routing plans
Section 4: CHANNELS
The CHANNELS section lists all mixer channels (1-40) and aux channels (A1-A8) with their input assignments.
Channel Table Columns
| Column | Description | Example |
|---|---|---|
| Ch # | Channel number | 1, 15, A3 |
| Channel Name | User-assigned channel name | "Kick Drum" |
| Active Src | Currently selected input | AES-A.1 |
| Active Src Name | Name of active input | "Kick" |
| Active Src Type | MAIN or ALT | MAIN |
| Other Src | Non-active alternate input | USB.1 |
| Other Src Name | Name of alternate input | "Kick USB" |
Asterisk (*) in Channel Name
If you see a channel name prefixed with an asterisk (e.g., *Kick), this indicates that the Wing console's "Link Customization to Source" feature is enabled for that channel. When enabled, the channel name is automatically copied from the input source name.
The asterisk serves as a visual indicator that:
- The displayed name came from the source, not from a direct channel name assignment
- The original channel name (if any) has been replaced
Stereo Source Display Mode (Premium)
For stereo channels, Premium users can choose how the left and right sources are displayed in the Channel List. This option is available in the PDF Configuration panel.
Display Modes:
| Mode | Description | Example |
|---|---|---|
| Compact (default) | Single row with "+1" suffix | Active Src: AES50-A.1+1 |
| Expanded Rows | Two separate rows for L/R | CH16-L: AES50-A.1, CH16-R: AES50-A.2 |
| Extra Column | Additional columns for R source | L Src: AES50-A.1, R Src: AES50-A.2 |
When to use each mode:
- Compact: Best for most situations, keeps the table concise
- Expanded Rows: Useful when you need to see both sources clearly and don't mind the extra rows
- Extra Column: Good when you want all stereo info on one row but need to see both source numbers
Note: The "Mode" column shows "ST" for stereo channels regardless of display mode.
Main vs. Alternate Sources
Each channel can have two input sources:
- Main Source: The primary input assignment
- Alternate Source: A secondary input for quick switching
The "Active Src Type" column shows which is currently selected.
Use cases for alternate sources:
- AB microphone comparison: Main = Shure SM58, Alt = Sennheiser e945
- Virtual soundcheck: Main = Stage box input, Alt = USB playback
- Backup routing: Main = wireless mic, Alt = wired backup
- Scene-specific routing: Different inputs for different songs
Aux Channels (A1-A8)
Aux channels appear after regular channels (1-40) and are labeled with an "A" prefix:
Ch #: A1
Channel Name: 2TR
Active Src: USB.1
Active Src Name: USB Playback L
Active Src Type: MAIN
Aux channels are typically used for:
- Stereo playback sources
- Effects returns
- Guest input channels
- Additional stereo inputs
Section 5: ROUTING TABLE (Active Routes)
The routing table shows all active signal routing from channels to outputs.
When enabled, the table shows:
| Ch # | Channel Name | Output Type | Out # | Output Name | Pre/Post |
|---|---|---|---|---|---|
| 1 | Kick | Main | 1 | Main L/R | Post |
| 1 | Kick | Bus | 1 | IEM Drum | Pre |
| 2 | Snare | Main | 1 | Main L/R | Post |
Columns:
- Ch #: Source channel
- Channel Name: User name for channel
- Output Type: Main, Bus, or Matrix
- Out #: Output number
- Output Name: User name for output
- Pre/Post: Pre-fader or post-fader send
This section answers:
- Where is each channel being sent?
- Which sends are pre-fader (monitor mixes)?
- Which sends are post-fader (effects, broadcast feeds)?
Source Name Replacement Hack (Basic+)
The "Hacks" section provides advanced configuration options. The source name replacement hack replaces input source names with channel names.
What It Does
When enabled, this hack:
- Finds the lowest-numbered channel using each input
- Replaces the input's source name with that channel's name
- Leaves inputs with no channel references unnamed
Why Use This?
Many engineers name their channels but not their physical inputs. This hack ensures your INPUTS section shows meaningful names by borrowing from channel names.
Without hack:
| Group | Number | Source Name | Used By |
|---|---|---|---|
| AES50 A | 1 | (unnamed) | CH 1 |
| AES50 A | 2 | (unnamed) | CH 2 |
With hack enabled:
| Group | Number | Source Name | Used By |
|---|---|---|---|
| AES50 A | 1 | Kick | CH 1 |
| AES50 A | 2 | Snare | CH 2 |
How to Enable
- Navigate to the configuration panel
- Expand the Hacks section
- Check "Replace Source Names with lowest referencing Channel Name"
- Generate your PDF
When to Use This Hack
Ideal for:
- Console operators who name channels but not inputs
- Snapshots from virtual soundcheck setups
- Situations where channel names are the "source of truth"
Not recommended for:
- Snapshots with meaningful input names already
- Multi-console systems where inputs serve different channels
- Situations requiring independent input naming
Routing Matrix (Basic+)
The routing matrix provides comprehensive visual routing grids showing all signal connections.
The Four Matrices
Wing Tools generates four distinct routing matrices:
Matrix 1: Input to Channel
Shows which physical inputs feed which mixer channels.
Rows (Sources): Physical input groups (LCL, AES-A, AES-B, AES-C, AUX, USB, etc.) Columns (Destinations): CH1-40, AUX1-8
What it shows:
- Which stage box channels go to which console channels
- Input source assignments at a glance
- Alternate source connections (if configured)
Matrix 2: Sources to Mix Outputs
The complete mixing matrix showing all internal routing.
Rows (Sources):
- Channels (CH1-40)
- Buses (BUS1-16)
- Mains (MAIN1-4)
Columns (Destinations):
- Buses (BUS1-16)
- Matrices (MTX1-8)
- Mains (MAIN1-4)
What it shows:
- Channel-to-bus sends (monitor mixes, effects sends)
- Channel-to-matrix sends (zone mixes, delays)
- Channel-to-main sends (FOH mix)
- Bus-to-bus sends (subgroup routing)
- Bus-to-matrix sends (processed zone feeds)
- Main-to-matrix sends (FOH to zones)
This is the most comprehensive matrix, showing your complete mix architecture.
Matrix 3: Mixer to Physical Outputs
Shows how mixer outputs are patched to physical hardware outputs.
Rows (Sources): BUS1-16, MTX1-8, MAIN1-4 Columns (Destinations): Physical output groups (LCL, AES50-A, AES50-B, AES50-C, etc.)
What it shows:
- Which mixer buses go to which physical outputs
- Monitor mix output assignments
- Matrix output routing
- Main output patching
Matrix 4: Direct Connections
Shows direct patches that bypass the mixer.
Rows (Sources): Physical inputs Columns (Destinations): Physical outputs
What it shows:
- Direct input-to-output connections
- Splitter configurations
- Pass-through routing
Reading Matrix Cells
Matrices use visual indicators to show connection status and properties.
Circle Mode (Default)
Circle size indicates send level:
- Larger circle = higher level
- Smaller circle = lower level
- Empty outline = inactive route
Circle color indicates send type:
- Green: Post-fader send
- Blue: Pre-fader send
- Orange: Alternate source connection
Gray Mode
Cells are filled with gray gradients:
- Darker gray = higher level
- Lighter gray = lower level
- White = inactive route
Text Mode
Cells display the actual dB value for precise level documentation.
Row and Column Omission
To keep matrices compact, Wing Tools intelligently omits unused rows and columns.
Omission rules:
- Rows/columns with no active connections are candidates for omission
- Two or more consecutive inactive rows/columns are collapsed
- Single inactive rows/columns are kept for context
- Omitted sections are marked with dotted gray lines
Enabling Routing Matrix
- Upload your snapshot
- Check "Include routing matrix" in configuration options
- Generate PDF
- Matrices appear after the standard sections
Use Cases for Routing Matrices
Pre-show verification:
- Check all monitor sends are configured
- Verify effects bus routing
- Ensure backup routing is in place
System documentation:
- Archive mix architecture for future shows
- Document installed system routing
- Create reference material for training
Troubleshooting:
- Quickly identify missing sends
- Verify signal flow visually
- Compare against known-good configurations
Device Labels
Device Labels generates printable pages for stageboxes that can be physically attached to your equipment. Each label shows XLR connector layouts with channel names and routing information.
Why Use Device Labels?
Unlike the Full Routing PDF which documents your entire mixer configuration, Device Labels are designed to be:
- Printed and attached directly to your stageboxes
- Quick-reference showing only what's relevant to each device
- Physically accurate matching the XLR layout of real devices
- Self-contained with all routing info for that device in one place
Supported Devices
AES50 Stageboxes
| Device | I/O | Form Factor | Output Switch |
|---|---|---|---|
| SD8 / DL8 | 8 in, 8 out | Desktop | 1-8, 9-16, or 17-24 |
| S16 / DL16 | 16 in, 8 out | 2U rack | 1-8, 9-16, or 17-24 |
| S32 / DL32 | 32 in, 16 out | 3U rack | Fixed 1-16 |
StageConnect Devices (Basic+)
| Device | I/O | Description |
|---|---|---|
| DN4888 | 8 in, 8 out | Configurable I/O (8x8 or 16x8 mode) |
| DN4816-I | Up to 16 in | Input-focused (16x0, 16x16, or 0x16) |
| DN4816-O | Up to 16 out | Output-focused (slave or ultranet mode) |
Free vs Paid Device Labels
| Feature | Free Tier | Basic+ Tier |
|---|---|---|
| Devices per PDF | 1 | Unlimited |
| AES50-A support | Yes | Yes |
| AES50-B/C support | No | Yes |
| StageConnect devices | No | Yes |
| WING mixer local I/O | No | Yes |
Configuring Devices
- Select "Device Labels" as the output format
- Click "Configure Devices" to open the configuration modal
- Add your stageboxes with their connection details:
- Name: A descriptive name (e.g., "Stage Left")
- Device Type: SD8, S16, S32, DL8, DL16, DL32, or StageConnect
- AES50 Bus: Which mixer port (A, B, or C)
- Position: Daisy-chain position (1, 2, or 3)
- Output Switch: Which return channels the device outputs
- Click Close to save your configuration
- Click Generate
Your configuration is saved for reuse (in browser for anonymous users, in your project for logged-in users).
Understanding Daisy-Chain Positions
When multiple stageboxes connect on the same AES50 port:
| Position | 16-ch Device | 32-ch Device |
|---|---|---|
| 1 (nearest mixer) | Inputs 1-16 | Inputs 1-32 |
| 2 | Inputs 17-32 | Inputs 33-48 |
| 3 | Inputs 33-48 | N/A |
The PDF shows both local and mixer channel numbers.
PDF Layout Options
Layout Mode:
- Fill Mode (default): Maximizes use of page space with efficient grid layout
- Physical Mode: Arranges XLR connectors to match the real device's physical layout
Compact Mode: When enabled, smaller devices (like SD8) can be combined on a single page.
Reading the Generated Labels
Each device label page includes:
Header Section:
Stage Left
Behringer S16 | Mixer Port: AES50-A | Output Switch: 1-8
AES-A > FOH | AES-B > Stage Right
XLR Connector Grid:
-
Inputs (female XLR, dark inner circle):
- Local channel number
- Source name from snapshot
- Mixer channel assignment (e.g., "CH 1")
- "N/C" for unused channels
-
Outputs (male XLR, light gray inner circle):
- Local output number
- Destination name from snapshot
- Mixer output assignment (e.g., "BUS 1")
Footer:
- Wing Tools logo
- Snapshot filename
- Generation timestamp
Best Practices for Device Labels
- Name your devices clearly: Use location-based names like "Stage Left", "Drum Riser", "FOH Rack"
- Configure output switch correctly: Match the physical switch position on your device
- Verify daisy-chain order: Ensure position numbers match your actual cable connections
- Print on appropriate paper: Labels are designed for A4 landscape; consider laminating for durability
Snapshot Health Check
After every generation — whether you produce a routing PDF, device labels, or an Excel export — Wing Tools automatically checks your snapshot for potential issues and shows a compact Snapshot health check summary panel.
The panel displays counts of findings by severity:
- Critical: Issues that will almost certainly cause problems at your show
- Error: Likely mistakes worth investigating before doors
- Warning: Configuration choices that may or may not be intentional
- Info: Informational notices with no immediate action required
If no issues are found, the panel confirms your snapshot is clean.
The health check shows counts only. Full issue details and AI-powered insights are available in the Snapshot Linter (Pro). If you already have Snapshot Linter access, an Open full report button in the panel takes you directly to the detailed analysis for the same snapshot. If you are on a lower tier, the panel includes a link to unlock the full report.
Next Steps
- Signal Flow: Visualize your routing interactively
- Routing Diff: Compare two snapshots to see what changed
- Projects: Save device configurations for reuse
Questions? Check the Reference section for troubleshooting tips.