Import supported console files or generate a supported target from scratch. Each preview states which names, colors/icons, stereo, mixes, routing, phantom, and processing fields are written and which still require desk-side setup.
These are the console file workflows load·in publicly ships today.
Import and export native SQ files for channel names, colors, verified stereo relationships, and preserved unedited file data. SQ-5, SQ-6, SQ-7.
Import and export native S6L files for channel names, preserved unedited file data, and — on same-console reorder of an imported show — the full per-strip data block moved to its new slot. S6L-16C, 24C, 32D, 48D.
Import and export native SD files for channel names, mix labels, and preserved unedited file data — including stereo configuration, carried untouched on same-console import-then-export. SD7-SD12.
Scope is not identical across desks. X32/M32 currently has the broadest parameter writeback. dLive writes selected verified native fields and preserves untouched archive data; it is not yet X32-equivalent. Always read the export preview and validate a copy in the official editor or target desk.
These are the native console file workflows load·in ships publicly today.
load·in is independent interoperability software; all console names and trademarks are property of their respective owners — see our Trademark Notice.
If a desk you rely on is not in the shipped list yet, tell us which workflow would help most.
Tell Us What Console You Need →Build your stage plot once. Generate the supported console file you need.
Try Free — Import Your Console File →No signup required to plan offline. Open the app once while online so it's ready for offline use; exporting a console file and account features need a connection.