> 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/setup-examples.md).

# Setup Examples

FLOW 4V and FLOW 4VIO offer great flexibility through StageConnect and USB connectivity. Below are a few setup examples to illustrate their versatility and inspire some creativity.

## FLOW 4V and FLOW 4VIO

The simplest setup pairs the FLOW 4V with 4VIO. Even within this basic configuration, there are many placement options, for example, stacking both units together either on their own or mounted beneath a camera, or placing one unit under the camera and the other on a mic stand closer to the sound source.

In all configurations, FLOW 4V and 4VIO are connected through StageConnect: the FLOW 4V acts as the StageConnect Host and the FLOW 4VIO as the StageConnect Client. Apply external power to the FLOW 4V, which then powers the FLOW 4VIO over StageConnect. See [Power and Mounting](/power-and-mounting.md#power) for the power requirements.

<figure><img src="https://3855008865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEeobaGGdWhQsZjKhg5XU%2Fuploads%2FimAceOemaYrkT5E7pwml%2Fflow-4v-and-flow-4vio.png?alt=media&amp;token=81ca307c-19e2-4d89-a6a4-4c3ea2b44d51" alt=""><figcaption></figcaption></figure>

## FLOW 4V/4VIO as USB Audio Interface

FLOW 4V and FLOW 4VIO can each be used as a standalone USB audio interface. They can also be combined: in that setup the FLOW 4V connects to the computer over USB, the FLOW 4VIO connects to the FLOW 4V over StageConnect, and the FLOW 4V determines the USB channel count. The FLOW 4VIO's four preamplifiers occupy USB recording channels 5–8.

See [Signal Routing](/signal-routing.md) for the USB channel counts and channel assignments of each configuration.

<figure><img src="https://3855008865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEeobaGGdWhQsZjKhg5XU%2Fuploads%2F2C0oD538xA89GXmmfcWn%2Fflow-4v-usb-audio-interface.png?alt=media&amp;token=33b968c0-4d7b-4a30-851c-5cb45d92652d" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3855008865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEeobaGGdWhQsZjKhg5XU%2Fuploads%2FsJMTnPv1yEVOMWqP5G4w%2Fflow-4v-4vio-usb-audio-interface.png?alt=media&amp;token=0ee40c1d-e870-40ef-9861-ff4c184ce967" alt=""><figcaption></figcaption></figure>

## FLOW 4V/4VIO as Stagebox

FLOW 4V and FLOW 4VIO can function as I/O boxes for both live and studio applications. Up to two FLOW 4V/4VIO units can be daisy chained.

Both units can also be combined freely with a WING console. Each unit adds 4 analog inputs, 4 analog outputs, 4 USB inputs and 4 USB outputs, using 8 upstream and 8 downstream StageConnect channels per unit.

<figure><img src="https://3855008865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEeobaGGdWhQsZjKhg5XU%2Fuploads%2FK2Kq7IJQDWp1TqlF31bL%2Fflow-4v-4vio-stagebox.png?alt=media&amp;token=97e10d9a-cb2c-47fa-8b3a-1ce5745a364a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3855008865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEeobaGGdWhQsZjKhg5XU%2Fuploads%2F07jwH6q5AcXAX2Ae3cp5%2Fflow-4vio-stagebox.png?alt=media&amp;token=f1dbf1d7-ce46-407d-911b-cf3abfbd3e35" alt=""><figcaption></figcaption></figure>


---

# 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/setup-examples.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.