Console Import
Already have a supported console file or channel list? Import it into stage·left to build from existing channel data, or start from scratch and generate a supported console export later.
How to Import
- Tap the Files tab in stage·left.
- Tap Import Console File.
- Select your file from your device.
- stage·left auto-detects the format and parses the channels.
- Your input list populates with channel names, colors, and routing data from the file.
You can also drag and drop a console file directly onto the app. stage·left will recognize the format and import it automatically.
Supported Formats
stage·left reads these shipped console and list formats today:
| File Type | Consoles | What It Contains |
|---|---|---|
.scn |
Behringer X32, Midas M32 | Channel names, colors, icons, stereo links, and supported X32/M32 scene metadata |
.clf |
Yamaha CL/QL | Channel names, colors, stereo links, and supported CL/QL metadata |
.scn / .snap |
Behringer WING | Supported WING channel names, colors, stereo links, and scene or snapshot metadata |
.ses |
DiGiCo SD series | Supported DiGiCo SD channel, mix, color, and stereo-link data |
.tar.gz |
A&H dLive | Supported dLive channel, mix, color, and stereo-link data |
.txt |
Generic input lists | Plain-text channel lists (one channel per line) |
.csv / .tsv |
Spreadsheet exports | Tab or comma-separated channel data from any source |
.pdf |
Scanned or printed input lists | stage·left parses the text and extracts channel data |
Auto-Detection
You do not need to tell stage·left which console your file came from. The import engine reads the file structure and automatically identifies:
- The console model (X32/M32, Behringer WING, Yamaha CL/QL, DiGiCo SD, dLive, etc.)
- The channel names and their order
- The color assignments (where the format includes them)
- The routing data (input sources, stereo links)
After import, you can see all of this in the Inputs tab. Review the channels, make any adjustments, and you are ready to go.
Supported Export Workflow
Import is how stage·left starts from real-world console data. When a format has a shipped export path, the imported file gives stage·left the console context it needs to generate a supported export with your updated names, colors, stereo links, and other supported channel data.
Import → Edit → Export
- Import your existing console scene file into stage·left.
- Edit in stage·left — rearrange channels, rename inputs, add new instruments to the stage plot.
- Export back to the same console format.
- Load the updated file on your console.
Imported console context helps stage·left carry supported channel and mix data into the exported file. Verify exported files in the manufacturer editor or on the desk before show use.
This workflow is especially useful for consoles with native scene files. Save a scene from the console to USB, import it into stage·left, make your edits, export the updated file, and verify it in the official editor before loading it on the desk. See the Console Export guide for format-specific details.
What Gets Imported vs. What Gets Updated
It helps to understand what stage·left reads from your file and what it changes on export:
- Read on import: channel names, colors, icons, input routing, stereo links, and console context for supported workflows
- Editable in stage·left: channel names, colors, order, notes, wireless frequencies
- Carried into supported exports: channel names, colors, icons, stereo links, mix names, and other supported console data depending on the format
- Updated on export: only the fields stage·left owns for the chosen format and the values you change