Behringer WING Pre-Show Checklist

The worst time to discover a routing mistake is during the first song. This checklist walks the WING from input to output so you catch the small configuration errors — a muted bus, phantom power off the wrong channel, an unrouted talkback — while you still have time to fix them. Work through it after your patch is built and before you open the doors.

Tip: Most of these checks can be run automatically against your snapshot with the Snapshot Linter (Pro). Use this list to understand what to check; use the linter to check it in seconds.

1. Inputs and Sources

• Every active channel has a source assigned (no channel feeding from nothing).
• Sources point at the right physical input — AES50-A, AES50-B, StageConnect, Local, or USB as intended.
• Phantom power (+48V) is on for condensers and active DIs, and off for dynamics and line sources.
• Gain / trim is set sensibly per source (no channels left at default that should be driven).
• Channel names and colors match the patch list, so the desk reads cleanly under pressure.

Warning: Phantom power on a dynamic mic input usually does no harm, but +48V on a line-level or unbalanced source can. Verify per channel, not globally.

2. Stereo Links and Pairs

• Stereo sources (keys, playback, stereo DIs) are linked as pairs where intended.
• Linked pairs share consistent processing and pan hard L/R as expected.
• No channel is accidentally linked to its neighbor.

3. Bus and Monitor Routing

• Each monitor / aux bus that should be in use is named and active.
• Channels are sent to the correct monitor buses at workable levels.
• No bus that feeds a wedge or IEM is left muted at the master.
• Bus pre/post fader settings match the use (monitors usually pre, effects usually post).

4. Effects and Returns

• Effects sends route to the intended FX buses.
• FX returns come back into the mix (and aren't muted or unrouted).
• No feedback loop — an output feeding back into its own input chain.

5. DCAs and Mute Groups

• DCA assignments are correct and channels aren't double-assigned in a way that fights you.
• Mute groups contain the right channels (and nothing surprising).
• No critical channel is sitting in a mute group that's currently engaged.

6. Talkback and Comms

• Talkback is configured and routed to the right destinations (monitors, comms).
• A TALK source / channel exists if your workflow expects one.
• Talkback isn't accidentally routed into the main mix.

7. Mains and Matrices

• Main L/R (and mono/sub) outputs are routed to the correct physical outputs.
• Matrix feeds (fills, broadcast, recording) are assigned and at sane levels.
• Output patching matches the system tech's expectations — confirm against the stage plan.

8. Recording and Playback

• USB / card recording is armed and pointed at the right sources if you're tracking the show.
• Virtual soundcheck playback routing is set (and switched back to live before doors).

Automate It With the Snapshot Linter

Walking this list by hand is reliable but slow, and it's easy to skip a step when you're rushed. The Snapshot Linter reads your snapshot and flags the exact problems above — muted buses that receive sends, talkback with no destination, phantom power inconsistencies, unrouted channels — with severity levels so you know what's critical versus cosmetic.

Pair it with Routing Diff to confirm that what changed since last night's rehearsal is only what you meant to change.

A Repeatable Routine

1. Build and finalize the patch on the console.
2. Export the snapshot (.snap).
3. Run the Snapshot Linter and clear any critical findings.
4. Document the routing and share the PDF with your deputy and the venue.
5. Open doors with confidence.

Next Steps

• Snapshot Linter: Automate every check on this page.
• Documenting WING Routing: Turn the verified snapshot into shareable docs.
• Routing Diff: Confirm exactly what changed since the last show.

---

Questions? Check the Reference section for troubleshooting tips.