Supported presets
The Waveroom Mastering engine has been adapted for the web. Natural, Warm / Analog and Loud use it on desktops with memory headroom. Phones, long tracks and Reference retain the existing processing path.
A shared DSP core
The desktop plugin's C++ processing code is compiled to WebAssembly. Automatic settings and output stages can produce different results.
Processing on your device
Audio is processed locally. Processing time depends on track length, sample rate and device performance.
Memory-aware processing
Phones and long tracks use in-place processing to reduce extra copies. Audio buffers and the browser need memory in addition to the engine.
A familiar workflow
Master your track, compare with the original, then adjust it with Fine Tune.
Safe recovery
If the new engine cannot start or fails before changing the original, the existing processing path takes over. If a single-track job fails after changing its source buffer, the file is decoded again for one light-path retry. Outputs that fail delivery checks are not returned.
Frequently asked questions
Will saved files change?
No. Saved files stay as they are. Mastering a track again creates a new result.
Is the output identical to the plugin?
The DSP core is shared, but automatic settings, decoding and output stages can affect level and other details.
Does the workflow change?
Original comparison, Fine Tune, existing exports and pass entitlements are retained.