Updated October 2026
This tool's rate and beat-error math is only as good as the ticks it's able to cleanly detect. A noisy room, a watch held too far from the mic, or a capture stopped too early all degrade the result in predictable ways — here's how to avoid each one.
The highpass filter and adaptive threshold (see how this works) do real work to separate the tick from background noise, but they aren't magic — a loud HVAC vent, a running dishwasher, music, or conversation in the room all raise the noise floor the adaptive threshold has to climb above, which can suppress quieter ticks or, in bad cases, cause the threshold to miss them in the trailing-window statistics entirely. A quiet room is the single highest-leverage thing you can control.
Sound intensity falls off quickly with distance through open air, and the tick's energy at 2000Hz and above (the frequency band the highpass filter preserves) attenuates faster over distance than lower frequencies do. Holding the case back within an inch or two of your phone or laptop's microphone gives the clearest possible signal for the envelope follower and onset detector to work with.
Any handling noise — fingers shifting grip, the watch tapping against something, even fabric brushing the case — produces its own transient clicks that can register as false onsets, polluting the interval data the outlier-rejection step then has to filter back out. Set the watch down on a soft, non-vibrating surface near the mic, or hold it steady with minimal grip adjustment during the capture, rather than holding it in a moving hand.
The tool automatically captures for 15 seconds once you click "Start Listening." It's tempting to stop early once you see ticks registering, but more detected ticks means the final averaging in analyzeTicks() has more data to work with, which meaningfully steadies the rate number — a handful of ticks can show noisy, scattered timing even from a perfectly healthy watch, purely from measurement variance, while dozens of ticks average that noise out.
An easy mistake that looks like a capture-quality problem but isn't: selecting the wrong beat rate for your specific watch. See what is beat rate (bph) for how to find the right value — a wrong selection produces a wildly implausible rate number regardless of how clean your capture was.
Real mechanical watches genuinely vary their rate somewhat by position — dial up, crown up, crown down — due to how gravity interacts with the balance wheel and escapement in each orientation. This is a normal mechanical characteristic, not a measurement error. See testing positions for a full guide; testing two or three positions and looking at the spread gives you a much more complete picture than any single reading.
If you've done all of the above and still get this message, there's a dedicated troubleshooting page for it — see not enough ticks detected: troubleshooting, which walks through the two distinct underlying causes and how to tell them apart.
Even under ideal conditions, this tool is measuring through an everyday, uncalibrated microphone, not a purpose-built sensor. A single capture is a reasonable estimate; a few captures, in a quiet room, with the watch close and still, and averaged by eye, is meaningfully more trustworthy than treating any one number as definitive.
Does the type of surface I set the watch on matter? Yes, somewhat — a hard surface can transmit some vibration noise; a soft but non-absorbing surface (like a folded cloth) near the mic tends to work well without muffling the tick itself.
Will a case with a loud movement (like some chronograph calibers) read differently? Louder ticks generally help the adaptive threshold trigger more reliably, so if anything a naturally louder movement tends to produce an easier, cleaner capture.
Should I remove the watch from my wrist to test it? Not required, but holding it steady and close to the mic is easier off-wrist; either works as long as it stays still and close during the capture.