> For the complete documentation index, see [llms.txt](https://docs.behringer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.behringer.com/mixers/2.-sources-channels-buses-and-outputs.md). # 2. Sources, Channels, Buses and Outputs With its enhanced routing flexibility, WING introduces a new method for labeling signal Sources using names, icons, and colors, alongside their physical parameters such as gain, phantom power, and phase inversion. WING Sources can be routed to one or more channels for signal processing, or routed to Main Buses, Buses, and Matrices. They can also be sent directly from any input to any output directly, when no processing is needed, such as in recording setups or when sharing audio with another console for independent mixes. Additionally, Sources enable remote control of preamps and allow for the sharing of names and customization settings via AES50. WING Sources include the following information: * Identifying characteristics like name, color, icon, and tags * Physical characteristics such as gain, mute, phase inversion and phantom power * Mono, stereo or mid/side configuration. All 48 channels on the console can process mono, stereo and mid/side signals, without the need to link two adjacent channels. See [Section 5.4](/mixers/5.-main-screens/5.4-routing.md): ROUTING for more information. ## 2.1 Sources Inputs can be analog signals via combo jacks or 1/4-inch TRS connectors on the rear panel, or digital signals via StageConnect, USB, AES50, internal modules, and expansion cards. WING has the following external SOURCE GROUPS: * Local In (8 on-board preamps on WING, 24 on WING COMPACT and WING RACK) * Aux In (8 TRS connectors for line-level inputs, WING only) * AES/EBU (2 channels) * AES50 A, B and C (48 channels each) * StageConnect (up to 32 channels) * USB Audio (48 channels) * External expansion card (WING-LIVE by default) (64 channels) * Internal module (64 channels) * USB Player (4 channels) ## 2.2 40 Input Channels and 8 Aux Channels WING channels offer powerful and flexible processing. All Input Channels (1-40) support mono, stereo, or mid/side signals without requiring adjacent channel linking. Aux Channels (A1-A8) support mono and stereo signals. As a result, all signal processors and sends within each channel are stereo capable. When a mid/side Source is assigned to a channel, it is decoded into standard stereo before processing. Each Input or Aux channel can accommodate both a MAIN and an ALT (alternative) Source. Channels automatically adopt the Source’s customization properties and mono/stereo configuration (see [Section 5.1](/mixers/5.-main-screens/5.1-home.md) → ICON / COLOR for details). ## 2.3 4 Stereo Main Buses WING features 4 stereo Main buses (M1-M4). Each channel has 4 independent Main sends that can be configured as Pre or Post fader (Fig. 1). A typical application for multiple Main buses is using a single WING console to mix both the PA system in a venue and a live stream of the same event. One Main bus can handle the PA mix, while another handles the stream mix. ![Figure 1: MAIN sends on a channel](https://1894100560-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwpjLdmPnyWfhPygRNPrD%2Fuploads%2F08oXQlhDJ1ieOWWyspey%2F1.jpg?alt=media\&token=6bf3d24d-d7ae-4133-ad9a-201d135b7e8b) *Figure 1: MAIN sends on a channel* ## 2.4 16 Stereo Buses WING provides 16 stereo buses (B1-B16) that can operate in three modes: * TAP: The signal sent to the bus is derived from the channel’s TAP point, which is freely customizable on Input Channels and fixed at the pre-fader position on other channel types (see [Section 6.1](/mixers/6.-channel-processing/6.1-input-channels.md) Input Channels for details). This mode is commonly used for monitoring mixes by setting the TAP point to a pre-fader position. * POST: The signal sent to the bus is derived post-fader, typically used for adding effects like reverb or delay. * GROUP: The send level to the bus is deactivated and controlled solely by the channel fader. This mode is often used for group processing, such as compressing all drum channels together. All channels can be sent in different modes to the same bus. For example, one channel can be sent in Group mode to Bus 1, while another is sent in TAP mode to Bus 1. This configuration can be set in the Bus Sends section of each channel (Fig. 2) or on the Bus Feed Configuration screen (Fig. 27). For more information, see [Section 5.1](/mixers/5.-main-screens/5.1-home.md) → Home, Bus Feed Configuration. ![Figure 2: Channel Send settings](https://1894100560-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwpjLdmPnyWfhPygRNPrD%2Fuploads%2FdlfGZnXaBVS5c7OJSRjb%2F2.jpg?alt=media\&token=81bdc059-1ec7-42a8-824b-1518e0ee3379) *Figure 2: Channel Send settings* ## 2.5 8 Matrix Buses The 8 Matrix buses (MX1 - MX8) offer processing and routing options like the 16 Buses. However, Matrices can only be routed to digital or analog outputs, not to other Buses or Matrices. Additionally, Matrices can serve as Sources for any channel. ## 2.6 Internal Sources ### Bus / Main / Matrix All Buses, Mains and Matrices can be selected as the Source for all Input and Aux channels. ### 2 Oscillators There are two independent mono test tone generators that can be configured for sine wave, pink noise or white noise output. They can be used as a Source for any channel or output. ### 24 User Signals User Signals are copies of any of the 40 input channels, 8 Aux channels, 16 Buses, 8 Matrices or 4 Main buses. The signal can be derived pre-fader (from the TAP point on Input channels) or post-fader. Each User Signal is mono. Users can choose whether the User Signal is a copy of the left (L) or right (R) channel, or a sum of both (L+R). If the original channel or bus is mono, this setting has no effect. Two adjacent User Signals can be configured as a single stereo or mid/side Source, allowing for further processing and routing as needed. ### 32 User Patches User Patches are copies of external Sources, either digital or analog, such as Local In, AES50, USB Audio, etc. User Patches allow you to create stereo or mid/side combinations of raw input signals that don’t belong to the same Source Group or which are not adjacent. Possible applications are: * Combining two signals from different Source Groups into a stereo or mid/side configuration * Combining non-adjacent signals into a stereo or mid/side configuration * Creating a stereo or mid/side Source that starts with an even channel * Apply different gain or polarity to each channel of a stereo or mid/side configuration * Apply phantom power to only one channel of a stereo or mid/side configuration Each User Patch is mono. Two adjacent User Patches can be configured as a single stereo or mid/side Source and then processed or routed as desired. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.behringer.com/mixers/2.-sources-channels-buses-and-outputs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.