Compare Half, Base, and Double Tap Pulse Levels

Compare pulse levels without choosing for the listener

The YouTube half time double time checker takes one prepared BPM and displays a half, base, and double family. It does not record taps or decide which value is musically “right.” The observer uses accents, phrase structure, movement, and the task to interpret the candidates.

Select whether the input describes observed playback or corrected source time. The three rows retain that basis. No speed conversion occurs on this page.

The candidate arithmetic

Half BPM equals base ÷ 2. Double BPM equals base × 2. Interval duration equals 60,000 ÷ BPM. A base of 120 creates 60, 120, and 240 BPM, with intervals of 1,000, 500, and 250 ms.

These rates are exactly related. They do not describe small tapping variation. A result of 118 versus 121 is a different issue from 60 versus 120.

Why people tap different levels

A prominent backbeat can invite one tap every two quarter-note beats. A rapid hi-hat can invite eighth-note taps. Dancers, DJs, musicians, and editors may prefer different operational pulse levels even while describing the same recorded timing.

Half-time arrangement can change accent placement without halving source tempo. Double-time feel can increase activity without doubling the underlying quarter-note rate. The tool avoids using arrangement labels as mathematical verdicts; it simply shows interval relationships.

Worked 174 BPM example

Enter 174 corrected source BPM. Half is 87 and double is 348. Interval durations are about 689.66 ms at 87, 344.83 ms at 174, and 172.41 ms at 348.

If a tapper followed a snare every 689.66 ms, the observed session may report 87. Another following eighth-note motion may report 348. Both can be synchronized to the same source under different pulse definitions. The copied candidate panel should retain “corrected source time” so it is not mixed with slowed observed playback.

A second family at a slower pace

Enter 72 observed BPM. Half, base, and double are 36, 72, and 144, with interval durations about 1,666.67, 833.33, and 416.67 ms. If playback was slowed, this page still does not correct it; the basis label remains Observed playback.

Now imagine the same 72 is already a corrected source value. The arithmetic rows are identical, but their meaning changes. That is why the basis field belongs in copy output. A collaborator who sees only 72/144 cannot know whether another speed division is still required.

Try tapping the three durations with a simple motion without the video, then return to the passage. The physical contrast can reveal which recurring layer was followed. This remains interpretive: the checker never highlights a recommended row, orders candidates by popularity, or uses genre stereotypes. When none fits, consider a non-binary relationship or incorrect input basis instead of forcing a choice.

Listen for accents and phrase fit

Try tapping each candidate physically. At half rate, determine whether every tap lands on a meaningful recurring accent or skips important beats. At double, determine whether the taps follow a genuine subdivision or merely chase ornamentation. At base, listen for how bars and phrases organize around the pulse.

Meter can help but is not inferred. In compound meter, two larger pulses and six subdivisions may produce a threefold relationship rather than simple half/double. This checker is not sufficient for every pulse hierarchy.

Correct speed before comparing source candidates

If a session was tapped at altered playback and the goal is source-time interpretation, divide observed BPM by speed first. For example, 90 observed at 0.75× corrects to 120 source, whose family is 60/120/240. Applying candidates to the uncorrected 90 would describe observed playback instead.

Either basis can be useful; the problem is leaving it unstated. Use the selector and preserve it in copied output.

Limits and privacy

The page cannot hear accents, detect meter, identify a song, know why a pulse was chosen, or recommend one candidate. It does not calculate tapping stability, remove outliers, or compare sessions. Values above typical ranges remain arithmetic candidates rather than claims about performance.

No media, URL, player, microphone, API, account, or storage is involved. The rate and rows exist in current-page memory only.

Frequently asked questions

Enter the prepared rate, choose its time basis, and try the half, base, and double interval pace. Copy all three when ambiguity should remain visible.