YouTubeBPMFinder.online
Reviewed concrete example
Local taps follow wall time
To correct tapped BPM for YouTube playback speed, begin with the clock basis. The browser records when your actions occur in wall time. If external playback is slowed, taps arrive farther apart. If accelerated, they arrive closer together. The recorded source performance itself has not changed.
The site cannot read another player’s setting. Check it manually and preserve it with the session.
The correction formula
Observed tap BPM equals source BPM multiplied by playback speed S. Therefore source BPM equals observed BPM divided by S. At normal 1× playback, observed and source values are identical.
If a 160 BPM source is played at 0.75×, observed rate is 120. Dividing 120 by 0.75 returns 160. If the same source is played at 1.25×, observed rate is 200, and 200 ÷ 1.25 returns 160.
Durations scale inversely. A 500 ms observed interval at 1× corresponds to 120 BPM. At 0.5× for the same source, observed intervals become 1,000 ms and observed rate 60 BPM.
Worked tap-card correction
Suppose a session of sixteen intervals spans 10,000 ms, producing 96 observed BPM. External playback was 0.8×. Source estimate is 96 ÷ 0.8 = 120 BPM. The card should state both 96 observed and 120 source.
Half and double source candidates are 60 and 240. Those candidates address pulse interpretation, not the speed factor. Correct time scale first; then consider whether the tapper followed the intended pulse.
Use one named summary
The core surface can show overall, median, trimmed, and recent BPM. Each can be corrected by the same speed factor, but they may differ because their interval basis differs. Choose one for the headline source estimate and name it.
The launch card uses overall observed BPM for the primary source correction. If a collaborator prefers median interval BPM, write “median observed” explicitly before division. Do not combine a recent observed rate with an overall source label.
Avoid double correction
Once a value is labeled corrected source-time BPM, do not divide it again. Session comparison should use all observed values under comparable speed or all corrected source values. Mixing bases can create artificial spread.
A separate timestamp-based method may calculate directly from source content coordinates. Such a rate is already source-based. This tap brand’s raw observations are different because current-page events occur in wall time.
Check speed before the session
A remembered 0.75× when playback was actually 0.8× changes the answer. Observed 96 becomes 128 at 0.75 but 120 at 0.8. Read the setting and avoid changing it mid-run.
If speed changes, pause, seek, or buffering occurs during tapping, discard or separately document the contaminated run. One factor cannot describe a mixed-speed session.
Check multiple summaries consistently
Suppose overall observed BPM is 96, median observed is 97, and recent observed is 95 at 0.8×. Their corrected source values are 120, 121.25, and 118.75. The factor does not make them converge because each summary still describes different intervals. Preserve that structure rather than correcting one number and presenting it as the entire session.
When reporting a range, either correct both endpoints by the same speed or label the range observed. Dividing only the headline rate leaves surrounding evidence on a different clock basis.
Apply one factor consistently to every value that shares the declared basis.
Half and double are separate questions
An observed 90 at 0.75× corrects to 120, but a tapper following subdivisions may still prefer a 60 or 240 candidate. Speed math cannot infer meter, accents, or musical intent. The candidate checker displays interval durations for listening review.
Do not choose a candidate merely because it falls in a familiar database range. Preserve the actual pulse label and section context.
Limits and independence
The formula cannot verify speed, detect audio, repair missed taps, grade stability, or decide pulse level. Browser timing and human motion constrain the input. Rounding should not imply more precision than the session supports.
The site never reads the player, URL, video, audio, microphone, account, or API. Correction is local arithmetic on numbers entered or captured on this page. YouTube is a Google LLC trademark; this service is independent and unofficial.
Frequently asked questions
Do I multiply or divide?
Divide observed wall-time BPM by the playback-speed factor to recover source-time BPM.
What if playback was 1×?
Observed and source BPM match. The formula remains visible as an identity check.
Can the page detect the speed?
No. Read and enter the external setting yourself.
Which summary gets corrected?
Any named observed summary can be divided, but keep its basis explicit. The core headline uses overall observed BPM.
Check the external setting, select the intended observed summary, and divide once. Copy all three elements so later readers do not repeat or omit the correction.