Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Build or repair [small metronome or step sequencer] with [bounded tempo range and pattern length] using the existing audio setup. Define the audio-clock schedule, the short scheduling horizon, and the relationship between scheduled notes and the visual playhead. Keep UI frame timing separate from note deadlines.
Specify what tempo changes, Stop, Restart, and context suspension do to already scheduled sound and future events. Keep track of sources or scheduled work so restarting does not stack a second sequence. Handle late scheduler wakeups according to an explicit policy instead of silently accumulating drift.
Verify a fixed pattern, a tempo change, repeated start/stop, a controlled busy-interface interval, and resume after interruption. Use modest test volume. Report timing observations and test conditions; do not describe a JavaScript timer callback as a guarantee of sample-accurate audio output.Make this prompt yours
Start with a short synthetic pattern. Device output latency and browser scheduling limits remain part of the test context.
You might also hear
- Web Audio
- lookahead scheduler
- metronome
- sequencer
- audio clock
- tempo change
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Research sources reviewed .
Editorial review · October 28, 2026
Supported: Original sequencer template. MDN schedules audio with AudioContext currentTime and a lookahead horizon while drawing separately. Timer wakeups and output latency are correctly not promised to be sample-accurate.