Console Scene Converter

What carries, and what doesn't

Two desks are never the same instrument, so a show can't move between them without some judgement. Here's where this one makes it, and where it stops. Converting up to the larger desk is mostly lossless; converting down gives things away, and the report names every one of them.

• Stereo pairs collapse going up, and expand coming back. X32 channels are mono and Wing channels are stereo, so every linked pair becomes a single Wing channel — which is why your channel numbers shift as you go down the list. Coming back the other way, each Wing stereo channel becomes two linked mono channels. The X32 only links odd-aligned pairs (1-2, 3-4 — never 2-3), so a stereo channel that would land on an even channel leaves that one empty rather than renumbering the rest of your show.
• Colours are matched, not copied. The two palettes are unrelated. An X32 green becomes the Wing's green, rather than whichever Wing colour happens to share green's index number.
• The patch comes from the routing blocks, not the channel's source field — so a rig running off an AES50 stagebox lands on the Wing's stagebox inputs instead of its local XLRs. Going the other way, those blocks are a hard limit: the X32 patches eight channels at a time, so a Wing show with a channel-by-channel patch can't always be expressed, and the channels that need repatching are named individually.
• You get a partial snapshot going up. It merges into the desk and leaves everything it doesn't know about alone, instead of overwriting your whole console. Coming down you get a full scene file, which is how the X32 loads one.
• The X32 is the smaller desk. 32 channels to the Wing's 40, eight strip colours to its eighteen, four EQ bands to its six, six matrices to its eight. Converting down, whatever doesn't fit is reported — colours that collapsed into one, bands that were dropped, channels that ran off the end.
• Effects, inserts and the routing matrix don't transfer. Neither do settings the target desk has no equivalent for — those are listed in the report rather than guessed at.
• Check it on the desk before a show. Gain structure and dynamics especially. This saves you forty minutes of typing, not soundcheck.

Building a plot from scratch instead? The stage plot builder exports scene files for the X32, M32 and Wing straight from your input list — and the input list guide covers how to lay one out so it survives contact with a house engineer.

Common questions

Can I convert an X32 scene to a Behringer Wing?

Yes. Drop an X32 or M32 .scn scene file in and you get a Wing .snap snapshot back. Channel names, icons, strip colours, input patch, preamp gain and phantom power, high-pass and low-pass filters, EQ, gate, compressor, bus sends, and DCA and mute group membership all carry across. Effects, inserts and the routing matrix do not.

Can I convert a Wing snapshot to an X32 or M32 scene?

Yes. Drop a Wing .snap snapshot in and choose the X32 or M32 as the target, and you get a .scn scene file back. The X32 is the smaller desk, so expect some loss: it has 32 channels to the Wing's 40, eight strip colours to the Wing's eighteen, four EQ bands to the Wing's six, and it patches inputs in blocks of eight rather than per channel. Everything that can't be carried across is listed in the report rather than dropped silently.

What happens to Wing stereo channels on an X32?

The X32 has no stereo channel, so each Wing stereo channel becomes two mono channels with the desk's channel link turned on. The X32 only links odd-aligned pairs — 1-2, 3-4, never 2-3 — so a stereo channel that would have landed on an even channel leaves that channel empty instead. Channel order is kept identical to the Wing rather than shuffled to fill the gap, because renumbering a show against its source is a worse problem at 2am than a spare channel. The empty channels are listed in the report so you can reuse them.

Why does the converter say my input patch needs repatching?

Because the X32 patches inputs in blocks of eight channels, not one at a time. A Wing show where channel 1 comes from a local input and channel 2 from an AES50 stagebox can't be expressed on the X32 — both channels sit in the same block, and a block has a single source. The converter picks the routing that fits the most channels in each block and names the ones that fall outside it, so you know exactly which to repatch on the desk.

Does it work with a Midas M32?

Yes. The M32 and X32 share the same scene file format, so an M32 .scn converts exactly the same way. Scene files saved by X32-Edit and M32-Edit work as well as ones saved on the console itself.

What happens to stereo linked channels?

X32 channels are mono and Wing channels are stereo, so each linked pair on the X32 becomes a single Wing channel. That's why the channel numbering shifts as you go down the list — a 32-channel scene with seven linked pairs converts to 25 Wing channels. The odd, left-hand channel's name, colour and icon are the ones that carry.

Will it overwrite the rest of my Wing?

No. The output is a partial snapshot, so it merges into the desk and leaves anything it doesn't contain untouched. It's still worth initialising the console first if you want a clean starting point, and you should always check the result before a show.

Are my scene files uploaded anywhere?

No. The conversion runs entirely in your browser using the File API. The scene file is read into memory, converted, and handed back as a download. Nothing is sent to a server and nothing is stored.

Why are the channel colours different from other X32 to Wing converters?

Because the two consoles use unrelated colour palettes. The X32 has eight colours plus inverted variants; the Wing has eighteen entirely different ones. Passing the X32's colour index straight through lands a green channel on Wing colour 2 — which is blue. This converter matches colours by how they actually look, so an X32 green becomes the Wing's green.