How Chronkle measures your timing

What the numbers mean, how they're worked out, and where they stop.

Every Chronkle game ends with some kind of score. Before you read too much into one, here's the honest frame: each result is an informal, on-device estimate of how you did on that task, right then, on that hardware. It's a practice tool giving you feedback, not a clinical measurement of your rhythmic ability. Keep that in mind and the numbers become genuinely useful. Treat them as lab results and they'll mislead you.

The one caveat that changes everything: device latency

Start here, because it colours the rest. When you tap or press a key, there's a delay before your input reaches the game, and another delay before a sound actually leaves your speaker. Bluetooth headphones add a big chunk. So do slower browsers, busy phones, and cheap audio paths. This lag can run anywhere from a few milliseconds to well over a hundred, and it varies by setup.

Chronkle can't see that delay, so it can't subtract it. What this means in practice: your absolute numbers aren't comparable across devices. A threshold that reads as 4% of a beat on a wired laptop might read worse on a phone with Bluetooth earbuds, even if your timing is identical. Don't compare your score to a friend's on different hardware, and don't compare your own scores across a device switch. The fix is simple: stay on one setup and watch how you change over time on that setup.

What the games actually measure

Chronkle's games fall into a handful of families, each probing a different piece of timing. They borrow their logic from tasks used in perception research, adapted into something you can finish in about a minute.

The units, and how scoring works in principle

Different families call for different yardsticks. A detection game reports a threshold: the smallest percentage difference between two tempos that you handled reliably. Because timing perception roughly follows Weber's law, expressing this as a percentage of the beat makes more sense than milliseconds, and it lets slow and fast tempos share one scale. Production and reproduction games report closeness to a target, often as how far off you were as a share of the beat. Zone-holding games report time in the zone. And several games track a streak, the run of correct calls before your first clear miss.

The scoring idea underneath most of them is the same. The game nudges the difficulty toward the edge of what you can do, then reads off where that edge falls. In a detection game, it makes the two tempos closer when you're right and further apart when you're wrong, homing in on the smallest gap you can still catch. That converged gap is your threshold for the session. In a production or interpolation game, the score is just how near you landed to the correct answer. There's no curve grading you against other players. It's you against the task.

Game familyWhat it estimatesRough unit
Detection (JND)Smallest tempo or interval difference you can reliably tell apartThreshold, as % of the beat
ProductionHow close your tapped tempo is to a targetBPM closeness, or % off
Reproduction from memoryHow well you hold a tempo or pattern once it stops% drift from the original
OrderingWhether you can rank tempos or durations correctlyCorrect placements, streak
InterpolationWhether you can find a value between two anchors% off from the midpoint
Real-time controlHow long you keep a drifting target lockedTime in zone

Difficulty adapts to you

Most games don't sit at a fixed level. They watch how you're doing and adjust: get several right and the task tightens, slip and it eases back. That keeps you near the boundary of your ability, which is both where practice pays off most and where the measurement is most informative. It also means the game meets a first-timer and a trained musician at their own edges rather than boring one and crushing the other. The flip side is worth stating plainly. Because the difficulty moved to find your edge, the final number reflects that adaptive search, not a single fixed test everyone takes identically.

What a score does not mean

Being clear about the limits is the point of this page. A Chronkle result is not a diagnosis of anything, and it isn't a clinical or hearing test. If you're worried about your hearing or a timing-related condition, see a professional. It also isn't a fixed verdict on your ability. Any single session is noisy. Sleep, caffeine, focus, the room, and that device latency all push a result around. One low score doesn't mean you're bad at timing, and one great score doesn't mean you've arrived. Your "true" ability is not a number you got on a Tuesday.

How to read repeated measurements

This is where the tool earns its keep. Don't fixate on today's number. Play on a regular schedule, keep the same device, and watch the trend across days and weeks. A single point tells you almost nothing; a line sloping the right way over a couple of weeks tells you a lot. Expect wobble from day to day even as you improve, and judge progress by the direction of the cloud of points, not by whether today beat yesterday. If you want the deeper theory behind the percentage-of-beat thresholds, the guide on tempo JND and Weber's law goes into it, and the broader picture lives in the complete guide to tempo and timing perception.

More about the project