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

# Specifications

## FLOW 4V

**General**

Frequency Response: 5 Hz – 22 kHz, ± 1 dB\
Frame Rates: 23.98, 24, 25, 29.97, 29.97df, 30, 50, 60

**Mic Inputs**

Type: 4 × XLR / 1/4" TRS combo jacks, balanced\
Dynamic Range (including A-D): 142 dB (A-weighted)\
Max. Input Level: +18 dBu\
EIN (20 Hz to 20 kHz): −130 dBu (unweighted)\
THD+N at 600 Ω: 0.005% at −40 dBu, 0.002% at +10 dBu\
Crosstalk Rejection: −110 dB\
Impedance: XLR: 10 kΩ bal. / 5 kΩ unbal.\
Gain Range: −63.5 dB to +63.5 dB\
Phantom Power: +48 V, switchable per channel

**Aux In**

Type: 1 × 1/8" TRS jack, stereo\
THD+N at 600 Ω: 0.008% at +6 dBu in\
Max. Input Level: +24 dBu\
Impedance: 10 kΩ

**Headset In/Out**

Type: 1 × 1/8" TRRS jack, stereo + mic in\
Impedance: 40 Ω\
Max. Input Level: +10 dBu\
Max. Output Power: 140 mW into 30 Ω, 75 mW into 300 Ω

**Stereo Out**

Type: 1 × 1/8" TRS jack, stereo\
Impedance: 100 Ω\
Max. Output Level: +10 dBu

**USB Audio Interface**

Connectivity: USB 2.0 Type-C\
Sample Rate: 48 kHz\
Bit Depth: 24 bit, 32 bit float\
Channel Count: 14 in / 2 out (4 in / 4 out when used as StageConnect Client)

**StageConnect**

Audio Channels: 8 upstream, 8 downstream\
Sample Rate: 48 kHz\
Bit Depth: 24 bit\
Remote Power: 12 V DC / 18 W\
Latency: 6 samples\
Cable Length: up to 40 m with 110 Ω DMX cable

**HDMI**

Type: Micro HDMI\
CEC: Camera-controlled Rec Start

**Bluetooth**

Frequency Range: 2402 MHz – 2480 MHz\
Channel Number: 79\
Version: Bluetooth 4.0 Dual Mode\
Compatibility: Supports A2DP 1.2 profile\
Max. Communication Range: 12 m (without interference)\
Max. Output Power: 9.6 dBm\
Gain: 1.84 dBi

**Power Supply**

Connector: USB-C\
Power Supply: 5 V to 15 V, 3 A\
Power Consumption: 10 W

**Physical**

Dimensions (H × W × D): 53 mm × 184 mm × 128 mm\
Weight: 800 g

## FLOW 4VIO

**General**

Frequency Response: 5 Hz – 22 kHz, ± 1 dB

**Mic Inputs**

Type: 4 × XLR / 1/4" TRS combo jacks, balanced\
Dynamic Range (including A-D): 142 dB (A-weighted)\
Max. Input Level: +18 dBu\
EIN (20 Hz to 20 kHz): −130 dBu (unweighted)\
THD+N at 600 Ω: 0.005% at −40 dBu, 0.002% at +10 dBu\
Crosstalk Rejection: −110 dB\
Impedance: XLR: 10 kΩ bal. / 5 kΩ unbal.\
Gain Range: −63.5 dB to +63.5 dB\
Phantom Power: +48 V, switchable per channel

**Phones Outputs**

Type: 2 × 1/4" TRS jack, stereo\
Max. Output Power: 140 mW into 30 Ω\
THD+N at 30 Ω: 0.005%

**USB Audio Interface**

Connectivity: USB 2.0 Type-C\
Sample Rate: 48 kHz\
Bit Depth: 24 bit, 32 bit float\
Channel Count: 12 in / 12 out (4 in / 4 out when used as StageConnect Client)

**StageConnect**

Audio Channels: 8 upstream, 8 downstream\
Sample Rate: 48 kHz\
Bit Depth: 24 bit\
Remote Power: 12 V DC / 18 W\
Latency: 6 samples\
Cable Length: up to 40 m with 110 Ω DMX cable

**Power Supply**

Connector: USB-C\
Power Supply: 5 V to 15 V, 3 A\
Power Consumption: 8 W

**Physical**

Dimensions (H × W × D): 53 mm × 184 mm × 128 mm\
Weight: 750 g


---

# 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/specifications.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.