Slab Sounds #2

Hi @mrsarac

So here is how I made https://x.com/MGasperowicz/status/2108692059431342428?s=20

Tools

Slab, my OSS DAW with a JITed DSP engine: https://github.com/nooga/slab

(It sounds better than ad-hoc synths that Claude writes, that's the whole point of it)

Discord, if you're interested in chatting about it: https://discord.gg/AnF3TUwmzR

Process

Described in #1

Result

As seen on X https://x.com/MGasperowicz/status/2108692059431342428?s=20

The Slab project project is fully editable, looks like this in the DAW:

https://www.youtube.com/watch?v=1xElFLyGi88

I PRed you the python generator and the slab project file.

Slab utility

Making sounds: You can easily generate Slab files programmatically in any language - see slabkit bundled with Slab for example. The project also has production skills checked in. Slab renders audio headlessly using the exact same DSP chain as the GUI.

Slab as a source: You can read Slab files and sync to them - they contain all note and automation info visible in the above YT video so it's relatively easy to sync or render visualizations from those. Slab can also render each track separately when needed.

Since agents don't hear I gave them some tools to analyze and visualize audio (image below) - Claude uses these routinely to see how the project sounds, measure sonic energy in different bands etc. This data also lends itself to ad-hoc analysis in python.