A 750-millisecond quarter-note pulse
Press Start for an 80 BPM click. Quarter-note beats are exactly 750 milliseconds apart. The control starts at 80 and remains adjustable for a slower count or a faster rehearsal pass.
Compare every interval
At 80 BPM, consecutive taps centered on the beat should be about 750 milliseconds apart. The recent-interval row keeps individual gaps visible beside the average.
The quarter-note interval is 60,000 milliseconds divided by 80 beats, which equals 750 milliseconds. The other rows below multiply or divide that base interval, so their arithmetic remains visible.
| Click value | Interval | Calculation from 80 BPM |
|---|---|---|
| Half note | 1,500 ms | 750 × 2 |
| Dotted quarter | 1,125 ms | 750 × 1.5 |
| Quarter note | 750 ms | 60,000 ÷ 80 |
| Eighth note | 375 ms | 750 ÷ 2 |
| Eighth-note triplet | 250 ms | 750 ÷ 3 |
| Sixteenth note | 187.5 ms | 750 ÷ 4 |
In 4/4, two full bars contain eight quarter-note intervals when you count from the first downbeat to the next downbeat after bar two. Eight intervals multiplied by 750 milliseconds equal 6,000 milliseconds, or six seconds.
A wall clock is only a rough playback comparison. Browser scheduling, the audio device, and the speaker each affect when the sound reaches you.
The quarter-note layer schedules 80 ÷ 60, or about 1.333 beat events per second. Eighth notes double the audible rate to about 2.667 clicks per second. Triplets produce exactly four clicks per second because each 750-millisecond beat is divided into three 250-millisecond gaps.
Use the triplet layer when you need three equal positions inside each beat, then return to quarter notes without touching the 80 BPM field. The added clicks change the guide density, not the underlying beat rate.
One quarter-note beat lasts 750 milliseconds because 60,000 milliseconds ÷ 80 beats = 750.
Four quarter-note intervals take three seconds: 4 × 750 milliseconds = 3,000 milliseconds.
No. Eighth notes add a click every 375 milliseconds while the quarter-note pulse remains 80 BPM.
Browsers normally require a user action before starting or resuming an audio context. The Start button activates the local clock used for the click schedule.
The interval, event-rate and bar-duration values above are transparent calculations from a selected 80 BPM value. They do not measure a performance, certify speaker latency, or prove that a recording remains at 80 BPM. Use the tap panel for your own input gaps and the BPM Finder for a browser estimate from a selected audio file.
Scheduling reference: BaseAudioContext.currentTime.
The click generator and tap timing run locally in this browser. No tapping data is uploaded.