Console Export Guide
Generate a supported console file from the same project as your plot and input list. The current export selection includes X32/M32/X-Air, WING, Yamaha CL/QL and DM3, scoped RIVAGE PM generation, DiGiCo SD7–SD12, Allen & Heath SQ and dLive, and Avid VENUE S6L.
The detailed walkthroughs below cover X32/M32, Yamaha CL/QL, and dLive. Every target has different field coverage. Read the preview shown before download; it is the source of truth for what that workflow writes, leaves unchanged, or requires you to finish on the desk.
What the Export Includes
Depending on your console, the export file carries:
- Channel names — abbreviated to the selected console's documented display limit.
- Colors and icons — only where the selected workflow exposes and verifies them.
- Stereo and mix labels — only where the export preview declares verified support.
- Routing, phantom, and processing — format-specific; never assume these transfer unless the preview explicitly says so.
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. This is deliberate: on a shared or split preamp, a wrong gain becomes someone else's input, and phantom sent to the wrong place can damage a mic or DI. Gain stays a desk-side decision, made by whoever owns that input.
How to Export
- Tap the File tab in load·in.
- Tap Export Console File.
- Select your console model from the dropdown.
- Read the scope preview and save the result as a new copy.
- Open that copy in the manufacturer's current official editor when one is available.
- Transfer it using the method required by the target console, then line-check names, patch, phantom, stereo, sends, processing, and outputs.
USB and folder requirements differ by manufacturer, model, and firmware. Follow the target console manual. Many desks use FAT32 media; dLive archives also require the expected Allen & Heath folder structure when handed to a desk by USB.
Behringer X32 / Midas M32
X32 / M32
- Build your stage plot and review the input list in load·in.
- File tab → Export Console File → select X32/M32.
- Read the preview, then download the
.scnfile as a new copy. - Copy the
.scnfile to a USB drive (FAT32 formatted). - On the X32: Utility → Import/Export → USB → load the scene.
- Validate the copy in X32-Edit or M32-Edit, then line-check it on a spare scene before show use.
The X32/M32 workflow has the broadest current verified parameter writeback. The X32 input layer is limited to 32 channels; review truncation warnings and every routing or monitor-send decision before loading the desk.
Yamaha CL / QL Series
CL1 / CL3 / CL5 / QL1 / QL5
- Build your stage plot and review the input list.
- File → Export Console File → select your model (CL1, CL3, CL5, QL1, or QL5).
- Read the preview and download the CLF or CSV produced by the selected workflow.
- Open the copy in the current Yamaha Editor workflow that matches the target model.
- Transfer it using Yamaha's documented method for that file type and firmware.
- Verify names, colors/icons, stereo, patch, phantom, processing, sends, and outputs before show use.
Channel counts: CL5 supports 72 mono + 8 stereo inputs. CL3: 64 mono. CL1: 48 mono. QL5: 64 mono. QL1: 32 mono. load·in keeps the original project name and normalizes or transliterates the exported scribble-strip name when the selected workflow requires it.
Allen & Heath dLive
dLive Native Archive
- Start with a new load·in project or import a supported dLive native archive.
- File → Export Console File → select Allen & Heath dLive.
- Read the desk- and version-specific preview, then save the result as a new copy.
- Open the downloaded ZIP and extract its
AllenHeath-dLivefolder at the destination drive's root. The native show archive is insideAllenHeath-dLive/Shows/. - Open the exported show in the current dLive Director release that matches the target desk and firmware.
- Confirm names, colors, stereo ganging, mixes, processing, patch, 48V, sends, outputs, and any warnings before desk use.
dLive uses the same patch-in-place safety principle as X32/M32: supported edits are applied to native show data while unrelated data is preserved. The verified fields and version floor differ, so dLive is not described as having identical parameter coverage. The export preview is authoritative.
Character Limits by Console
Every console has a maximum number of characters it can display on its scribble strips. load·in auto-abbreviates long names to fit (for example, "Kick Drum" becomes "Kick", "Overhead L" becomes "OH L"). Review the exported file to confirm abbreviations make sense for your setup.
| Console | Max Characters |
|---|---|
| X32 / M32 | 12 |
| Yamaha CL / QL | 8 |
If channel names are getting cut off, try shortening them in the List tab before exporting. Common abbreviations: "Kick Drum" → "Kick", "Acoustic Guitar" → "Ac Gtr", "Lead Vocal" → "Ld Vox".
Team Handoff Checklist
When one operator hands off to another, here is what each person should provide or review. Keeping this list consistent means the incoming tech can get up to speed fast.
What the Outgoing Operator Provides
- Saved stage plot in load·in or a portable .show backup
- Console scene file on USB (exported from load·in or saved from the console)
- Notes on any non-standard routing, processing, or monitor mixes
- RF frequency assignments if using wireless microphones
- Venue-specific notes (room quirks, speaker positions, AC power locations)
What the Incoming Operator Does
- Open load·in and load the saved plot or import its portable .show file.
- Review the input list — confirm it matches the physical stage.
- Export a fresh console file for today's show (if anything changed).
- Open the export in the official editor when available, then load it as a copy or spare scene.
- Walk the stage and verify every channel name, physical patch, phantom, stereo link, send, processing block, and output before show use.