8000 GitHub - joacod/audiobits: Procedural sound effects for the web · GitHub
[go: up one dir, main page]

Skip to content
joacodPublic

Latest commit

 

History

170 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

AudioBits: Sound that reacts. Procedural sound effects for the web, with a colorful waveform crossing bold white lettering on a black background.

npm version CI status on main MIT license

AudioBits is a framework-independent, browser-native procedural audio library with zero runtime dependencies. Generate sound effects from editable recipes, copy catalog sounds, and connect sound parameters to application state. No required audio files.

Live catalog · Documentation · Agents (Skill) · MCP server (optional) · npm · Catalog source

Quick start

Install in a browser application with a bundler:

npm install audiobits

Or install a ready-made sound from the catalog:

npx shadcn@latest add joacod/audiobits/<item>

See the documentation and the package README for the full example.

Use with coding agents

Install the official AudioBits Skill:

npx skills add joacod/audiobits --skill audiobits

The Skill includes an optional MCP server. See the agents guide and MCP docs.

Explore AudioBits

Recipes you own

Copy or install ready-to-use recipes from the source registry, import their local files, preview them in the live catalog, and adjust supported parameters and seeds. Use them as starting points for your own sounds. See the recipe guide for editable, versioned recipe data.

Interactive examples

Energy Charge, Reactive Thruster, and Lightsaber demonstrate sound driven by application state and events. Install their reusable sound controllers through the source registry and connect your existing controls. The showcases' visuals and input adapters remain separate.

The npm package owns the engine and recipe language. Recipes and interactive examples are copy-owned application source.

Why AudioBits?

  • Procedural by design. Generate effects in the browser without managing prerecorded audio assets.
  • Responsive to state. Update supported live parameters as an interaction changes.
  • Portable recipes. Edit and share versioned JSON sound definitions.
  • Framework-independent. Zero runtime dependencies.

Learn more

MIT license, with 0BSD catalog source.

Releases

Sponsor this project

Contributors

Languages

0