Reviewed concrete example
One recording can support several useful pulse rates
The phrase half time vs double time YouTube BPM describes pulse-level interpretation, not a platform feature. A tapper may follow a slow backbeat, a central beat, or faster subdivisions. Those choices can produce values related by factors of two even while the recorded source is unchanged.
The local tool shows candidates so the observer can listen again. It never chooses automatically.
Translate rates into physical intervals
A source candidate of 100 BPM has 600 ms between beats. Half rate 50 has 1,200 ms intervals, and double 200 has 300 ms. Try tapping each interval pace and notice which recurring accents it matches.
The numeric relationship is 1:2:4 for half/base/double BPM and 2:1:0.5 for interval duration. Rate doubles when duration halves.
Feel and tempo are not identical terms
A half-time feel can place the snare and motion at a slower level while the underlying beat grid continues. A double-time feel can increase activity without changing the base pulse. Saying “the tempo doubled” may be wrong when only arrangement changed.
Use language such as “tapped backbeat at 70; base candidate 140” when uncertainty matters. Do not replace an observation merely because another number is more common in a genre.
Worked 70/140/280 family
Suppose a session reports 70 corrected source BPM from taps every about 857.14 ms. Candidate base at 140 has 428.57 ms intervals, and double relative to 140 is 280 with 214.29 ms intervals. Depending on the pulse initially called base, the labels can shift; the ratios remain.
The safest note records what was actually tapped: “snare-level taps, 70 source; related candidates 140 and 280.” A listener can then interpret accents without losing the measured event stream.
Keep playback speed separate
Speed correction changes time scale; half/double interpretation changes pulse level. If 105 BPM was observed at 0.75×, source estimate is 140. Only then inspect 70/140/280 candidates. Treating 105 as a half-time candidate before correcting mixes two operations.
Conversely, if the purpose is the experienced slowed playback, keep the observed basis and candidate family 52.5/105/210. Both sets can be valid for different questions when labeled.
Listen for phrase organization
Strong beat accents, bass changes, chord rhythm, dance steps, bar openings, and melodic cadence can suggest a practical pulse. A candidate whose taps land on meaningful repeated positions may be easier to communicate.
Compound meter can defeat simple factor-two thinking. A 6/8 passage may support two dotted-quarter pulses and six eighth-note units, a factor of three. Swing can make subdivisions unequal. The half/base/double tool is a narrow 1:2 aid, not a meter analyzer.
Compare like with like
Before using the session comparator, align pulse and time basis. A 70 backbeat card and 140 beat-level card may describe the same section. Their 70-BPM range is not tempo drift. Relabel or retain both as different pulse levels rather than averaging them to 105.
Within a long mix, different genres can invite different operational pulse levels. Preserve the pulse note on every section card.
A useful ambiguity note
When both 70 and 140 remain plausible, write “tapped 70 at backbeat level; 140 base candidate retained.” Do not replace the measured value with the candidate. If another observer taps 140 directly, compare their interval cards at aligned pulse levels. The note makes disagreement analyzable without claiming either person made an error.
Test candidate motion against a short phrase
Choose a four-bar region and silently move at each candidate pace. A half-rate motion may land only on alternating strong beats; the base may organize every beat; double may follow subdivisions. Repeat the phrase without recording so the display cannot influence your choice. Then start a new card at the selected level. This listening exercise supplies context that arithmetic lacks and leaves every alternative available when the phrase supports more than one useful pulse.
Limits and privacy
No page can hear accents, infer meter, know genre, or select a musically authoritative BPM. Candidate display is pure arithmetic. The observer supplies every interpretation.
The site does not fetch video, accept a URL, use a microphone, inspect audio, read a player, call an API, or store a pulse choice. Inputs remain local until copied.
Frequently asked questions
Is half-time BPM always wrong?
No. It can be the most useful operational pulse when labeled and understood.
Does double-time feel mean source tempo doubled?
Not necessarily. Activity and accent density can change while the base tempo stays constant.
Should speed correction happen first?
Yes when interpreting source time. Divide observed BPM by speed, then inspect pulse candidates.
Can 6/8 require another ratio?
Yes. Two large pulses versus six subdivisions creates a factor of three, beyond this simple checker.
Correct the time basis, display half/base/double intervals, and listen at each pace. Record the actual tap level and keep alternative candidates when context does not settle the choice.
