What it does
A show file goes in, a console-neutral model comes out, and from that model come the three documents a patch actually needs: who is plugged into what, what the rig is, and how it is wired. Behringer X32/M32, Yamaha DM3/DM7/TF and CL/QL, and Allen & Heath Avantis/dLive and SQ are read today; DiGiCo and Avid VENUE are planned.
The browser build parses and renders entirely in WebAssembly, so a show file never leaves the machine — there is no upload and no server. That matters because show files are client data.
The hard part is that the patch chain has an indirection in the middle and every console has one. On an X32 a connector reaches a routing block, then an input slot, then a channel's source — so assuming channel N is fed by connector N produces a patch list that is confident and wrong. The model keeps the slot, the socket and the strip on every patch rather than collapsing them.
- Patch list, specification sheet and wiring topology as PDFs
- Console-neutral PFX model, plus PFX interchange XML
- Behringer X32 / Midas M32 / X-Air .scn — supported
- Yamaha DM3 / DM7 / TF and CL / QL — input patch and names
- Allen & Heath Avantis / dLive and SQ — input patch and strip inventory
- Browser build runs in WebAssembly: nothing is uploaded
Where it stands
An early preview and still very much in development. The X32 adapter is written against a real 2,104-line scene file saved by an actual console and asserted against it in CI. No output has ever been loaded back into a console, no conversion between consoles exists yet, and the Yamaha MMS patch-source encoding has never been confirmed against a console's patch screen — on TF no connector resolves at all, and the tool says so rather than guessing. Verify anything it prints against the desk before trusting it on a show.