Frequently Asked Questions

This is almost always one of four things:

• Wrong format — Make sure you selected the correct console model in the export dropdown. An X32 .scn file will not load on a Yamaha, and vice versa.
• USB format — Most consoles require FAT32 formatted USB drives. If your drive is formatted as NTFS or exFAT, the console may not recognize it. Reformat the drive to FAT32 (you can usually do this from the console itself).
• File location — Some consoles expect files in a specific folder on the USB drive. Check your console's manual for the correct path.
• Firmware version — Older firmware may not support newer file formats. Check if a firmware update is available for your console.

Every console has a maximum number of characters it can display on its scribble strips. load·in auto-abbreviates long names to fit, but you may want to customize them.

If names are getting cut off, shorten them in the List tab before exporting. Common abbreviations: "Kick Drum" becomes "Kick", "Acoustic Guitar" becomes "Ac Gtr", "Lead Vocal" becomes "Ld Vox".

First: Check any portable .show backups you exported to Files, iCloud Drive, another device, or storage you control.

Local plots: Clearing browser or app data can delete work stored only on that device. Export important work as a portable .show project to Files, iCloud Drive, another device, or storage you control.

Account sync: Treat it as active only after load·in reports the plot as synced. A portable .show project remains the user-controlled backup for show-critical work.

Each console has its own color palette, and they are not identical across brands:

• X32/M32: 16 colors (Red, Green, Yellow, Blue, Magenta, Cyan, White + light variants)
• Yamaha CL/QL: Different palette — "Red" on X32 may appear slightly different on a Yamaha

load·in picks the closest available color for each console. The mapping prioritizes readability: drums get warm colors, vocals get cool colors, DI inputs are neutral.

Yes. load·in currently imports these supported file types:

• .scn files from Behringer X32/Midas M32 and Behringer WING
• .snap files from Behringer WING
• .clf files from Yamaha CL/QL
• .ses files from DiGiCo SD series
• .zip / folder / SCENE*.DAT files from Allen & Heath SQ
• .tar.gz / .zip archives from Allen & Heath dLive
• .dsh files from Avid VENUE S6L
• .dm3f / .RIVAGEPM files from supported Yamaha DM3 and RIVAGE PM workflows
• .txt files for generic input lists

The format is auto-detected when its signature is supported. Confirm the detected desk, channel count, and every imported field before accepting the import. See the Console Import guide for full details.

After you've opened the app once with a connection, you can build your plot, edit it, and open your saved shows without one. Purchases, account features, integrations, and all console-file import and export require internet access, on every platform including the iPhone and iPad app.

No login is required to plan offline. Open the app once while online so it's ready for offline use; account features, purchases, integrations, sharing, and console file import/export require a connection. On mobile, use "Add to Home Screen" for an app-like launch experience.

load·in currently supports these console families and export targets:

• Behringer X32 / Midas M32, X-Air, and WING
• Yamaha CL / QL, DM3, and RIVAGE PM
• DiGiCo SD series
• Avid VENUE S6L
• Allen & Heath SQ and dLive
• DAW template export for labeled recording-session setup

New files made in load·in should preserve the fixtures and channel work you create in the app. Imported console files are handled conservatively, but exact carry-through can vary by desk model, firmware, and fields the manufacturer does not document. Keep backups of production files and test the exported file on the intended desk or editor before show time. See the Console Export guide for per-console instructions.

Free tier: Up to 3 saved plots, RF tools, generic CSV, watermarked PDF/PNG, and native X32/M32-compatible console files. No credit card required.

Pro: $99 one-time purchase with no subscription or recurring charge. Unlimited plots, clean exports, additional supported console workflows, DAW templates, Pro export tools, and supported format updates. No per-seat charges.

See the load·in pricing for current details.

In load·in, tap the upgrade prompt or go to the File tab. On iPhone and iPad, buy or restore the non-consumable through the App Store purchase controls. On the web app, use the web checkout and license recovery flow. See the Pro Features guide for full details.

Yes. load·in works on any device with a modern browser — phone, tablet, laptop, or desktop. It is mobile-first, meaning the interface was designed for touch screens first and then scaled up for larger displays. Many operators use it on a tablet at front of house or on their phone during load-in.

No, on purpose. 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 between desks never moves it on its own.

This is a safety decision, not a missing feature: a shared or split preamp means a wrong gain becomes someone else's input, and phantom sent to the wrong place can damage a mic or DI. Gain and phantom stay a desk-side decision, made once, by whoever owns that input.