morphazoid WAX setup

Browser-powered plug-in

Morphazoid for WAX

The whole instrument catalog inside your DAW

AudioFusion WAX puts a browser inside a VST3 or Audio Unit plug-in. The Morphazoid WAX build adds host-aware MIDI, project state, transport, and playhead hooks while preserving the normal browser experience. WAX is required: this is not a standalone Morphazoid VST3 or Audio Unit.

Windows 10+ macOS 11+ Linux browser test only

Downloads

Required host

AudioFusion WAX

Download WAX for Windows or macOS. The free tier supports one custom page; licensed features include unlimited custom pages and native DAW preset recall.

Download WAX

Morphazoid files

Morphazoid repository

Download the repository ZIP and extract it. The ready-to-run web app is the included dist-wax folder.

DAW for testing

REAPER

WAX works in major VST3 and Audio Unit hosts. REAPER is a compact cross-platform option for the first instrument and state-recall test.

Download REAPER

Load the hosted WAX build

You do not need to download or serve Morphazoid for the first test. After WAX is installed, paste the hosted Chaotic FM address into its address bar.

Integrated pilot instrument:

https://blechdom.github.io/morphazoid/dist-wax/chaotic-fm.html

Open the complete WAX-ready catalog to browse every Morphazoid page.

Choose your platform

Windows

VST3 setup

  1. Install WAX for Windows using AudioFusion’s installer.
  2. Open your DAW and rescan VST3 plug-ins.
  3. Insert WAX Instrument on an instrument track.
  4. Paste the hosted Chaotic FM URL above into WAX’s address bar.
  5. Use the local-copy instructions below only if you need offline access.

If you need Python, use the official Windows installer and enable its PATH option.

macOS

Audio Unit or VST3 setup

  1. Install WAX for macOS using AudioFusion’s installer.
  2. Open Logic, REAPER, or another compatible DAW and rescan plug-ins.
  3. Insert the WAX instrument as an AU or VST3 instrument.
  4. Paste the hosted Chaotic FM URL above into WAX’s address bar.
  5. Use the local-copy instructions below only if you need offline access.

If python3 is unavailable, install it from the official macOS downloads.

Run Morphazoid offline from localhost

Serving the folder over localhost gives ES modules, AudioWorklets, and fetched assets a consistent origin. Keep the terminal open while WAX is using Morphazoid. Do not open an HTML file directly from disk: browser security rules can block modules and worklets.

Windows PowerShell

cd C:\path\to\morphazoid\dist-wax
py -m http.server 3436 --bind 127.0.0.1

macOS Terminal

cd /path/to/morphazoid/dist-wax
python3 -m http.server 3436 --bind 127.0.0.1

Paste this into WAX for the integrated pilot instrument:

http://127.0.0.1:3436/chaotic-fm.html

Use http://127.0.0.1:3436/ to start at the complete Morphazoid catalog.

Instrument, Audio FX, or MIDI FX?

Choose by what must enter and leave the plug-in. VST3 and Audio Unit are plug-in formats; Instrument, Audio FX, and MIDI FX are the three WAX routing roles. There is no separate “WAX VST” role.

WAX Instrument

Track MIDI → Morphazoid → audio. Use the page’s built-in synth, sampler, drums, or sonification. This is the normal choice for Chaotic FM, Shape, and most of the catalog.

WAX Audio FX

Track audio → Morphazoid processing → audio. Use for Graph Delay, microphone/file processors, and other pages that should hear the DAW track instead of generating the source themselves.

WAX MIDI FX

MIDI or host clock → Morphazoid → MIDI. Use a page’s MIDI-only output to play another instrument. Put it before an instrument in a compatible MIDI-FX chain, or route its track’s MIDI output to a separate instrument track.

Does this apply to every plug-in format?

Yes, the role choice is the same whether the host loads WAX as VST3 or, on macOS, Audio Unit. Windows and macOS are the officially published WAX platforms. Linux has no official WAX build, so a browser test or a Wine-hosted experiment is useful evidence, not a supported native plug-in result.

Find the wrapper for a Morphazoid page

“Recommended” is the page’s primary DAW role. “Also works” is useful when you deliberately want a different output, especially MIDI-only. Preview caveats identify pages that still need host-input or render validation before a serious session.

First test: Chaotic FM

  1. Open Chaotic FM in WAX Instrument.
  2. Arm the track and send MIDI notes from the DAW or a controller.
  3. Open WAX’s Debug Panel and confirm that it detects audio and MIDI.
  4. Confirm the instrument starts without pressing its browser Audio button.
  5. Change Depth, Carrier, Output, and an envelope control.
  6. Save, close, and reopen the DAW project; confirm the controls return.
  7. Close the plug-in editor while playing and listen for uninterrupted audio.
  8. Repeat at 44.1 and 48 kHz and try an offline render.

Chaotic FM remains the first fully bespoke instrument adapter. Every catalog instrument now also receives the WAX routing panel, complete MIDI message decoding, controller macros, program and pressure fallback maps, host play/stop/BPM/PPQ follow, and project-persisted routing settings. These broad mappings are intentionally a first pass; the catalog caveats identify pages whose native event timing still needs a page-specific pass.

Second test: silent MIDI output

  1. Insert WAX MIDI FX, then load Rubix or Algorithmic Sequencers.
  2. Open the page’s WAX panel and choose MIDI only.
  3. Select the host MIDI destination, a root note, division, channel, and gate.
  4. Place a software instrument after WAX, or route this track’s MIDI to another instrument track.
  5. Start REAPER and confirm the notes follow play, stop, BPM, PPQ position, seeks, and loops.
  6. Use REAPER’s MIDI logger or record the output; confirm stop and seek leave no hanging notes.
  7. Repeat with Audio + MIDI only in a wrapper whose fixed buses expose both outputs.

The MIDI companion pattern is deterministic and shaped by the page’s first mapped controls. Incoming MIDI is never echoed automatically. Timestamped MIDI lookahead follows the Web MIDI standard, but WAX timing through Linux bridging remains a host test rather than an officially supported guarantee.

What Linux can test

AudioFusion currently publishes WAX for Windows and macOS, not Linux. On Linux you can run Morphazoid in Chrome, test the generated WAX artifact, and run the complete automated suite. That verifies browser compatibility, but not WAX’s VST audio, host MIDI, or DataTree bridge.

npm run verify
npm run build:wax
python3 -m http.server 3436 --directory dist-wax --bind 127.0.0.1

WAX documentation

WAX is an AudioFusion product. Morphazoid is an independent web-instrument project and is not affiliated with or endorsed by AudioFusion.