🌿 New sprout. This tool is freshly built and still being tested against real ATEM exports — double-check anything that looks off before relying on it.
Mapping ATEM audio outputs without hunting through XML #
Routing audio inside Blackmagic's ATEM Software Control gets tedious fast once you're past a handful of MADI or AES/EBU sources — every output has to be checked by hand, and it's easy to lose track of which input is actually feeding which channel. This tool loads a full config export and gives you a filterable, sortable view of every output, plus a complete source-by-output matrix you can edit directly.
Drag a full config export onto the row above (audio routing only exists in a full export, not a macro-pool-only one — a macro-only file will just show an empty table, which is expected), or click Code to paste XML directly.
Reading the mapping table
Every column is one output, every row is one source — the filled radio button marks which source currently feeds that output. Clicking a different radio button updates the underlying XML immediately, and the textarea at the bottom reflects the change so you can copy it straight back into your production config. Use the output-type filter chips (MADI1, AUX1, AUX2, ...) to narrow the table down to a single bank of outputs before reassigning sources — auditing sixteen channels at a time is a lot easier than all ninety-six at once.
Exporting your changes
Once you're happy with the mapping, copy the contents of the XML textarea back into your ATEM configuration. A minimal output entry looks like this:
<Output id="1" name="Aux1 1/2" sourceId="2001" />Just make sure the sourceId matches one of the <Source> entries defined earlier in the same profile, or the ATEM software will reject the import.
Related tool
This shares its underlying parsing logic with the original ATEM Audio Mapping tool — the same reliable output/source matrix, just wired into the shared config-loading row (drag & drop, paste, and recent configs) used across the rest of this tool family.
Privacy
Parsing runs entirely in your browser — nothing is uploaded anywhere. That matters here specifically: ATEM configs can reveal production setups, camera names, and internal notes.