X-AIR XR12 / XR16 / XR18 · .SCN

X-Air is X32 lineage, not an X32.

Import a plaintext X-Air scene, build the plot, and export a patched copy with Pro. XR18 has its own fixture; smaller boards use a scoped-down version of it.

Open load·in See what it won't touch

01 — The format

The same OSC scene, a smaller surface

X-Air's .scn is plaintext, same lineage as X32 — but it's not an X32 file wearing a different badge. XR12/16/18 have fewer channels, fewer aux buses, and no onboard DCA groups. The scene comes off the mixer through the X-Air Edit app (or the free ME/XR apps for personal monitor control), not a front-panel USB slot the way X32 works.

Model	Inputs	Aux buses	DCA groups
XR18	16	6	0 — not on the desk
XR16	16	4	0 — not on the desk
XR12	12	2	0 — not on the desk

X-Air has no DCA groups on any model — that's not a load·in gap, the hardware doesn't have the control.

02 — What load·in reads

Names, color, icon, per channel

Import an X-Air scene and load·in reads channel names, colors, and icons — X-Air borrows X32's 16-color palette and 74-icon set rather than running its own table, since the OSC parameter model is the same underneath.

03 — What load·in writes

Scoped, native writeback

✓Channel names, colors, icons in the supported Pro workflow

✓Mute, fader level, pan

✓HPF, EQ, gate, and comp — on/off only, not the values inside

✓Aux send on/off, tap, and level — XR18 only, verified by export and re-import to the format's own quantization step

—XR16 and XR12 do not write aux sends. They ride a model-capped XR18 template and stay caveated until each model has its own captured fixtures.

04 — What load·in leaves alone

Untouched means untouched

Because .scn is plaintext, load·in can patch a single line without touching the lines around it. Routing, FX, and anything else in the scene rides through exactly as it came in.

05 — What load·in won't claim

The honest edges — and one worth reading twice

—XR18 has a dedicated fixture set behind its verification. XR16 and XR12 do not. Both ride a capped-down version of the XR18 template — real desk families, adjacent lineage, but not their own captured scene files yet. Give the exported file a closer look on those two boards before a show that matters.

—No aux send writeback on XR16 or XR12, and no DCA claim on any model — the hardware has no DCA groups on any X-Air board.

—EQ, gate, and comp are toggled on or off, not tuned.

06 — Before the show

Verify it before it's the desk's problem

Open the exported scene in X-Air Edit and confirm names, colors, and icons before loading it live.
On XR16/XR12 specifically, do a full read-back after load — compare the surface against your plot channel by channel.
Load into a spare scene slot first, not over your only working scene.
On XR16 and XR12, confirm aux sends manually — load·in does not write them on those models.

Other supported workflows: X32/M32 · WING · the full list is on the console support page.

Small board, same discipline.

Import your XR12, XR16, or XR18 scene. Build the plot. Export a patched native copy with Pro.

Try load·in free →

No signup required to plan offline. X-Air console-file import and export require Pro and an internet connection.