Free for personal and non-profit use. Commercial use requires a subscription.
Documentation
Back to App

Audio Engineer Guide

This guide provides best practices, workflow tips, and troubleshooting strategies specifically for audio engineers using Wing Tools with Behringer Wing consoles.

Naming Conventions and Best Practices

Why Naming Matters

Proper naming in your Wing console:

  • Makes Wing Tools PDFs immediately readable
  • Speeds up troubleshooting during live shows
  • Improves handover documentation for other engineers
  • Enables meaningful signal flow visualization
  • Helps with snapshot comparison and archiving

Input Naming Strategy

Physical Inputs

Recommendation: Name inputs at the console with descriptive, consistent names.

Good input names:

Kick, Snare Top, Snare Btm, HH, OH L, OH R
Vox Lead, Vox BV1, Vox BV2
Bass DI, Bass Mic
Gtr L, Gtr R
Keys L, Keys R

Characteristics of good names:

  • Short but descriptive (fits on scribble strip)
  • Consistent abbreviations (Vox, Gtr, Kbd)
  • Numbered for multiple similar sources (BV1, BV2, BV3)
  • Instrument position for drums (OH = Overhead, HH = Hi-Hat)

Avoid:

Input 1, Input 2, Channel 1          (not descriptive)
Michael's Vocal                      (too long)

Channel Naming

Option 1: Same as input names

If you name inputs descriptively, copy those names to channels:

Input AES-A.1: Kick → Channel 1: Kick
Input AES-A.2: Snare Top → Channel 2: Snare Top

Option 2: Different channel names

Some engineers prefer different naming schemes:

Input AES-A.1: SM57-SNARE → Channel 2: Snare
Input AES-A.5: DPA-OH-L → Channel 5: OH L

This approach documents both the microphone and its function.

Option 3: Use Source Name Replacement Hack (Premium)

If you only name channels, enable the Source Name Replacement hack to automatically populate input names from channel names in the PDF. See Routing Generator for details.

Bus and Output Naming

Bus Names

Name buses by their function, not their number:

Monitor mixes:

BUS 1: IEM Drums
BUS 2: IEM Bass
BUS 3: IEM Gtr
BUS 4: Monitor FOH L
BUS 5: Monitor FOH R

Effects sends:

BUS 6: Reverb
BUS 7: Delay
BUS 8: Chorus

Subgroups:

BUS 9: Drums
BUS 10: Vocals
BUS 11: Band

Matrix Names

Name matrices by their destination or zone:

MTX 1: Zone A Front
MTX 2: Zone A Rear
MTX 3: Zone B Front
MTX 4: Delay Tower
MTX 5: Video Feed
MTX 6: Recording Out

Main Outputs

If your Wing uses multiple main outputs:

MAIN 1: FOH L/R
MAIN 2: Broadcast

Channel Tagging

In addition to naming, the Wing console supports tagging channels. Tags are independent of names and can be used to explicitly categorize channels for Wing Tools.

When to use tags:

  • When channel names don't follow standard naming patterns
  • When using non-English names that aren't auto-detected
  • When you want to ensure specific channels are always correctly categorized

Example tags:

CH 15 "Band Return" + tag: COM        (Communication - explicitly tagged)
BUS 1 "Pierre IEM" + tag: IEM         (In-ear monitor - explicitly tagged)
CH 10 "Pastor Mike" + tag: VOX        (Vocal - wouldn't be detected by name)

See Source Tags Reference for the complete list of recognized tags.

Scene Naming

Name your Wing scenes descriptively:

Format: [Date] [Show/Venue] [Revision]

Examples:

2025-12-15 Jazz Club FOH v3
2025-12-15 Jazz Club Monitors v2
2025 Festival Template
2025-12-20 Corporate Gala Main

This makes it easy to:

  • Identify snapshots in Wing Tools file list
  • Compare different versions of the same show
  • Archive configurations by date

Exporting Snapshots from Wing Console

Quick Export Workflow

From the console:

  1. Save your current scene:

    • Press SCENES button
    • Navigate to target scene slot
    • Press SAVE to store current configuration

  2. Connect USB drive:

    • Insert FAT32-formatted USB drive to console USB port
    • Wait for recognition (LED indicator)

  3. Export scene:

    • Press UTILITY button
    • Navigate to Files → Export Scene
    • Select scene to export
    • Choose USB drive as destination
    • Confirm export

  4. Verify file:

    • File appears on USB with .snap extension
    • Typical format: SceneName.snapshot.10

From Wing Edit app (computer):

  1. Connect Wing to computer via USB or network
  2. Open Wing Edit application
  3. Connect to your Wing console
  4. Top Right → Save As...
  5. Choose location and filename
  6. File saves as .snap file

Recommendation: Keep your Wing firmware updated. Newer formats include:

  • More accurate routing data
  • Additional metadata
  • Better compression
  • Enhanced compatibility

If using an older firmware version, Wing Tools will still parse the snapshot but may display a warning banner in the PDF.

Export Best Practices

For show archival:

  1. Export at start of soundcheck (baseline)
  2. Export after soundcheck (with changes)
  3. Export after show (final state)
  4. Name files clearly: Show-Soundcheck.snap, Show-Final.snap

For system documentation:

  1. Export with all channels assigned
  2. Export with all buses configured
  3. Include descriptive names everywhere
  4. Document any custom routing in scene notes

For troubleshooting:

  1. Export "known good" configuration
  2. Export current problematic configuration
  3. Use Routing Diff to compare

Interpreting Routing Tables

Reading Input Assignments

The INPUTS section tells you what's plugged into the mixer.

Example:

Group: AES50 A
Number: 15
Source Name: Bass DI
Mode: -
Gain: 0.0 dB
+48V: -
Used By: CH 10, LCL.5

What this tells you:

  1. Physical location: AES50 Port A, channel 15 (stage box position)
  2. What it is: Bass direct input
  3. Gain setting: 0 dB (no preamp gain, DI provides line level)
  4. Phantom power: Off (DI doesn't need it)
  5. Routing: Feeds mixer channel 10 AND is directly patched to Local output 5

Why the direct patch? Likely sending the bass signal to both FOH console (CH 10) and monitor console or recording interface (LCL.5) simultaneously.

Understanding Direct Patches

Direct patches bypass the mixer entirely, sending input straight to output.

Common use cases:

Digital snake split:

Input: AES50-A.1-24
Output: AES50-C.1-24 (direct)
Purpose: Send all stage box inputs to monitor console

Multitrack recording feed:

Input: LCL.1 (Kick)
Output: USB.1 (direct)
Purpose: Dry signal to DAW while also processing in mixer

FOH/Monitor split:

Input: AES50-B.1-16
Output: LCL.1-8 + USB.1-8 (direct)
Purpose: Distribute inputs to multiple destinations

Identifying direct patches in Wing Tools PDF:

Look for Type: Direct in OUTPUTS section:

Group: AES50-C
Number: 5
Type: Direct
Connected To: AES50-A.5
Source Name: Snare Top

This shows AES50-C output 5 carries a direct copy of AES50-A input 5.

Pre-Fader vs. Post-Fader Sends

Understanding pre/post fader sends is critical for monitor mixes and effects routing.

Pre-fader sends:

  • Signal is taken before the channel fader
  • Send level independent of fader position
  • Typical use: Monitor mixes, IEM feeds

Post-fader sends:

  • Signal is taken after the channel fader
  • Send level follows fader position
  • Typical use: Effects sends, broadcast feeds, recording

In Wing Tools PDF (when enabled):

Ch #: 1
Channel Name: Kick
Output Type: Bus
Out #: 1
Output Name: IEM Drums
Pre/Post: Pre

This tells you the kick channel is sent to Bus 1 (IEM Drums) pre-fader, so the monitor mix level won't change when you adjust the kick fader for FOH.

Workflow Tips and Tricks

Pre-Show Documentation Workflow

1 week before show:

  1. Create baseline snapshot on Wing
  2. Export to USB
  3. Upload to Wing Tools
  4. Generate PDF
  5. Share with production team

Soundcheck day:

  1. Load baseline snapshot
  2. Make adjustments during soundcheck
  3. Save as new scene (e.g., "Show-Soundcheck")
  4. Export snapshot
  5. Upload to Wing Tools
  6. Use Routing Diff to compare with baseline

After show:

  1. Save final snapshot
  2. Export with descriptive name (e.g., "Show-Final-2025-12-15")
  3. Upload to Wing Tools
  4. Archive PDF with show notes

Using Wing Tools for System Integration

For permanent installations:

  1. Document as-built configuration:

    • Export snapshot after system commissioning
    • Upload to Wing Tools
    • Generate PDF for client deliverables
    • Include in system documentation binder

  2. Create baseline template:

    • Name all inputs by rack position
    • Name all outputs by amplifier/zone
    • Document direct patches clearly
    • Save as template snapshot

  3. Training documentation:

    • Use Signal Flow visualization to train new operators
    • Print routing matrix as quick reference chart
    • Label console scribble strips to match PDF names

Troubleshooting with Wing Tools

Problem: No signal on channel

Troubleshooting steps:

  1. Check INPUTS section:

    • Is phantom power enabled if needed?
    • Is gain set appropriately?
    • Is the input being used by any channel? (Used By column)

  2. Check CHANNELS section:

    • Is the correct source selected (MAIN vs ALT)?
    • Is the source assignment correct?

  3. Check OUTPUTS section:

    • Is the output patched correctly?
    • Is it going to the right bus/main?

Problem: Wrong signal on output

  1. Find the output in OUTPUTS section
  2. Check "Connected To" column - what mixer output is it connected to?
  3. Cross-reference with CHANNELS section to find source
  4. Verify physical patching matches PDF

Problem: Monitor mix missing channels

  1. Generate PDF with routing matrix enabled (Premium)
  2. Check Matrix 2 (Sources → Mix Outputs)
  3. Look for the bus column (e.g., BUS 1 for first monitor mix)
  4. Scan down column - empty cells show missing sends
  5. Add sends on console for missing channels

Common Scenarios and Solutions

Scenario 1: Festival Handover

Situation: You're handing over console to another engineer mid-festival.

Using Wing Tools:

  1. Export current snapshot
  2. Upload to Wing Tools
  3. Generate PDF with:
    • Signal flow visualization (Premium)
    • Routing matrix (Premium)
    • Complete input usage (Premium)
  4. Print or email PDF to incoming engineer
  5. Highlight special routing (direct patches, effects buses, etc.)

What the PDF provides:

  • Complete input list with names and gain settings
  • All channel assignments
  • Monitor bus configuration
  • Main output routing
  • Any special direct patches

Scenario 2: Virtual Soundcheck Setup

Situation: Setting up USB playback for virtual soundcheck.

Step 1: Configure Wing for recording

Channel sources: Set to AES-A inputs (stage box)
Direct patches: AES-A → USB (for recording)

Step 2: Export and document

Upload to Wing Tools
PDF shows all direct patches in OUTPUTS section

Step 3: Configure for playback

Channel sources: Switch to alternate (USB inputs)
Maintain same channel processing

Step 4: Export and compare

Upload new snapshot
Use Routing Diff to see source changes

Scenario 3: Monitor Mix Documentation

Situation: Documenting all monitor mixes for production team.

Using Wing Tools:

  1. Export snapshot with all monitor buses configured
  2. Upload to Wing Tools (Premium)
  3. Enable routing matrix
  4. Check Matrix 2 (Sources → Mix Outputs)
  5. Columns show each bus (monitor mix)
  6. Rows show which channels are sending to each bus
  7. Print matrix for monitor engineer quick reference

PDF shows:

  • Which channels are in each monitor mix
  • Send levels (circle size or dB value)
  • Pre/post fader status (circle color)

Scenario 4: System Commissioning

Situation: Completing permanent installation, need as-built documentation.

Documentation package:

  1. Export final snapshot after commissioning

  2. Upload to Wing Tools

  3. Generate complete PDF with all sections

  4. Include in deliverables:

    • INPUTS section: Documents all rack inputs
    • OUTPUTS section: Documents all zone outputs
    • Signal flow diagram: Visual system overview
    • Routing matrix: Complete routing reference

  5. Provide to client as part of system documentation

Advanced Routing Patterns

Creating Sub-Mixes

Pattern: Using buses as subgroups before sending to mains.

Example - Drum submix:

  1. All drum channels send to BUS 9 (Drums)
  2. BUS 9 sends to MAIN 1/2
  3. Individual drum channels also send to MAIN 1/2

In Wing Tools PDF:

Matrix 2: Sources → Mix Outputs
Rows: CH 1-8 (drums), BUS 9 (drum submix)
Columns: BUS 9, MAIN 1, MAIN 2

Shows:
- CH 1-8 have sends to both BUS 9 and MAIN
- BUS 9 also sends to MAIN

This gives you:

  • Individual drum control at mains
  • Group control via BUS 9 fader
  • Complete flexibility

Matrix Mix Applications

Pattern: Using matrices for zone distribution.

Example - Multi-zone venue:

  1. FOH mix on MAIN 1
  2. MTX 1-4: Different zones with different levels
  3. Each matrix receives MAIN 1 but with individual level control

In Wing Tools PDF:

Matrix 2: Sources → Mix Outputs
Row: MAIN 1
Columns: MTX 1-4

Shows main-to-matrix routing

This provides:

  • Same mix content to all zones
  • Individual zone level control
  • Delay compensation possible per zone

Effects Bus Routing

Pattern: Dedicated effects buses with returns.

Setup:

  1. BUS 6: Reverb send
  2. AUX 1/2: Reverb returns (from external effects or USB)
  3. Channels send to BUS 6 (variable amounts)
  4. AUX 1/2 return to MAIN mix

In Wing Tools PDF:

CHANNELS section shows:
AUX 1: Reverb Return L (Source: USB.1)
AUX 2: Reverb Return R (Source: USB.2)

Matrix 2 shows:
Multiple channels sending to BUS 6
AUX 1/2 sending to MAIN

Next Steps

Questions or tips to share? Contact support@theta-tontechnik.de (Premium/Pro users)

← Account
Reference →