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)

Searching Database…

201 ·GitHub
Procedural-sounds
这是什么？Procedural Sounds 在浏览器中用代码配方实时生成界面和 UI 音效，而不是依赖音频文件，因此你可以凭听觉设计一个声音，然后导出它。
这是供下载的音效库，还是我自己运行的工具？它是你自己运行的 Next.js 网页应用：一个用于生成和导出音效的公开产品页面，外加一个仅在本地运行时才存在的、用于策划音效库的开发者专属“工作台”。
怎么把它跑起来？用 Node 24（Next 16、React 19、Tailwind 4）在本地运行，然后打开 '/' 的产品页面；页面底部有一个开发模式链接，可打开策划工作台。
要真正做出一个声音我需要什么？不需要额外的东西：选一个分类，反复生成直到某个声音合适，在场景中试听，然后把它导出为 WAV 文件或几行 JavaScript。
我能直接 npm install 到自己的项目里吗？还不能——目前使用声音的唯一方式是从运行中的应用导出，而提供可导入的 npm 包被明确列为最大的缺失项。整个项目仍处于早期 beta 阶段。
声音生成实际是怎么工作的？一个手工策划的音效库供给少数几个生成器进行混搭，学习层则在策划者每次在工作台保留或删除生成结果时调整各生成器的胜出概率。
在工作台里我能做什么？Variations、Creations、Invent、Wild、Craft、Prospect 等标签页批量生成声音供保留或删除，Library、Editor、Calibrate、Atlas、Dedupe 和 Trash 则负责整理、手写配方、听力安全校准和清理。
这个合成引擎是怎么来的？合成核心最初改编自一个开源的配方播放器，最早的声音库也由几个开源音效包奠基；此后生成、学习和策划的一切都是本项目原创。
这个项目到底定名了吗？没有——README 声明尚未确定名称，并通过 issue 征集命名想法。
What are similar projects?tweakcn, orb, procedural-film, ScrollMagic, openreel-video, onlook, 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