Hurst
Rhythm Analysis Researcher & Music Production Educator | Founder, MusicTempoFinder.com
Every musician who has ever tried to sample a record, sync a loop, or teach a student about pulse has encountered the same foundational question: what is the tempo of this piece, exactly? The answer sounds simple. It is not always easy to get right — especially from audio, where tempo fluctuates, time signatures vary, and the distinction between 90 BPM and 180 BPM is genuinely ambiguous without careful analysis.
My name is Hurst. I have spent years researching rhythm analysis, beat detection algorithms, and the mathematics of tempo measurement — from the simple interval averaging formula behind a tap tempo tool to the onset detection, autocorrelation, and half-time disambiguation logic required for reliable audio BPM detection. MusicTempoFinder.com was built out of a specific frustration: most tempo tools either work only by tapping, work only on clean audio, or produce a result with no explanation of what the algorithm actually did or why the number might be wrong.
The formula behind a tap tempo tool is disarmingly straightforward: BPM = 60,000 ÷ average interval in milliseconds. But the reliability of that result depends on how many taps you use, how outliers are handled, and how the session resets. A tool that does not document these choices is not giving you the full picture. For audio BPM detection, the picture is more complex — onset detection using energy envelope and spectral flux analysis, autocorrelation to find the beat period, and a disambiguation step to resolve the half-time/double-time ambiguity that affects nearly every real-world audio analysis. MusicTempoFinder.com documents all of it. To see the full pipeline, visit the How It Works page.
What I Research and Write About
Tap Tempo Mathematics and Interval Averaging The tap tempo method is conceptually simple but implementationally nuanced. How many taps are needed for a reliable result? How should outlier intervals — caused by a misplaced tap — be filtered without discarding valid data? When should the session reset? I research and document the specific choices that determine tap tempo accuracy, including the effect of tap count on result stability and the relationship between human timing variability and measured BPM precision.
Beat Detection Algorithms for Audio Analysis Audio BPM detection requires identifying the onset of beats in a signal — a task that varies in difficulty depending on the rhythmic content, production style, and tempo consistency of the track. Onset detection using energy envelope and spectral flux analysis, autocorrelation to identify the fundamental beat period, and tempo candidate evaluation across the plausible BPM range are the core components I research and write about. The FAQ addresses the most commonly misunderstood aspects of why BPM detection gives the result it does.
Half-Time and Double-Time Disambiguation The most frequently misunderstood aspect of automated BPM detection is the half-time/double-time problem. A track at 80 BPM and a track at 160 BPM have beat structures that are mathematically related — the autocorrelation function will produce peaks at both periods. Determining which is the “correct” tempo requires contextual information that no algorithm can fully resolve from audio alone. I write about this limitation specifically and honestly, because understanding it is essential for anyone using a BPM tool in professional music production or DJ work.
Tempo in Music Production and DJ Workflow BPM is not just a number — it is a workflow parameter. For producers, it determines DAW project tempo, sample grid alignment, and swing quantisation. For DJs, it determines mix compatibility and transition planning. I research and write about how tempo measurement tools fit into these practical contexts, what accuracy is actually required for different use cases, and what the distinction between a BPM result and a musical tempo indication means in practice.
Why I Built This
When I was looking for a browser-based BPM tool that handled both tap input and audio analysis, explained what it was doing, and was honest about where its results might be wrong, I consistently found tools that did one of these things but not all three. Tap-only tools were accurate for tapped input but useless for recorded audio. Audio analysis tools returned a number but gave no indication of confidence or the half-time/double-time ambiguity that might make the number meaningless for professional use.
What I built is a tool that does both — tap tempo with documented interval averaging, and audio BPM detection with documented onset detection and autocorrelation — and explains both honestly. Not just what the result is, but what the algorithm did to get there and where you should not trust it without verification.
Accuracy Standards
Every algorithm description, BPM range, and accuracy figure on MusicTempoFinder.com is cross-referenced against established beat detection research and the W3C Web Audio API specification. Accuracy claims for tap tempo are documented with reference to tap count and interval consistency. Accuracy claims for audio BPM detection are documented with explicit reference to the half-time/double-time ambiguity, tempo variation effects, and sparse rhythmic content limitations. All limitations are stated prominently — not in footnotes. For how audio and file data is handled during analysis, see the Data Security page.
Tools on This Site
- Music Tempo Finder — musictempofinder.com
Get in Touch
For content corrections, technical questions, or data requests, visit the Contact page or email directly: contact@musictempofinder.com
Response times: technical and content questions within 48–72 hours. Privacy and data requests within 7 business days. GDPR requests within 30 days. CCPA requests within 45 days.
Hurst is the founder and sole author of MusicTempoFinder.com. For a full account of how content is researched and written, see the Editorial Guidelines. Last updated: June 2026.