How to Import X32 Scene Files to Create Instant Stage Plots

Here's something no other stage plot tool can do: Import your existing X32/M32 scene files and automatically generate a professional stage plot. Stop retyping channel names. This is the game-changer.

The Problem We All Know Too Well

You've just finished soundcheck. The band's happy, the mix is dialed, your X32 scene is saved. Now production wants a stage plot for tomorrow's festival advance.

Your options until now:

• Manually recreate everything in a stage plot app (30-60 minutes)
• Type out a channel list in Excel (error-prone, ugly)
• Send a photo of your scribble strip (unprofessional)
• Use the generic plot from 3 tours ago (wrong)

This is insane. The information already exists in your console. Why are we retyping it?

Enter Console File Import

stage·left can now import scene files directly from your console and automatically:

• Extract all channel names and numbers
• Detect instrument types from naming patterns
• Create appropriate stage elements (drum kit, keys, mics, etc.)
• Arrange them intelligently on the stage
• Preserve your color coding and organization

What took 45 minutes now takes 45 seconds.

How It Works

Step 1: Export from Your Console

On your X32/M32:

SETUP → config → SAVE
Select "Scene" → Save to USB
File saves as: MyShow.scn

Or if using X32-Edit/M32-Edit, just File → Save Scene.

Step 2: Import into stage·left

1. Open stage·left
2. Click "Import Console File" in settings
3. Select your .scn file (or drag & drop)
4. Watch the magic happen

Step 3: Fine-Tune and Export

The import gets you 90% there. Drag a few elements to match physical stage positions, add any additional notes, and export. Done.

Supported Console Formats

Current support (more coming):

• Behringer X32 / Midas M32 - .scn files, .txt snippets
• Yamaha CL/QL/TF - Name list CSV exports
• Allen & Heath dLive/Avantis - Director CSV exports
• Allen & Heath SQ - CSV exports
• DiGiCo SD/Quantum - Semicolon-delimited CSV
• Generic CSV - For everything else

Smart Detection Examples

stage·left intelligently parses channel names to create the right elements:

Channel Name → Detected Element
"Kick"       → Drum Kit (with kick input)
"VOX 1"      → Vocal Mic
"GTR L"      → Guitar Amp (stereo)
"KEYS DI"    → Keyboard (DI)
"TRACK L"    → Playback (stereo)

It even handles variations: "BD", "B.Drum", "Bass Drum" all map to kick drum. "Vox", "VOC", "Lead Vocal" all create vocal mics. Built by someone who's actually mixed shows.

Real-World Use Cases

Festival Advances

Import last night's show file, generate plot, send to tomorrow's festival. Include it with your rider. Update it as the tour evolves.

Documentation

Finally document that complex corporate rig. Import the scene file, arrange the stage elements, export PDF. Archive it for next year.

Rental Returns

Venue needs to know what you used? Import your scene, export the input list. Accurate channel count, no guessing.

The Technical Details

For those interested, X32 scene files use a text-based OSC command format:

/ch/01/config/name "Kick"
/ch/01/config/color 1
/ch/01/config/icon 65

stage·left parses these commands, extracts the relevant data, and rebuilds your input list. Colors map to instrument categories. Icons inform element selection. It's surprisingly elegant.

Why This Matters

This isn't just a convenience feature. It's about accuracy and professionalism. Every typo in a stage plot causes confusion. Every outdated input list wastes time. Every manual recreation introduces errors.

By importing directly from the source of truth—your console—we eliminate these problems. The plot matches the show file. Always.

What's Next

We're adding more console formats based on user requests. Avid S6L, Soundcraft Vi, and SSL Live are next. Have a specific console? Let us know.

This is just the beginning. Imagine: bidirectional sync, automatic patch sheets, real-time updates. We're building the bridge between documentation and reality.

No more retyping. No more outdated plots. No more "I'll send it after the show" (and never do). Just import, adjust, export. Done.