YouTubeBPMFinder.online
Reviewed concrete example
Plan before the clean section arrives
The YouTube tap window planner estimates how many deliberate taps fit inside a chosen observation duration. It does not capture taps. Enter a rough observed BPM and a target number of seconds, then use the plan to decide whether a section is long enough for the desired interval count.
The rough rate can come from an earlier attempt, a conductor note, or a simple guess. It is not verified. Playback remains outside the page, and no URL or media is needed.
Taps are one more than intervals
A tempo window is built from spaces between activations. Three intervals require four taps; sixteen intervals require seventeen taps. The planner first calculates expected intervals as rough BPM × target seconds ÷ 60, rounds to a whole interval count, and adds one for expected taps.
Suppose the rough rate is 120 BPM and target duration is 10 seconds. Expected intervals are 120 × 10 ÷ 60 = 20. The plan calls for 21 taps enclosing twenty intervals. At exactly 120 BPM, that whole-interval plan lasts ten seconds.
Rounding is disclosed. At 128 BPM for ten seconds, expected intervals are about 21.33. A recommendation of 21 intervals means 22 taps and an estimated duration of 60 × 21 ÷ 128, about 9.84 seconds. The result must show both the unrounded expectation and selected whole count.
Compare standard interval targets
The result also lists durations for eight, sixteen, and thirty-two intervals. At 120 BPM, those spans last 4, 8, and 16 seconds. At 60 BPM, they last 8, 16, and 32 seconds. Faster music fits more intervals into the same period, but it can also invite subdivision mistakes.
These values help choose a section. If a clean groove lasts only six seconds at 120 BPM, an eight-interval window is feasible while sixteen intervals would cross the transition. If the next section offers twenty seconds, thirty-two intervals may fit without overstaying.
More taps are not always better
A longer run lowers the proportional effect of one late tap, but it can span a fill, tempo ramp, mix transition, or lost focus. The plan answers quantity, not section quality. Stop the live surface when the chosen pulse changes even if the target count has not been reached.
Conversely, a four-tap minimum offers only three intervals and little information about spread. Eight or more taps make recent and median summaries more informative. Ten or more intervals are needed for the core trimmed result under its declared recipe.
Use observed rate, not corrected source rate
Tap density follows what the observer hears in wall time. If source tempo is 160 BPM but playback is slowed to 0.75×, observed rate is 120 BPM. Enter 120 into this planner because that determines how quickly taps arrive. Speed correction belongs after a session or in the dedicated corrector.
Entering 160 would predict too many taps for the slowed passage. This is why the label says Rough observed BPM. The page does not ask for external speed and cannot infer it.
A practical rehearsal plan
Imagine a viewer expects about 96 observed BPM and has a 15-second stable verse. Expected intervals are 96 × 15 ÷ 60 = 24, so the plan recommends 25 taps. Eight intervals would take 5 seconds, sixteen would take 10 seconds, and thirty-two would take 20 seconds. The sixteen-interval option fits comfortably with room to start and stop cleanly.
The copied plan might read “rough 96 observed BPM; target 15 s; 24 intervals; 25 taps; comparison 8/16/32 intervals = 5/10/20 s.” It contains no song or video information.
Limits and local scope
The planner cannot predict human reaction, missed taps, browser delay, tempo variation, or whether a section remains stable. It does not guarantee that the live result will match the rough input. Its recommended count is preparation, not an accuracy score.
No live events are captured. The page does not fetch or embed YouTube, read player speed, listen to audio, use a microphone, upload media, call an API, or save plans. Values disappear after Reset, reload, or closure.
Frequently asked questions
Why round intervals instead of taps?
Tempo is defined across completed intervals. Once a whole interval count is chosen, taps equal intervals plus one.
Which BPM should I enter at slowed playback?
Enter the observed wall-time rate, because it predicts tap arrival. Correct source BPM after the session.
Is thirty-two intervals always best?
No. Use the longest coherent section rather than crossing a musical change to reach a target.
Does this page capture my taps?
No. It creates a duration plan only. Use the core tap surface when ready.
Enter the rough observed rate and available seconds, compare target durations, and pick a whole-interval count that ends before the section changes. Then move to the live surface.