> 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/sc-i-o/signal-routing.md). # Signal Routing StageConnect carries up to 32 channels in total, in any combination of upstream and downstream channels. ## SC16-I When the Ultranet OUT 1 switch is set to OFF, the SC16-I uses 16 upstream channels to send its 16 analog inputs to the StageConnect Host. 16 channels remain available on the bus. When the Ultranet OUT 1 switch is set to ON, the SC16-I uses the same 16 upstream channels, and the Host allocates 16 downstream channels that the SC16-I converts to Ultranet OUT 1. All 32 channels of the bus are then in use, so no additional device can add inputs to the bus in this mode. You can daisy-chain additional receive-only Clients from the StageConnect HOST port to access the 16 downstream channels sent from the Host. Ultranet OUT 2 does not consume StageConnect bus channels. ## SC16-O The StageConnect Host allocates 16 downstream channels that the SC16-O converts to both the 16 analog outputs and the StageConnect 16 CH OUTPUT port. 16 channels remain available on the bus. You can daisy-chain additional Clients from the StageConnect HOST port to use the 16 remaining channels or to access the 16 downstream channels sent from the Host. When an Ultranet source is connected to the ULTRANET 16 CH INPUT port, the SC16-O becomes the StageConnect Host. The StageConnect chain starts with the SC16-O instead of a console. The 16 channels from Ultranet are sent to the analog outputs and allocated to 16 downstream channels sent through the StageConnect HOST port. The Ultranet port labeled "StageConnect 16 CH OUTPUT" then carries Ultranet Thru. ## SC88 The StageConnect Host allocates 8 downstream channels, which the SC88 outputs through the XLR line outputs on the front panel. The 8 analog inputs from the Triad preamplifiers are sent through 8 upstream channels to the Host. In this mode, the SC88 uses 8 downstream and 8 upstream channels. This leaves 16 channels available on the StageConnect bus. When the Ultranet OUT 1 switch is moved from the 8 CH to the 16 CH position, the SC88 receives 16 downstream channels from the Host and routes them to Ultranet OUT 1. Channels 1–8 are the same downstream channels that feed the XLR line outputs; only channels 9–16 add further channels to the bus. The routing of the analog inputs and outputs remains the same. In this mode, the SC88 uses 16 downstream and 8 upstream channels. 8 channels remain available on the StageConnect bus. Ultranet OUT 2 is always on and carries the analog inputs on channels 1–8 and the analog outputs on channels 9–16. It does not consume StageConnect bus channels. ## MIDI Routing The MIDI IN and MIDI OUT ports create a MIDI tunnel between two StageConnect interfaces: whatever is connected to the MIDI IN of one interface is reproduced at the MIDI OUT of the interface at the other end of the bus. Currently, the Behringer SC-U is the only unit capable of forwarding MIDI data from the StageConnect bus to another protocol — in this case, to a computer through USB. The Behringer WING series does not read MIDI data received over StageConnect. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.behringer.com/mixers/sc-i-o/signal-routing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.