Audio processing
Planar audio, sample-timed events, smoothing, prepared graphs, filters, FFT and convolution. Keep preparation separate from the processing callback.
A framework for audio plug-ins and standalone applications. Portable processing, prepared DSP, state and visual tools — with explicit boundaries between your audio code and the host.
RAVET is in development. Repository access currently requires permission; the guides are available here.
Build on reusable components with prepared capacities, explicit ownership and deterministic tests. The feature catalogue records what is implemented, what is a prototype, and what still needs validation.
Planar audio, sample-timed events, smoothing, prepared graphs, filters, FFT and convolution. Keep preparation separate from the processing callback.
Parameters, observable state, presets, MIDI and OSC. Reusable primitives for connecting sound, automation and interface controls.
CLAP, VST3, AUv2, AAX and LV2 reference prototypes, plus explicit device adapters. Validation varies by format and platform.
The first example runs an offline stereo gain fixture, applies automation, and checks the output. It opens no audio device and installs no plug-in.
cargo run -p ravet-gain --lockedSearch hosted guides, explore the processing contracts, and check the scope of each integration before you build.
Set up Rust and Python, run the offline gain example, and check sample-timed automation against known output.
Then build the CLAP bundle, load it in the smoke host and validate it before trying a DAW. The guide also covers native editor checks and generating Rust API documentation.
See how portable DSP is separated from plug-in formats, audio devices and editors. Covers crate responsibilities, borrowed planar buffers, processor ownership and the prepare/process/reset lifecycle.
Follow the boundaries between the audio thread, control state and worker services, including where allocation is allowed and how adapters translate host data.
Browse DSP, graphs, parameters, presets, MIDI and OSC, file I/O and native integrations.
Each feature records its implementation status, current limits, source and test evidence. Distinguish reusable components from format prototypes and find the supporting guide for each capability.
Choose GPL-compliant use, or a separate commercial agreement for proprietary distribution when commercial licensing opens. Commercial revenue bands do not restrict GPL-compliant use.
Free commercial tier
Company revenue up to $50,000
Per developer / year
Company revenue above $50,000, up to $500,000
Per developer / year
Company revenue above $500,000
USD excluding applicable taxes. Paid licences include twelve months of updates and permanent commercial rights to versions received, on the final agreement's terms. Explore licensing ↗
Join the RAVET community for implementation questions, projects and feedback.