I’ve been working on a development environment for experimenting with DSP algorithms for synthesizers and audio effects.
The project is called dsplab. It’s a browser-based DSP lab built around the Vult language. The idea is to prototype oscillators, filters, envelopes, and other audio algorithms without having to build a plugin or embedded firmware project first.
You write DSP code in Vult and run it in an isolated AudioWorklet engine. The environment includes a set of tools for inspecting signals and internal state while the algorithm is running.
Currently it includes things like:
* dual-trace oscilloscope
* logarithmic spectrum analyzer
* logic analyzer for inspecting internal variables
* telemetry viewer for real-time parameter data
* signal generators and a small sequencer for testing patches
There is also an integrated LLM agent that can work on the DSP code. It can read compiler errors, write or modify functions, fix broken code, and iterate on implementations while observing telemetry and spectrum data from the running algorithm. The idea is that it can autonomously try improvements or fixes until the code compiles and behaves as expected.
The main goal is to use this as a sandbox for DSP ideas before moving them into hardware projects.
When an algorithm is finished it can be exported as C++ suitable for embedded targets such as Teensy, Daisy, or custom audio hardware.
Still evolving, but I’d be interested in feedback from people working on synths, plugins, or embedded audio DSP.
The project is called dsplab. It’s a browser-based DSP lab built around the Vult language. The idea is to prototype oscillators, filters, envelopes, and other audio algorithms without having to build a plugin or embedded firmware project first.
You write DSP code in Vult and run it in an isolated AudioWorklet engine. The environment includes a set of tools for inspecting signals and internal state while the algorithm is running.
Currently it includes things like:
* dual-trace oscilloscope
* logarithmic spectrum analyzer
* logic analyzer for inspecting internal variables
* telemetry viewer for real-time parameter data
* signal generators and a small sequencer for testing patches
There is also an integrated LLM agent that can work on the DSP code. It can read compiler errors, write or modify functions, fix broken code, and iterate on implementations while observing telemetry and spectrum data from the running algorithm. The idea is that it can autonomously try improvements or fixes until the code compiles and behaves as expected.
The main goal is to use this as a sandbox for DSP ideas before moving them into hardware projects.
When an algorithm is finished it can be exported as C++ suitable for embedded targets such as Teensy, Daisy, or custom audio hardware.
Still evolving, but I’d be interested in feedback from people working on synths, plugins, or embedded audio DSP.