Overview
Audiorective is a modular toolkit for Web Audio applications. Use it to build instruments, sequencers, spatial scenes, visualizers, and audio tools.
The audio engine owns its state. Your interfaces observe parameters, change values, and call methods. React components and canvas or 3D views can control the same engine without separate copies of that state.
Choose your packages
| Package | What it provides |
|---|---|
| Core | Reactive parameters and cells, processors, playback, analysis, spatial audio, and graph routing |
| Clock | Transport, tempo automation, scheduling windows, and beat/bar/time rulers |
| Effects | Filters, delay, reverb, distortion, modulation, pitch shifting, dynamics, channel strips, and send buses |
| React | Hooks and an engine context for reactive interfaces |
| Three.js | A shared audio context and spatial sound that follows scene objects |
| PlayCanvas | Engine integration and entity-to-panner bindings |
| Devtools | Processor latency measurement and assertions |
PixiJS uses core directly; it does not need a dedicated binding package. Other imperative interfaces can also observe and change the engine’s state.
Playback and sound
Choose a source for the job:
- Sampler plays polyphonic one-shots, with per-voice fades, reverse playback, and mute controls.
- BufferPlayer plays in-memory loops and stems with sample-accurate scheduling and a schedulable playback rate.
- FilePlayer streams longer tracks with play, pause, and seek.
- AudioProcessor is the base for your own instruments and effects.
Route sources through effects, add a Spatial processor for positional sound, and use Analyser for waveform or frequency data. See Choosing Playback.
Timing and automation
Use the clock for transport and look-ahead scheduling. Rulers express positions as bars, beats, cycles, or seconds. Tempo supports scheduled changes and ramps.
Audio parameters use the Web Audio .value and scheduling conventions. Native-backed parameters delegate automation to the audio thread and update reactive values for the interface. See Clock and Core.
Routing, latency, and offline rendering
defineGraph connects processors from a reactive list of edges. When the graph changes, it updates the connections and compensates unequal processing latency where paths join.
Use renderOffline for a graph or renderTimeline for clock-driven audio. Both let you render audio without real-time playback. Devtools checks whether a processor’s measured latency matches its declared latency.
Start building
Follow Get Started for a runnable sound, or Installation to choose packages. The showroom contains working examples and source links.
Audiorective’s audio engine runs in the browser. For Astro, Next.js, or other server-rendered frameworks, keep audio code behind a client-only boundary.