Two decimal places, and why
If you are stretching a loop into a 128 BPM session, the difference between 127.5 and 128.0 is a beat of drift every four bars. That is the error you notice at bar 33 and then spend twenty minutes hunting.
DropWave reports a real estimate to two places — not a rounded integer with digits added to look precise.
The grid survives a breakdown
The common failure in tempo detection is a reading that falls apart the moment the kick drops out, because the kick was carrying the whole measurement.
DropWave reads the pulse from across the spectrum. Hats, snares, rim clicks and percussion all count, not just the low end — so a breakdown, a half-time section, or an arrangement with no four-to-the-floor at all still gives you a grid that holds.
Half time or double time?
Often both. When DropWave says 103.16, could also be 206.32, the two numbers describe the same grid counted at different levels:
- A drum & bass tune at 174 has a half-time feel at 87.
- A trap beat at 140 is frequently written as 70 with double-time hats.
Pick whichever matches how you count the track. Naming the alternative is the whole point — a tool that picks silently is making a decision about your music without telling you it made one.
When there is no tempo
- Vocals and soft-transient material. Frequently no beat present at all — low confidence there is the correct answer.
- Rubato, live and unquantised playing. The tempo moves, so there is no single number.
- One-shots, ambient, drones. Nothing periodic to measure.
In your session
With the plugin, the same reading comes off a channel while it plays — useful on a loop you have already processed past recognising.
Requirements
macOS 13.0 (Ventura) or later. Universal — Apple silicon and Intel. about 40 ms per file, and it never connects to the internet. Closed beta — the Discord is the way in.
Related
Key finder · Key & BPM finder · How to find the BPM of a sample · How to find the BPM of a drum loop