Source Tags Reference

This reference documents the standardized tags that Wing Tools recognizes from your Behringer Wing console's tagging feature. These tags allow you to explicitly classify channels, overriding the automatic name-based detection.

What Are Wing Console Tags?

The Behringer Wing console has a built-in tagging feature separate from channel names. Tags are text labels you can assign to inputs, channels, buses, and mains. They are stored in the snapshot file and are visible in Wing Tools analysis.

Key points:

• Tags are independent of channel names
• Multiple tags can be assigned to a single channel (comma-separated)
• Tags are used for DCA assignments, mute groups, and custom categorization
• Wing Tools recognizes specific tags to classify channels for the Snapshot Linter

How to Apply Tags

On the Wing Console

1. Press HOME to access the channel configuration
2. Select the channel, bus, or main you want to tag
3. Navigate to CONFIG or the tagging screen
4. Enter your tag(s) in the Tags field
5. Separate multiple tags with commas (e.g., DRUMS,#D1,MGRP.1)

In Wing Edit

1. Connect to your Wing console
2. Select the channel strip
3. Find the Tags field in the channel configuration
4. Enter your tags

System Tags

The Wing console uses specific system tags for built-in features:

DCA Group Tags

Mute Group Tags

Talkback Routing Tags

The Wing uses these system tags on buses, matrices, and mains to indicate talkback routing. These are automatically applied based on the Monitoring > Talkback configuration on the console.

Common configurations:

• IEM mixes: TALK A ON - Engineer can speak to musicians without interrupting their mix
• Stage manager wedge: TALK B SOLO - Stage manager has priority communication
• FOH Main: No tags - Protected from accidental talkback to audience
• Broadcast feed: No tags - Clean feed without talkback

How the WING dual talkback works:

1. Talkback A - Primary communication path, typically engineer-to-band
2. Talkback B - Secondary path, typically stage manager or alternate engineer
3. Both can route independently to any combination of buses, matrices, and mains
4. SOLO variants dim other audio so only talkback is heard (useful for critical cues)
5. ON variants add talkback to the existing mix (less intrusive)

Wing Tools Recognition Tags

Wing Tools recognizes the following tags to classify channels for the Snapshot Linter. When present, these tags override automatic name-based detection.

Communication / Talkback

Specializations: COM-FOH, COM-MON, COM-MD, COM-STAGE, COM-BAND, COM-PM

Example: Tag your production intercom return with COM-STAGE to mark it as a communication channel from stage management.

Click / Metronome

Specializations: CLK-L, CLK-R, CLK-CUE

Example: Tag your click track channels with CLK to ensure the linter checks they're routed to all IEM mixes.

In-Ear Monitor Outputs

Specializations: IEM-VOX, IEM-DRUMS, IEM-KEYS, IEM-GTR, IEM-BASS, IEM-MD, IEM-1 through IEM-8

Example: Tag bus outputs feeding P16 personal monitors with IEM so the linter knows these are IEM destinations.

Wedge / Loudspeaker Monitors

Specializations: WDG-DRUM, WDG-SIDE, WDG-SR, WDG-SL, WDG-CTR

Example: Tag your drum fill bus with WDG-DRUM to distinguish it from IEM outputs.

Main PA Outputs

Specializations: PA-L, PA-R, PA-SUB, PA-CTR

PA Fill Speakers

Specializations: FILL-SIDE, FILL-NEAR, FILL-DELAY, FILL-FRONT, FILL-REAR

Example: Tag delay tower outputs with FILL-DELAY to help the linter understand PA distribution.

Effects Returns

Specializations: FX-VOX, FX-VERB, FX-DLY, FX-CHOR

Drum Channels

Specializations: DRM-KIT, DRM-PERC, DRM-ELEC

Vocal Channels

Specializations: VOX-LD, VOX-BG, VOX-CHOIR

Instrument Channels

Specializations: INST-GTR, INST-KEY, INST-BASS, INST-BRASS, INST-STR, INST-WIND

Tag Behavior

Override Rules

• Wing Tools recognition tags override automatic name-based pattern detection
• If a channel has an explicit tag (e.g., COM), its name won't be checked against naming patterns

Case Sensitivity

• Tags are case-insensitive in Wing Tools recognition
• com, COM, and Com are all recognized as communication tags

Hyphenated Specializations

• Base tags and hyphenated specializations both work
• COM and COM-FOH both classify the channel as communication
• The specialization provides additional context for your reference

Multiple Tags

• You can combine Wing Tools tags with system tags
• Example: DRUMS,#D1,MGRP.1 assigns a channel to:
  • Wing Tools drums category
  • DCA group 1
  • Main group 1

Examples

Monitor Engineer Setup

BUS 1: IEM-VOX      (Lead vocal IEM mix)
BUS 2: IEM-KEYS     (Keys player IEM mix)
BUS 3: IEM-DRUMS    (Drummer IEM mix)
BUS 4: WDG-DRUM     (Drum fill wedge)
BUS 5: WDG-SIDE     (Sidefill wedges)

FOH Engineer Setup

CH 15: CLK          (Click track - tagged explicitly)
CH 16: COM-STAGE    (Stage manager talkback)
MAIN 1: PA          (Main L/R)
MTX 1: FILL-DELAY   (Delay tower)
MTX 2: FILL-NEAR    (Near fill speakers)

Hybrid Tagging

CH 1: DRUMS,#D1     (Kick - drums category + DCA 1)
CH 2: DRUMS,#D1     (Snare - drums category + DCA 1)
CH 10: VOX,#D4      (Lead vocal - vocals category + DCA 4)
CH 11: VOX-BG,#D4   (BG vocal 1 - vocals category + DCA 4)

Why Use Explicit Tags?

1. Non-standard naming: When channel names don't follow common patterns (e.g., person names instead of instrument names)
2. Multi-language setups: When your naming uses a language not covered by automatic detection
3. Complex routing: When you need the linter to understand special routing configurations
4. Template standardization: To ensure consistent categorization across different shows

Next Steps

• Snapshot Linter: Learn how channel types affect linting rules
• Audio Engineer Guide: Best practices for naming and tagging
• Reference: Complete feature reference

---

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