kunitoki/sonic-skills / skills/webaudio-guide
webaudio-guide
UnverifiedStep-by-step guide for building Web Audio processing pipelines — AudioWorklet processors, custom nodes, parameter automation, and WebMIDI integration. Use when the user asks how to build or wire up Web Audio code from scratch. Trigger on phrases like "build an AudioWorklet", "create a custom Web Audio effect", "how do I use WebMIDI", "how do I write an AudioWorkletProcessor", or "how do I connect AudioNodes".
Web Audio Processing Guide
Step 1 — Set up AudioContext and load worklet module
- Create
AudioContextinside a user gesture handler (click, keydown) to satisfy autoplay policy. - Call
await audioContext.audioWorklet.addModule('path/to/processor.js')before creating nodes. - The module path is resolved relative to the page; bundlers may require special config (e.g. Vite's
?worker&urlimport). - Check
audioContext.stateand callaudioContext.resume()if it is'suspended'.
Step 2 — Write the AudioWorkletProcessor
- Subclass
AudioWorkletProcessorin a separate file; callregisterProcessor('name', Class)at module scope. - Implement
process(inputs, outputs, parameters)—inputs[n][channel]andoutputs[n][channel]areFloat32Arrayviews for the current render quantum. Use.lengthin loops instead of hardcoding 128. - Pre-allocate all working buffers in
constructor(); never create objects or arrays insideprocess(). - Declare custom
AudioParams viastatic get parameterDescriptors()returning an array of{ name, defaultValue, minValue, maxValue, automationRate }descriptors. - Return
truefromprocess()to keep the processor alive;falseor no return shuts it down.
Step 3 — Wire up the node graph
- Instantiate the node on the main thread:
new AudioWorkletNode(ctx, 'name', options). - Use
node.connect(destination)andsource.connect(node)to build the signal path;AudioContext.destinationis the hardware output. - Access
AudioParams vianode.parameters.get('paramName')— set.valuefor immediate changes. - Schedule smooth automation with
.linearRampToValueAtTime(),.setTargetAtTime(), or.setValueCurveAtTime()on theAudioParam. - Tear down cleanly:
node.disconnect(), thensource.stop(), thenaudioContext.close().
Step 4 — Worklet ↔ main thread communication
- Use
this.port.postMessage()/node.port.onmessagefor low-frequency control (meters, state changes, error reporting). - Batch postMessage calls; avoid sending one per render quantum (currently ~344/sec at 44.1 kHz with 128-frame quanta).
- For high-frequency or low-latency control (e.g. live gain, pitch), share a
SharedArrayBufferand read/write integer views withAtomics.load()/Atomics.store(). Scale floats to integers or bit-cast through a private buffer;Atomicsdoes not operate onFloat32Array. - Cross-origin isolation (
COOP: same-origin+COEP: require-corpresponse headers) is required forSharedArrayBuffer.
Step 5 — WebMIDI integration
- Request access with
await navigator.requestMIDIAccess({ sysex: false }); handle theMIDIAccessobject on success. - Enumerate inputs via
midiAccess.inputs.forEach(input => ...)and attachinput.onmidimessage = handler. - Parse the
MIDIMessageEvent.databyte array:data[0] & 0xF0= status (0x90 = note on, 0xB0 = CC, 0xE0 = pitch bend),data[1]= note/CC number,data[2]= velocity/value. - Map MIDI values to
AudioParamtargets: normalize 7-bit CC (0–127) to your parameter range and write via.setTargetAtTime()or aSharedArrayBuffercell for real-time feel.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |