procedural-sounds README

The project's README from github.com/m1ckc3s/procedural-sounds. As one markdown file: README.md.

Procedural interface sounds, with taste

This project does not have a settled name yet. Naming ideas are welcome, open an issue.

Every sound is synthesized live in the browser from a recipe. There are no audio files anywhere in the product. Pick a category, generate until one fits, hear it in context, export it as a WAV or as a few lines of JavaScript.

Where this is at

Early beta, and very much a work in progress. The core loop works: generate, hear it in context, export. The library is growing, the generators are learning, and a lot of what is here is the first version of itself. Do not read this repo as a finished project. Read it as one you can help build.

I am looking for help, and PRs are welcome. In rough order of how much they would matter:

CONTRIBUTING.md has the specifics, including how curation contributions get merged. docs/TODO.md is the live work list.

Run it

Node 24 (Next 16, React 19, Tailwind 4).

npm install
npm run dev

Open the product at /. At the bottom of the page there is a dev mode link. That is the workbench, and it only exists when you run locally: its routes write curation state to data/pool/*.json on your filesystem, and a production build closes them.

Inside the workbench you can:

Read docs/TRAINING.md before a curation session. It says what each tab's keep and delete actually write.

How it works

The short version: a hand-curated library, a handful of generators that draw from and remix it, and a learning layer that shifts each generator's odds every time a curator keeps or deletes what it made. The library and the training data are the same asset.

On provenance: the synth core began as an adaptation of an open source recipe player, and a several open source sound packs seeded the very first library. Everything that generates, learns and curates is original to this project, as are the instruments, figures and characters the generators draw from, and the library has been growing past its seeds ever since. The specific projects and their licenses are in THIRD-PARTY-NOTICES.md, also rendered at /licenses.

The long version lives in docs/:

License

MIT. See LICENSE.

procedural-sounds (m1ckc3s/procedural-sounds)

procedural-generation
Searching Database…

201 ·GitHub
Procedural-sounds
What is this?Procedural Sounds generates interface and UI sounds live in the browser from code recipes instead of audio files, so you design a sound by ear and then export it.
Is this a sound library I download, or a tool I run myself?It is a Next.js web app you run yourself: a public product page for generating and exporting sounds, plus a dev-only 'workbench' for curating the library that only exists when run locally.
How do I get it running?Run it locally with Node 24 (Next 16, React 19, Tailwind 4), then open the product page at '/'; a dev-mode link at the bottom of the page opens the curation workbench.
What do I need to actually get a sound out of it?Nothing extra: pick a category, generate until a sound fits, audition it in context, then export it as a WAV file or as a few lines of JavaScript.
Can I just npm install this into my own project?Not yet — the only way to use a sound today is to export it from the running app, and shipping an importable npm package is called out as the single biggest missing piece. The whole project is still early beta.
How does the sound generation actually work?A hand-curated library feeds a handful of generators that remix it, and a learning layer shifts each generator's odds every time a curator keeps or deletes what it produced in the workbench.
What can I do inside the workbench?Tabs like Variations, Creations, Invent, Wild, Craft and Prospect generate sounds in batches to keep or delete, while Library, Editor, Calibrate, Atlas, Dedupe and Trash cover sorting, hand-writing recipes, ear-safety calibration and cleanup.
Where did the synth engine come from?The synth core began as an adaptation of an open source recipe player, and several open source sound packs seeded the very first library; everything generated, learned and curated since is original to this project.
Does the project even have a settled name?No — the README states it does not have a settled name yet and invites naming ideas via an issue.
What are similar projects?tweakcn, orb, procedural-film, openreel-video, onlook, ScrollMagic, shapeshift, CHOMPI
Which topics is it in?synthesizer, web-audio, ux, procedural-generation, design-tools, creative-coding, tailwindcss, nextjs, audio, browser, ui, web-app
Creator
m1ckc3s
Size
1.2 MB
Stars
201
Updated
CommitAug 18
Age
2mo
Commits · 90 Days