BEHRINGER WING · NATIVE .SNAP

Native WING snapshot import and export.

Import a native .snap from WING Edit, build or revise the plot, then export a patched native snapshot with the exact write scope shown before download.

Open load·in See what it won't touch

01 — The format

One supported native path

load·in's supported WING workflow uses the desk's native JSON snapshot. WING .scn files are not accepted because load·in cannot currently preserve them with the same safety guarantees.

.snap — native snapshot

JSON

WING's own nested snapshot format

Write strategy

Template patch

Starts from an imported snapshot or a desk-authored WING template

Editor

WING Edit

Offline editor reads/writes the same files as the desk

The fixture-backed round trip, including the 48V and DCA write proofs, runs against native .snap snapshots. This is the WING format to use with load·in.

02 — What load·in reads

Surface the channel plan

Import a supported WING snapshot and load·in surfaces its channel plan for the stage plot and input list. WING snapshots remain a distinct workflow from X32 scenes.

03 — What load·in writes

The download preview is the contract

✓Channel names and the supported identity fields shown in the export preview

✓48V on/off for supported local inputs — fixture-backed native .snap write and re-import

✓DCA membership — written using the native WING snapshot tag grammar

✓Aux send on/off, tap, and level — written into the native .snap and read back by re-import, to the format's own quantization step

—EQ curves, dynamics parameters, FX sends, gain, inserts, mute-group setup, and routing beyond the aux-send fields above are not public write claims.

04 — What load·in leaves alone

Untouched means untouched

For an imported supported snapshot, load·in starts from that snapshot and patches the supported fields. For a new project it starts from a desk-authored WING template. The export preview names the current limits before a file is written.

05 — What load·in won't claim

The honest edges

—WING .scn is not the supported round-trip path. Export a native .snap from WING Edit instead.

—Processing values and routing outside the export preview are preserved or left at the source/template value; they are not advertised as translated settings.

—Snapshot versions outside the verified snapshot.11 write envelope remain read-only.

06 — Before the show

Verify it before it's the desk's problem

Open the exported .snap in WING Edit and confirm the fields named in the export preview landed where you expect.
Load into a spare scene/snapshot slot first — never straight over a show-critical one.
Check DCA membership on the surface against your input list.
If you're loading a .snap, confirm 48V state on channels that need phantom before patching mics in.
Check the aux sends the preview names — on/off, tap, and level — against your monitor plan.
Confirm processing and routing that the preview does not claim manually on the desk.

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

Build the plot once. Export the file WING actually opens.

Import your native WING snapshot. Edit what's supported. Export a patched native copy.

Try load·in free →

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