Rust VSTi
Playground

Learn the Stack

Why Rust + WASM for audio?

Rust is a good fit for predictable DSP code, explicit memory control, and sharing one engine across browser and native targets.

The browser shell can stay lightweight while the hot DSP path moves into a cached .wasm binary over time.

How the browser graph stays stable

Transport only starts after a user gesture
AnalyserNode powers the scope and spectrum
Delay and filter chains make sketching effects fast
WASM manifest probing shows whether the Rust build is active

Why iPhone can still be silent

Mobile Safari can allow the page to start correctly while system Silent Mode still suppresses Web Audio output.

If the UI responds but you hear nothing on iPhone or iPad, disable Silent Mode and confirm the hardware volume is up before assuming the graph or wasm engine failed.

Public-hosting contract

The source repo owns the implementation. The personal website only imports the generated artifact under /explorations/rust-vsti-playground/app/.

That keeps the public site fast, cacheable, and free of the source repo itself.

First exploration ideas

Instrument voices that start as Web Audio node graphs
Rust-generated modulation tables and envelope shapes
WASM-backed sample mangling and loop slicing
Visual traces of audio motion for lightweight hosted demos

Specs & Resources

MDN Web Audio API Web Audio Spec Rust and WebAssembly Book Audio Worklet Guide

Web Audio + Rust/WASM

Rust VSTi Playground

Select an experiment, then start audio to hear the current patch.

On iPhone and iPad, system Silent Mode can suppress Web Audio output even after you tap Start Audio. If you hear nothing, turn Silent Mode off and raise the device volume.

Rust VSTi Playground

Engine status

Parameters

Experiment notes