> 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/flow-4v-4vio/introduction-to-flow-4v-and-flow-4vio.md).
# Introduction to FLOW 4V and FLOW 4VIO
### Field Recorder, StageConnect I/O Extension, USB Audio Interface
**FLOW 4V** is a 10-track field recorder equipped with four onboard dual-stage preamps with extreme dynamic range. It also functions as a standalone 32-bit float USB audio interface and an I/O box for other StageConnect devices. Record and mix line-level signals using the stereo AUX input. FLOW 4V can be expanded with four additional remote inputs through StageConnect using a FLOW 4VIO.
**FLOW 4VIO** is an I/O box featuring four onboard dual-stage preamps and two 1/4" TRS outputs. Similar to FLOW 4V, FLOW 4VIO can also serve as a standalone USB audio interface and I/O box for other StageConnect devices.
### Dual-Stage Preamps
The dual-stage preamp and A/D conversion deliver a 142 dB dynamic range for microphone or line-level sources.
Highly optimized input circuitry ensures an optimal signal-to-noise ratio and prevents audio clipping without requiring manual gain adjustments. Input levels can be trimmed digitally for added flexibility.
---
# 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/flow-4v-4vio/introduction-to-flow-4v-and-flow-4vio.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.