Updated October 2026
This is the most common error message the tool produces, and it actually covers two different underlying situations in the code, with different causes and different fixes. Knowing which one you're hitting helps you fix it faster than just trying the same thing again.
The analysis step, analyzeTicks(), first checks whether at least 6 tick onsets were found in the whole capture before attempting any further math. If fewer than that were detected, you'll see: "Not enough clear ticks detected... Move the watch closer to the mic, reduce background noise, and try again." This means the adaptive-threshold onset detector (see how this works) simply never saw enough distinct peaks clear the threshold — almost always because the tick's signal-to-noise ratio in the capture was too low, not because of a math problem downstream.
Typical causes: the room was too noisy (the adaptive threshold's trailing-window statistics stayed elevated the whole capture, raising the bar for what counts as a peak); the watch was too far from the microphone (tick energy attenuated below the noise floor); or — less commonly — the watch had actually stopped running and wasn't ticking at all.
Fix: move to a quieter room, hold the watch within an inch or two of the mic, and confirm by ear that the watch is actually ticking before testing again. See the full accurate reading guide for the complete checklist.
If 6 or more onsets were found, the code moves on to computing intervals between them and filtering outliers (keeping only intervals within 0.5×-1.8× of the theoretical interval for your selected bph). If fewer than 5 intervals survive that filter, you'll see a different message: "Detected ticks were too irregular to analyze reliably. Try a quieter room and hold the watch steady near the mic." This means onsets were detected, but the timing between them was too inconsistent to trust — most of the gaps were either much shorter or much longer than a real tick interval should be.
Typical causes: handling noise (shifting grip, tapping, fabric contact) creating spurious extra onsets mixed in with real ticks, which produces a chaotic mix of very short and very long intervals once the real ticks and the noise onsets are interleaved; or an incorrect bph selection, which shifts the theoretical interval the 0.5×-1.8× window is centered on, causing otherwise-valid real tick intervals to fall outside that window and get discarded as "outliers" even though they weren't actually bad data.
Fix: keep the watch completely still during capture (set it down rather than holding it in a moving hand), and double-check that you've selected the correct bph for your specific watch — see what is beat rate (bph) if you're not sure.
If you don't have access to the underlying numbers, the message text itself tells you which case you hit — "not enough clear ticks" is the first (too few onsets overall), "too irregular to analyze reliably" is the second (onsets found, but timing too inconsistent). The fixes overlap (quiet room, close/steady mic placement) but the second case specifically benefits from double-checking bph and eliminating handling noise, which the first case doesn't particularly depend on.
A watch that's run down (little to no remaining power reserve) may tick too faintly or too irregularly to analyze reliably even in ideal conditions — try testing shortly after winding or wearing the watch. Very loud or acoustically unusual environments (tile rooms with heavy echo, for example) can also confuse the adaptive threshold in ways a quieter carpeted room wouldn't.
Does this mean my watch is broken? No — in the large majority of cases this message reflects capture conditions (noise, distance, handling), not a problem with the watch itself.
Can a stopped watch trigger this message? Yes — if the watch isn't actually ticking, there's nothing for the detector to find, and you'll see the "not enough ticks" version specifically.
Is there a way to see how many ticks it actually found? Not in a failed result — the "ticks analyzed" count only shows on a successful reading. If you're consistently just missing the 6-tick threshold, that itself suggests cause 1 (signal-to-noise) rather than cause 2.