> 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/introduction-to-sc-i-o-serie.md).

# Introduction to SC I/O Serie

## SC16-I

The SC16-I is a 16-channel analog input interface with support for StageConnect and Ultranet. It provides 16 combination XLR/TRS input jacks: inputs 1–8 accept microphone or line-level signals through Triad microphone preamplifiers, and inputs 9–16 accept line-level signals.

The SC16-I adds 16 analog inputs to a StageConnect Host and supplies the analog input signals for P16 monitoring systems through Ultranet OUT 2.

## SC16-O

The SC16-O is a 16-channel analog output interface with support for StageConnect and Ultranet. It provides 16 line-level outputs on XLR-M connectors.

The SC16-O can also convert Ultranet sources to analog audio outputs.

## SC88

The SC88 is an 8-input / 8-output analog interface with support for StageConnect and Ultranet. It provides 8 combination XLR/TRS input jacks accepting microphone or line-level signals through Triad microphone preamplifiers, and 8 line-level outputs on XLR-M connectors.


---

# 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/sc-i-o/introduction-to-sc-i-o-serie.md?ask=<question>&goal=<user_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.