The plugin is the flexible one.
The web version is deliberately narrow: one file in, one file out, nothing kept. The plugin runs inside your session, on every track, in real time, with every parameter automatable — and because it runs on your machine, it can afford to keep things.
Compiled binaries for macOS, Windows and Linux. Every build is produced by CI from the source in this repository, and each platform runs the compiled-plugin test suite before it is packaged — a red run ships nothing.
| macOS — universal (Apple Silicon + Intel) | VST3 · Audio Unit · Standalone |
| Windows x64 | VST3 · Standalone |
| Linux x64 | VST3 · Standalone |
INSTALL.md in the download explains how to clear the quarantine flag. If you would rather not run an unsigned binary on your master bus, which is a reasonable position, the source builds in one command:cd plugin cmake -B build -DCMAKE_BUILD_TYPE=Release cmake --build build --config Release --parallel
- Runs live on any track, at real-time latency, on unlimited instances
- Six bands, each with its own engine, all host-automatable
- A different device per band — low end on one voicing, top end on another
- Every parameter automatable, including the per-band device choice
- Your DAW’s timeline replaces the web version’s region editor
- Copies of every export, filed with the settings that made it
- Rolling backups of your last three processings, restorable from the editor
- Linear-phase crossovers — non-causal, so only possible offline
- Deeper transient control: reading the gain curve arbitrarily far ahead costs nothing offline, where a plugin can only look ahead as far as it delays
- True A/B: several devices rendered at once and switched sample-aligned
- Automatic loudness matching across every version you are comparing
- Nothing to install, and nothing kept afterwards
The device table in the plugin is a transcription of the one the web engine uses, value for value. A chain you dial in here sounds like the same chain there — the differences between the two are the ones real-time forces, and they are listed above rather than hidden.
| macOS | ~/Library/Application Support/multiTransBender/ |
| Windows | %APPDATA%\multiTransBender\ |
| Linux | ~/.config/multiTransBender/ |
backups/ holds the last three states. exports/ holds a dated copy of each render next to the settings that produced it. Nothing in either folder is ever transmitted.