Skip to content
AbilityBench

Paced, then unpaced

Rhythm test — how steady is it once the beat stops?

Tap along with a click, then carry on at the same interval after the click stops — under a minute a run, at one of four tempos between 75 and 150 BPM. What comes back is the spread of your timing, not a mark out of ten, and for the unpaced half the interval you kept with nothing to correct against, its drift, and its variability split into the clock and the finger.

  • 4 tempos
  • Spread in ms
  • Latency stated, not hidden

4 clicks to count you in, 24 to tap along with, and then silence for 24 more taps that you keep going on your own. Space, or the pad on screen. About 26 seconds.

Hear the click before you commit to a minute of it

Four clicks at the tempo you picked, at the level the run will use. A click has to be short and sharp to be worth timing against — this one is 30 ms of 1200 Hz square wave — so if yours sounds like a thud rather than a tick, the output path is smearing it and every asynchrony below will be wider than it should be.

Tempo

All four are well above the roughly 200 ms interval below which tapping stops being synchronization and becomes a burst, and the spread is reported as a share of the interval so the four are comparable.

Taps per phase

The short run exists to be tried, not to be quoted: a standard deviation from 12 taps carries roughly a fifth of its own value as uncertainty, and the unpaced split below needs the longer one to mean much.

Exactly what is measured

Beat
30 ms of 1200 Hz square wave, every 500 ms
Phases
4 count-in clicks, 24 clicks to tap with, then 24 taps with no click
Matching
each tap goes to the nearest click, not to the next one in line, so one missed tap does not shift every asynchrony after it
Dropped
a tap within 25% of an interval after the last one, a tap during the count-in, and any unpaced interval outside 40%-210% of the target
Reported
the spread of your asynchrony, the average step between consecutive asynchronies, the spread as a share of the interval, the drift after the beat stops, and the two-part split of the unpaced run
Not reported
any judgment of whether you have rhythm. There is no pass mark on this page and no percentile

Nothing is scored during the 4 count-in clicks; tap on any of them and the tap is counted as early and dropped. Space is captured while the run is going so the page does not scroll under you — the stop control on screen stays reachable by pointer.

Why the headline is a spread and not an offset

A browser adds two delays to this measurement that it cannot know to the millisecond: the audio path holds the click back after the page schedules it, and the input path holds your keypress back before the page sees it. A human offset sits on top of both — tappers land ahead of the beat, by 20-60 ms in Repp (2005), Sensorimotor synchronization: a review of the tapping literature, Psychonomic Bulletin & Review, less with musical training. Add the three and an average asynchrony is mostly a number about a laptop. The standard deviation ignores all of them: a constant added to every tap moves the mean and leaves the spread exactly where it was. The page still prints the output latency the browser reports, because a floor that is stated can be argued with.

The clicks are thirty milliseconds of a 1200 Hz square wave, with the count-in accented at 1800 Hz — a short, bright onset is something a finger can aim at, and a soft click widens every figure on the page. All of them are scheduled up front on the audio hardware’s own clock rather than fired from a timer, since a browser timer wobbles by the same order as the quantity being measured. Each tap is matched to its nearest click, so one missed tap does not shift the rest; a tap within a quarter of an interval of the last is read as a bounced key, and a continuation interval outside 40 to 210% of the target as a missed or doubled tap. All three are counted and named.

When the clicks stop

While the metronome plays, two things run at once: a timekeeper producing intervals and a correction process nudging each tap toward the click. Take the click away and correction has nothing to work with, so the intervals that keep coming are the timekeeper’s own. They drift, and the result reports the drift and the average interval against the target. Timing variability grows with the interval being timed — the smallest change in an interval people can detect is 5-10% of it, per Grondin (2010), Timing and time perception: a review of recent behavioral and neuroscience findings — so the spread is also given as a share of the interval, which makes the four tempos comparable.

The clock-and-finger split follows Wing and Kristofferson’s 1973 model: a tap happens when an internal interval runs out, plus a motor delay, and the two noises are independent. A motor delay that runs long shortens one interval and lengthens the next, so neighboring intervals should be negatively correlated — and the size of that correlation gives the motor part, with the remainder belonging to the clock. When the correlation comes out positive, the model has failed for that run, usually because the run drifted, and the page says so instead of taking the square root of a negative variance.

This is a measurement exercise, not a clinical assessment. It reports what you did on this page against a stated reference and nothing more — it cannot establish a timing or movement disorder. Only a qualified professional, working with more than a browser, can make that judgment.

Every figure here describes one run on one machine, and the machine is inside the number: a slow keyboard scan, a large audio buffer or a click too quiet to give the ear a sharp target each widen a spread that other hardware would call narrow. The comparison worth making is between two of your own runs, taken the same way.

Questions after a run

Why is my average asynchrony negative — am I rushing?

No. Tapping slightly ahead of the beat is the normal finding — 20-60 ms in Repp (2005), Sensorimotor synchronization: a review of the tapping literature, Psychonomic Bulletin & Review — and it shrinks with musical training rather than disappearing. The usual explanation is that the brain lines up the feel of the tap with the sound of the click, and the feedback from a fingertip takes longer to arrive than a sound does, so the movement starts early. On this page the browser's own delays are added to your value too, which is why it is reported small and the spread large.

Does tapping on the screen instead of the keyboard change the numbers?

It moves the average and barely touches the spread. A tap on the pad has to travel to a target, so it lands later than a resting finger's keypress by a fairly constant amount, and a constant is invisible to a standard deviation. Aiming does add a little variability of its own, so a run taken half on the pad and half on Space comes out slightly wider than either alone, and the result says how many taps arrived each way.

Why not measure rhythm with a microphone, by clapping?

This site opens no microphone anywhere, and clapping would make this measurement worse rather than better. A clap's onset is a broad sound a detector has to threshold, and where the threshold sits moves every asynchrony by an amount that depends on how hard you clapped. A key or a tap is one timestamped event with nothing to interpret in between.