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

# Get Started

This section outlines the typical workflow for a recording session. Each step points to the section with the full details.

1. **Connect and power the units.** For a FLOW 4V on its own, connect a USB-PD source supplying at least 5 V / 3 A to either USB-C port. To add a FLOW 4VIO, connect the FLOW 4V's StageConnect HOST port to the FLOW 4VIO's CLIENT port and use a source supplying 12 V / 3 A; the FLOW 4V then powers the FLOW 4VIO over StageConnect. See [Power and Mounting](/power-and-mounting.md).
2. **Choose the recording medium.** FLOW 4V can record a multitrack session to an SD card, and can send multitrack audio to a computer over USB, where the recording is made in the computer. The two are independent and can be used at the same time. See [SD Recording and Playback](/sd-recording-and-playback.md) and [Signal Routing](/signal-routing.md).
3. **Choose the tap point.** Decide whether the signals are captured before or after the channel processing and level controls: RAW INPUT or PROCESSED. SD recording and USB recording have separate settings, both in the Settings section. See [Recording](/sd-recording-and-playback.md) and [Signal Routing](/signal-routing.md).
4. **Set the timecode mode.** Select REC RUN, TIME OF DAY or FREE RUN in the TIMECODE screen. In FREE RUN, the FLOW 4V can also send or receive timecode: tap SEND to output a synchronization signal on the STEREO OUT connector, for jam-syncing other units, or tap RECEIVE to synchronize the FLOW 4V to an incoming SMPTE timecode signal on the tip of the AUX IN connector. See [Timecode Modes](/sd-recording-and-playback.md#timecode-modes).
5. **Set the levels.** The channel trim can be set manually with the channel fader in each channel screen, with the red infinite knobs on the FLOW 4V, or in the 4V App. Alternatively, in the METERS screen, touch and hold the channel group areas 1–4 or 5–8 to apply Easy Level, which adjusts the trim of the active channels automatically so the post-fader signal peaks at approximately −18 dB. See [Easy Level](/channels-and-processing.md#easy-level) and [4V App](/control-surface-and-app.md#id-4v-app).
6. **Record-enable the channels.** When recording to an SD card, only record-enabled sources are written to the card. Swipe in the Recorder section to reach the REC ENABLE screen. See [Recording](/sd-recording-and-playback.md).
7. **Set Pre-Roll if needed.** Pre-Roll is set in the Recorder section, on the screen following REC ENABLE. With Pre-Roll enabled, the five seconds preceding the moment the Record button is pressed are included in the recording. Pre-Roll is available in Free Run and Time of Day, and is not available in Rec Run. See [Transport Controls](/sd-recording-and-playback.md#transport-controls).


---

# 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/get-started.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.