> 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/signal-routing.md).

# Signal Routing

FLOW 4V and FLOW 4VIO each feature StageConnect HOST and CLIENT ports, allowing integration in various setups. When used as Clients, both units appear on the StageConnect bus with 8 upstream and 8 downstream channels. The USB channel count, however, depends on how the unit is used:

| Mode                                          | FLOW 4V USB audio | FLOW 4VIO USB audio |
| --------------------------------------------- | ----------------- | ------------------- |
| StageConnect Host or standalone USB interface | 14 in / 2 out     | 12 in / 12 out      |
| StageConnect Client                           | 4 in / 4 out      | 4 in / 4 out        |

USB audio can only be transmitted through the USB 2.0 Type-C port labeled AUDIO.

## Routing as StageConnect Host or Standalone USB Interface

FLOW 4V provides the following USB recording channels:

| USB Recording Channels | Source                  |
| :--------------------: | ----------------------- |
|           1–4          | Local inputs 1–4        |
|           5–8          | StageConnect inputs 1–4 |
|          9–10          | AUX IN, stereo          |
|          11–12         | Talkback, stereo        |
|          13–14         | Main Mix, stereo        |

The FLOW 4V sends the audio over USB; the recording itself is made by the computer. The signals can be sent raw or processed, as set by the switch in Settings, USB RECORDING. This setting is independent of the SD recording setting described in Recording:

* **RAW INPUT:** Input channels and the MAIN MIX are recorded before the processing and level controls, useful for mixing in post-production
* **PROCESSED:** Input channels and the MAIN MIX are recorded after applying levels, channel, delay and auto mixing in FLOW 4V, useful for live streaming applications

Two channels are played back in the opposite direction, from the computer to the FLOW 4V through **USB Output 1–2**, and they can be mixed and monitored on the USB/BT channel.

FLOW 4VIO provides the following USB recording channels:

| USB Recording Channels | Source                  |
| :--------------------: | ----------------------- |
|           1–4          | Local inputs 1–4        |
|          5–12          | StageConnect inputs 1–8 |

FLOW 4VIO provides the following USB playback channels:

| USB Playback Channels | Destination              |
| :-------------------: | ------------------------ |
|          1–2          | PHONES OUTPUT 1          |
|          3–4          | PHONES OUTPUT 2          |
|          5–12         | StageConnect outputs 1–8 |

## Routing as StageConnect Client

On FLOW 4V, the StageConnect downstream channels 1–4 are routed to processing channels 5–8. The MAIN MIX is sent over StageConnect upstream channels 1–2, while the PHONES mix is sent over StageConnect upstream channels 3–4. Upstream and downstream channels 5–8 provide 4 in / 4 out over USB to a computer connected to FLOW 4V.

On FLOW 4VIO, the StageConnect downstream channels 1–2 and 3–4 are routed to the stereo PHONES OUTPUT 1 and 2, respectively. The MIC/LINE 1–4 inputs are sent over StageConnect upstream channels 1–4. Upstream and downstream channels 5–8 provide 4 in / 4 out over USB to a computer connected to FLOW 4VIO.


---

# 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/signal-routing.md?ask=<question>&goal=<endgoal>
```

`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.