Editorial Guidelines

Written by Hurst | Last updated: June 2026

Who Writes the Content on This Site

All content published on MusicTempoFinder.com is written by Hurst, rhythm analysis researcher, music production educator, and founder of this site. There are no guest contributors, no outsourced writers, and no AI-generated articles published without full review, fact-checking, and rewriting by Hurst personally.

Every page — whether a technical explanation of beat detection algorithms, a guide to interpreting BPM results, an FAQ answer, or a legal disclosure — is the direct product of Hurst’s research into tempo mathematics, onset detection, and the practical application of BPM measurement in music production and performance contexts.

Editorial Standard

The single test every piece of content on this site must pass before publication:

Would a music producer, DJ, recording engineer, or rhythm analysis researcher reading this page find it technically accurate, practically useful for real tempo measurement tasks, and honest about where automated BPM detection produces unreliable or ambiguous results — or would they find something oversimplified, inaccurate, or missing?

If the answer is anything other than “accurate, useful, and honest,” the content is not ready to publish. Generic content about “finding the beat” that does not address the half-time/double-time ambiguity, does not document algorithm behaviour, and does not state accuracy limitations honestly is not acceptable on any page of this site.

How Tool Pages Are Written

Tool pages on MusicTempoFinder.com are written to document three things with equal rigour:

1. What the tool measures and how Every tool page names the specific algorithm, formula, or signal processing pipeline involved. The tap tempo pipeline — interval recording, averaging using BPM = 60,000 ÷ average interval in ms, outlier filtering, and session reset logic — and the audio analysis pipeline — onset detection, autocorrelation, beat period identification, and tempo candidate evaluation — are both documented in full on the How It Works page. Tool pages summarise these pipelines in user-facing language without sacrificing technical accuracy.

2. What the result means A BPM figure is only useful if the reader understands what tempo range is normal for their genre, what the half-time/double-time ambiguity means for their result, and what variables — track consistency, rhythmic content density, production style — affect the reliability of the output. Every result explanation on this site includes this contextual layer.

3. What the tool cannot determine Automated BPM detection cannot resolve the half-time/double-time ambiguity definitively from audio alone. It cannot determine time signature. It cannot handle tempo-variable performances without producing averaged or unstable results. It does not capture the subjective feel or groove of a track. These limitations are stated explicitly on every relevant page — not footnoted, but presented as essential information for anyone using BPM data professionally. The FAQ addresses the most common questions about result interpretation and known limitations.

How Technical Articles Are Researched

Beat Detection and Tempo Analysis Content Articles covering onset detection, autocorrelation, spectral flux analysis, and tempo candidate evaluation are researched against established beat tracking research literature — including publications from the International Society for Music Information Retrieval (ISMIR) — and the W3C Web Audio API specification. Where specific accuracy figures are cited, the conditions under which those figures apply are stated explicitly: track type, rhythmic content, tempo consistency.

Tap Tempo Mathematics Content Articles covering tap tempo interval averaging, outlier filtering, and session reset behaviour are researched against the mathematics of interval measurement and the documented behaviour of tap tempo implementations. Accuracy claims for tap tempo results are stated with reference to tap count — for example, fewer than 4 taps produces an unreliable result; 8 or more taps produces a result within ±1 BPM under consistent tapping conditions.

Music Production and DJ Workflow Content Articles covering how BPM measurement is used in DAW project configuration, sample alignment, DJ mix planning, and live performance are written to reflect real production workflow rather than theoretical descriptions. Hurst does not publish claims about specific DAW software behaviour without verification against current software documentation.

AI Content Policy

Hurst uses AI writing tools as a research aid and first-draft accelerator. No AI-generated content is published on this site without the following process:

  1. Fact-check every technical claim — any formula, algorithm description, accuracy figure, or music production workflow claim is verified against a primary source before it appears on the page
  2. Rewrite for accuracy and specificity — AI drafts are rewritten to reflect Hurst’s research knowledge and the tempo-measurement-specific focus of this site; generic music content is replaced with content directly relevant to BPM detection and its practical applications
  3. Add site-specific context — general beat detection explanations are replaced with examples, worked calculations, and figures relevant to the specific tools and audience of MusicTempoFinder.com
  4. Final review before publication — every page is read in full by Hurst before it goes live

Corrections Policy

If a technical or factual error is identified on any page — an incorrect formula, a misattributed algorithm, an inaccurate BPM range, or an outdated workflow description — it will be corrected as a priority. Corrections are made to the live page and the “Last updated” date is revised. Significant corrections are noted at the top of the relevant page.

To report a correction, use the Contact page with the subject line “Content Correction” and the specific page URL and error. Hurst reviews all correction submissions personally. Response time: 48–72 hours.

What This Site Does Not Publish

  • BPM detection results or accuracy claims presented without disclosure of the algorithm, conditions, and known failure modes
  • Content implying automated audio BPM detection resolves the half-time/double-time ambiguity definitively
  • Music production advice that conflates BPM with time signature, groove, or musical feel
  • Medical, clinical, or hearing health advice of any kind
  • Link exchange requests, sponsored content, or paid product placements of any kind
  • Content written by contributors who have not verified their claims against primary rhythm analysis sources

Related Pages

  • About MusicTempoFinder.com — what this site is, who runs it, and who it is for
  • How It Works — full technical documentation of both the tap tempo and audio BPM detection pipelines
  • Data Security — how microphone audio and uploaded files are handled
  • Contact — to report errors, ask technical questions, or submit data requests

These guidelines were written by Hurst and apply to all content published on MusicTempoFinder.com. Last updated: June 2026.

Scroll to Top