Recording#

A recording captures the raw signal from a streaming headset to a file on the device. You start and stop it from several places in the app — most directly with the ● Rec button in the Live signal viewer dock. This page covers starting and stopping, where files go, the BDF and CSV formats, markers, snapshots and iOS lifecycle limits.

Starting and stopping#

Where

How

Viewer dock

● Rec — tap to start, tap again to stop

Device card

● Rec — starts streaming and recording without leaving the device list; while recording the same button becomes a red stop button with a timer

Contact check

Record — switches to streaming and starts recording

Root return bar/viewer

Stop controls finish recordings cleanly before stopping the stream

When ● Rec on the device card or Record in the contact check starts the stream, the recording begins at the stream’s first sample. ● Rec in the viewer records from the moment you tap it.

When a recording finishes you get Saved m:ss · FORMAT · filename with an Open action. Saving does not leave the current screen or stop the stream. Open enters review; Dismiss clears the notice. Open is unavailable while a firmware update is taking over the app (see Recordings and review).

Where files go#

Recordings and snapshots are stored in the app container under Application Support/BrainAccess/recordings/ and are shown in Recordings.

Filenames: YYYY-MM-DD-HH_mm_ss_TAG.bdf (or .csv), where TAG is a short uppercase hex identifier derived from the headset identifier used on this device. If you set a Session label it is appended as a slug: 2026-08-04-22_07_16_A1B2C3_eyes-closed.bdf.

Each recording has a <filename>.metadata.json beside it (see Metadata file below). Use in-app Share or Save to Files to copy files out of the app before uninstalling or moving to another device. See Files, storage and privacy for storage, backup and uninstall details.

Choosing a format#

BDF (default)

CSV

Format

24-bit BDF+ (BioSemi/EDF+ family)

Plain text, comma separated

Opens in

EDFbrowser, MNE-Python (read_raw_bdf), EEGLAB, any EDF/BDF tool

Any spreadsheet, pandas, MATLAB

Markers

Stored as BDF+ annotations. Up to about four marker annotations can be stored in each one-second BDF record; extra markers in the same second are dropped when the file is closed and the app warns you

Stored in a marker column, no limit

Contact flags

One contact_<channel> signal per channel (1 = connected, 0 = not)

One contact_<channel> column per channel

Dropped-sample flag

A Streaming signal — 1 where a sample arrived, 0 where the link dropped it

A streaming column, same values

If the session ends abnormally

Every complete one-second record can be recovered; a trailing partial second is dropped

Less robust; a final write failure can discard the file

Warning

If storage runs out mid-session, a CSV recording can be discarded entirely. BDF commits every complete second as it is written, so an interrupted session can still open. Prefer BDF for long or unattended sessions.

BDF contents. One signal per active EEG channel, labelled with your electrode names, in uV; then Accelerometer x/y/z in m/s^2 if the headset has one; then Gyro_X/Y/Z in deg/s if it has a gyroscope (EXG8); then a SampleCounter signal; then a Streaming flag signal; then one contact_<channel> signal per EEG channel (1 while the headset reports the electrode as connected, 0 otherwise — labels are limited to 16 characters, so a long electrode name is clipped); then annotation channels for markers. Data is written in one-second records at the configured sample rate; a trailing partial second is dropped. The session label is stored in the header, together with the equipment (BrainAccess_<MODEL>_<serial>), the reference and ground electrodes (ref=<electrode>_gnd=<electrode>) and, per signal, the electrode type (dry gold-plated pad or pin electrode) and a prefilter of None for EEG — the headset applies no hardware filter. Signal labels are the plain names, so a signal’s type and the reference live in the metadata file below.

SampleCounter is the headset’s own per-sample counter, stored modulo 2²⁴ (0 to 16 777 215, no unit): it wraps back to 0 after 16 777 216 samples, which a reader can unwrap. It lets you check for lost or repeated samples. Tools that plot every signal as a channel will show SampleCounter, Gyro_*, Streaming and contact_* among them; the app’s own review view hides them (and shows the contact signals as its contact indicators).

Metadata file. Next to every recording, in either format, the app writes <recording file name>.metadata.json (for example …A1B2C3.bdf.metadata.json) as soon as recording starts, so even a session that was killed is described. It holds the headset and montage in BrainAccess Board’s stream-metadata format: manufacturer, model, serial number, firmware and hardware version, sample rate, reference, ground, cap, the app version, and a channels list with each signal or column of the file in file order, under the exact name used in the file, its type (EEG, ACCEL, GYRO, CONTACT, SAMPLE, MISC), unit, and for EEG channels the standard 10-05 position and electrode hardware. A CSV’s list covers its signal columns (<name>_uV, accel_*, contact_*, streaming, sample_counter, gyro_*); sample, time_s and marker are row bookkeeping and are not listed. The metadata file is what a converter uses to turn the recording into a BIDS dataset without losing the headset information. A recording shorter than the first whole second is discarded together with its metadata file. If the metadata file cannot be written the app tells you (Recording metadata file could not be written.) and still records. The browser does not list it: it is shared, deleted and restored together with its recording.

CSV contents. Header row:

sample,time_s,P8_uV,O2_uV,…,accel_x,accel_y,accel_z,contact_P8,contact_O2,…,streaming,marker,sample_counter,gyro_x,gyro_y,gyro_z
  • sample — running sample index, time_s — seconds from the start with four decimals,

  • <name>_uV — raw signal in microvolts,

  • accel_* — accelerometer in m/s², only if present,

  • contact_* — 1 when the headset reports that electrode as connected,

  • streaming — 1 when the sample arrived, 0 when a gap was filled,

  • marker — the marker label on that sample, if any,

  • sample_counter — the headset’s own sample counter, the full value (it does not wrap in CSV),

  • gyro_* — gyroscope in °/s, only if present (EXG8).

The new columns are appended after the existing ones, so files and scripts that read columns by name keep working. A row that carries only a marker leaves the value columns, sample_counter and gyro_* empty.

If you set a session label, the file starts with a # session: <label> comment line.

Automatic annotations. Every 60 seconds of recording the app adds a battery <percent>% marker, and if the Bluetooth link drops mid-recording it adds a link drop marker at the last second that was saved. They appear with your own markers in the CSV marker column or as BDF+ annotations (and count towards the BDF’s four annotations per second).

Note

Recordings always contain the raw signal. Display filters, the notch and contact suppression are not applied to the file.

While recording#

  • The device card and viewer show a running m:ss timer.

  • N samples lost counts samples that never arrived — over Bluetooth, or, with firmware 3.8 or later, conversions the headset itself missed. The app fills each gap with zeros flagged as missing, so the timeline stays exact.

  • There is no fixed duration limit other than free storage and iOS/runtime constraints. Check storage before a long session.

  • iOS background Bluetooth mode allows continuation only while the system permits it. A system kill, force-quit, power loss or radio interruption can end the session; the app does not resume an interrupted recording into the same file.

What ends a recording#

Event

Result

Rec / viewer Stop / device stop

File is closed cleanly and saved

Disconnect while recording

You are asked to confirm; disconnecting ends the recording now and keeps what was written

Headset goes out of range or switches off

The recording is finished at the last written second and saved. It is not resumed on reconnect

A firmware update

Refused while a recording is running — stop it first

Storage runs out

The recording stops and you are told. BDF keeps completed seconds; CSV may be discarded

App killed by the system

BDF keeps completed seconds and available markers; the app reports the recovered duration when opened

Markers#

Markers are timestamps with a label, written into the recording and drawn on the plot as amber dashed lines (see Live signal viewer).

  • Tap the Marker chip to drop a marker with the last label you used.

  • Tap the caret or long-press for the preset list: Marker, Note, Bad, Event by default, plus Edit presets….

  • Presets are 1–8 labels, up to 24 characters each. Last-used marker and presets are remembered.

  • A marker is placed on the sample the headset took when you tapped, not on the last sample that had arrived over Bluetooth. With firmware 3.8.0 or later the headset’s own clock places it on the nearest sample, to within about a millisecond; older firmware is estimated from Bluetooth packet timing, a few tens of milliseconds early at most.

Markers land in the CSV marker column or as BDF+ annotations. BDF can store up to about four marker annotations in each one-second record, so a dense burst of markers in the same second can overflow even when the rest of the recording has few markers. The app warns if BDF drops surplus markers. The plot shows the most recent 256 markers — CSV keeps them all.

Snapshots#

The camera icon in the viewer saves a PNG of the current view, named snapshot-YYYY-MM-DD-HH_mm_ss.png, and confirms with Snapshot saved: . Snapshots appear on the Snapshots tab of the browser; open or share them from there.

See also#