The Rosetta Stone for
live sound consoles.
Channel names, colors, and stereo links, carried between supported desks. Or built from nothing, at the desk.
x32/m32 native free · pro one-time purchase for supported paid formats
Specific desks. Specific value.
Not "export to any console on earth." A tighter promise: channel names, colors, stereo relationships, and mix labels where the supported workflow exposes them. Supported same-console imports and exports patch scoped fields in the imported source; target-template generation and known limits are identified before export.
| Console family | File type | Tier | Coverage |
|---|---|---|---|
| X32 / M32 | .scn | Free | X32/M32 carry the broadest verified parameter writeback. |
| WING | .snap | Pro | Native WING snapshot import, light-touch edit, and export with unmodeled snapshot data preserved. |
| X-Air | .scn | Pro | Model-specific native scene import and export with limits shown before download. |
| Yamaha CL / QL | .CLF | Pro | Supported fields are listed in the export preview and must be verified in Yamaha Editor or on the target desk. |
| Yamaha DM3 | .dm3f | Pro | Native import and export for channel identity and selected standard-strip fields, with preserved fields and limits shown before download. |
| Yamaha RIVAGE PM | .RIVAGEPM | Pro | Names-only, scoped RIVAGE PM generation with explicit container and validation limits. |
| DiGiCo SD Series | .ses | Pro | Native SD7–SD12 workflow for the fields declared in its preview. 48V is written to Mic-type rack sockets, and aux send level and on are written on SD7–SD11 — check both at the desk. |
| Avid VENUE S6L | .dsh | Pro | Native import and export for the verified identity, stereo, and preservation scope shown before download. |
| Allen & Heath SQ | folder / .zip / SCENE*.DAT | Pro | Native archive workflow; the app states the exact fields before export. |
| Allen & Heath dLive | .tar.gz | Pro | Verified native archive import and export, identity fields, and the bounded writeback fields disclosed before export. Unverified data is left untouched rather than rewritten. |
load·in is independent interoperability software; all console names and trademarks are property of their respective owners — see our Trademark Notice.
gain and phantom power — a safety decision, not a gap
Preamp gain always stays exactly as the engineer set it at the desk — load·in never touches it, on any export. Phantom power (48V) is written only when you switch it on or off yourself in the app, on desks where that's proven; translating a show between desks never moves it on its own. A shared or split preamp means a wrong gain is someone else's input, and phantom sent to the wrong place can damage a mic or DI — that's why gain stays hands-off entirely, and why phantom only ever moves when you ask it to.
the venue with bad wifi — what works at zero bars
The plot, the input list, and your saved .show projects sit on the device. Once the app has loaded once, you can open, edit, and save them with the wifi off. Making or reading a console file is the one step that needs a connection — it's a small file and a few seconds, so a single bar of phone signal is enough. If the room is a dead spot, build the console file before you get there. The .show project carries the whole show and moves like any other file: AirDrop, share sheet, email, or a USB stick.
A bad plot wastes time. A bad file wastes trust.
Your plot says 24 inputs. The house patched 24. The console file says 28. Now soundcheck starts with a scavenger hunt.
Pull channel identity out of a supported desk file instead of retyping it into a PDF, a note app, and another desk.
Carry the parts of the showfile that actually help the next engineer get moving: names, mixes, colors, and stereo logic.
The stage plot, input list, and supported desk file line up. Less historical fiction. More actual show prep.
The information already exists in your console.
This is the show it's actually for.
Not hypothetical workflow diagrams. The four things that keep happening at load-in.
Another engineer's show file lands in your inbox an hour before doors, and it needs to run on a desk they never touched. Import it, review what carried across for that desk, and rebuild the rest by ear — not by retyping 48 channels from a printout.
The band shows up with one more input than the advance said — a second vocal mic, a keyboard rig nobody mentioned. Add it to the stage plot and it drops into the input list where it belongs. You don't retype every channel underneath it by hand.
Different volunteers every week, a different instrument list every week, and the desk has to be right before the service starts. Hand the volunteer a plot and a list instead of a console with no notes on it.
Twenty minutes between acts, a different desk on the next stage, and a photo of a napkin where the input list should be. Build the plot once and export what that stage's desk actually reads. See the festival workflow →
load·in is live. The rest of go·for·show is still settling.
There are more tools here. They are not the thing I would send a stranger to buy from a Reddit thread today. load·in is.
Stage plots, input lists, RF export, and supported console file workflows. This is the public launch product. Open load·in →
Festival and service timing. Useful. Still in preview.
Free to plan. $99 to unlock Pro.
load·in is free with up to 3 saved plots (enter your email in the app to unlock unlimited), free native X32/M32 scene export, CSV, and watermarked PDF/PNG exports. Pro is a $99 one-time purchase with no subscription or recurring charge. It unlocks additional supported console workflows, DAW templates, clean exports, and Pro export tools. Every workflow states what it writes, preserves, and leaves out.
| Entitlements | Free | Pro |
|---|---|---|
| Saved plots | 3 | unlimited |
| PDF / PNG exports | watermarked | clean |
| Native console files | x32/m32 | supported paid formats |
| Stage planning | included | included |
| Password-protected .show projects | included | included |
| DAW templates | — | supported formats |
| $99one-time |
free stays free · console files are never modified beyond what you asked for · making or reading a console file needs a connection
A touring pro who got tired of bad handoff data.
"I built load·in because I got tired of loading in and discovering the advance was wrong. The source of truth should travel with the show."
FOH. Playback. Tour management. More than a decade of typing "Kick In" into desks on multiple continents.
Gryphon Graham · FOH Engineer · Playback Tech · Tour Manager