Behringer X32 Stage Plot Guide for Native .scn Export

About the X32

The Behringer X32 shows up on more small to mid-size stages than almost any other digital console. With 32 mic and line inputs, 16 mix buses, and fast scene recall, it is a common target when a band hands a house engineer an input list before load in.

What Stageplot Pro exports for the X32 today

Stageplot Pro ships a native X32 / M32 scene (.scn) export. This is a real console scene file the desk loads directly, not a text list you retype by hand. It carries:

• Channel names pulled straight from your input list, in channel order
• Starting EQ and gain settings, generated per instrument type by an AI enhancement pass
• Dynamics and send routing built from the monitor mixes on your plot

The export runs through a short server-side AI step, so it requires a free Stageplot Pro account. You can build your whole stage plot as a guest, then sign in only when you are ready to export the file.

How to export a scene file

1. Build your stage plot and confirm the input list is in the channel order you want on the desk.
2. Add monitor mixes so sends route correctly in the exported scene.
3. Sign in, or create a free account, and open the export menu in the toolbar.
4. Choose "X32 / M32 scene (.scn)." The AI pass usually finishes in under two minutes, and falls back to a base scene automatically if it does not complete.
5. Load the downloaded file onto the X32, or send it ahead to the house engineer so soundcheck starts with real channel names already in.

Nothing about this export is a guess. The .scn structure is documented and the emitter is built and tested against it, so the file that downloads is a real scene the console reads correctly.

If the AI pass does not finish

Occasionally the AI enhancement step runs long or fails on the AI provider's end. Stageplot Pro does not leave you waiting indefinitely. If the AI pass times out or errors, the export automatically falls back to a base .scn file built directly from your input list and monitor mixes, so you always get a working scene file with correct channel names, even on a bad network day or a busy AI queue. You lose the AI-generated EQ starting points in that case, but you never lose the export itself.

Getting your input list right first

The scene file is only as good as the input list behind it. Vague names like "Mic 3" turn into vague channels on the desk. Name things the way you would say them out loud to an engineer: "Lead Vox," "Kick In," "Guitar DI." Our input list guide walks through naming and ordering channels so the export lands exactly where you expect.

Common X32 stage plot setups

Bands running a full mix through an X32 are often five and six piece line ups with drums, bass, two guitars, and vocals, or larger acts adding horns or backing tracks. If you are starting from scratch, the five piece rock band stage plot and wedding band eight piece stage plot templates both use input counts that map cleanly onto an X32's 32 channels with room to spare.

What the export does not cover

The .scn file pre-labels channels and gives you a sensible starting point, but it is not a substitute for a soundcheck. Room acoustics, monitor wedge placement, and gain staging still need a real engineer listening in the room. Think of the export as removing the blank-slate part of the job, the naming and basic routing, so the engineer's time goes toward things a file cannot fix.

Try it

Open the editor, place your gear, build your input list, and export a real X32 scene file in minutes, no spreadsheet required.