Why your BPM reads half or double
A tempo detector looks for the pulse that repeats most strongly in a track. In most music there isn't just one: the kick, the snare, and the hi-hats each repeat at their own rate, and those rates are usually in a 1:2 or 2:1 ratio. The detector has to pick one, and sometimes it picks the "wrong" level.
So a dubstep track at 140 BPM shows up as 70. A drum & bass track at 174 shows up as 87. A slow ballad at 68 shows up as 136. In each case the software heard the right groove and counted it at a different speed.
That's why this is called an octave error: the number is off by exactly ×2 or ÷2, never by some random amount. If your BPM is off by a factor of two, the beats still line up, just on every other count.
What half-time and double-time mean
Half-time and double-time describe how a track feels, not its actual tempo.
- Half-time: the drums play as if the tempo were half as fast. In a typical half-time pattern the snare hits once per bar, on beat 3, instead of on beats 2 and 4. A 140 BPM dubstep track with that pattern feels like 70.
- Double-time: the drums or hi-hats move twice as fast as the main pulse. A hip hop beat at 90 BPM with rapid hi-hats can feel like 180.
Humans settle on one level without thinking, usually the one we'd nod our head to. Software doesn't nod. It sees two equally strong pulses and has to guess which one you mean.
There's also a convention problem. Drum & bass DJs say 174, not 87, even though the bassline often moves at half speed. Dubstep and trap are usually quoted at 140, not 70. The "right" BPM is partly an agreement inside each scene.
Genres that get hit the most
| Genre | Usual BPM | Common wrong reading | Why |
|---|---|---|---|
| Drum & bass | about 170–176 | about 85–88 | Half-speed bassline and pads |
| Dubstep | about 140 | 70 | Snare on beat 3, half-time feel |
| Trap | about 130–150 | 65–75 | Fast hi-hat rolls over a slow snare |
| Hip hop | about 80–100 | 160–200 | Busy hi-hats counted as beats |
| Ballads and downtempo | about 60–90 | 120–180 | Few clear hits, the detector leans faster |
| House and techno | about 120–135 | Rarely wrong | A kick on every beat |
Four-on-the-floor music, with a kick on every beat, is the easy case. The trouble starts when the kick and snare leave gaps and the hi-hats fill them.
How to tell a BPM is wrong
You don't need to listen to every track. Look for these signs:
- The number doesn't fit the genre. A dubstep track at 70 or a drum & bass track at 87 is almost certainly half of the real figure.
- It's an outlier in its folder. Twenty tracks at 172–176 and one at 86 means one was counted at half speed.
- It's exactly half or double a neighbor. 69.9 next to 139.8 is the same tempo, not two different ones.
- Tap along. Tap on every kick in house and techno. In breakbeat music, tap so the snare lands on your second and fourth tap. If the tapped number is twice or half the detected one, trust your tap.
- The beat grid looks sparse or crowded. Grid markers on every other kick mean half; markers between kicks mean double.
More on tapping and reading tempo in how to find the BPM of a song.
How to fix half and double BPM
- Choose a convention per genre and stick to it. For example: drum & bass in the 170s, dubstep and trap at 140, hip hop at 80–100. Write it down so your whole library agrees.
- Set the BPM range in your analysis settings. Most DJ software lets you choose a range like 78–155 or 88–175. Every result is folded into that range, so a drum & bass track lands at 174 instead of 87. One range covers about one octave, so pick the one that fits most of what you play.
- Fix the odd track by hand. Most DJ software has a double or halve option in the BPM or beat grid editor. It's usually a single click.
- Write the corrected BPM into the tag. Then the right number travels with the file to every program and every USB drive.
- Don't trust downloaded filenames blindly. A "70" in a filename may just be someone else's octave error, copied along.
Why it matters for sync and set prep
A wrong octave isn't just cosmetic. It breaks several things you rely on during a set:
- Sync: some software matches a 70 track to a 140 track by doubling it, some tries to change the tempo by a huge amount, and some just refuses. You find out which one mid-mix.
- Loops and beat jumps: with a half-time grid, a "4-beat" loop is really 8 beats, and beat jumps land in the wrong spot.
- Sorting and filtering: a dubstep track filed at 70 sits next to your slow hip hop instead of your other 140s, and a "138–142" filter never shows it.
- Phrase counting: the bar markers drift, so drops and breakdowns don't land where the grid says.
Fixing octave errors before a gig takes minutes. Finding them during a set costs a transition.
FAQ
Is 70 BPM the same as 140 BPM?
For mixing purposes, yes. Beats at 70 and 140 line up exactly, one beat of the slower track for every two of the faster one. What differs is the convention: dubstep and trap are usually quoted at 140, slow hip hop and ballads at 60–90.
Why does drum & bass show up at 87 BPM?
Because the bassline and pads often move at half speed, and a detector set to a range like 78–155 has to fold 174 down into that range. Choose a range that reaches up to the high 170s and drum & bass reads correctly again.
Can I mix a 70 BPM track with a 140 BPM track?
Yes, it's a classic trick. Double the slower track's tempo in your head, or in the software, and the beats lock together. It works best with half-time genres, for example a hip hop beat at 85 into drum & bass at 170.
Should I re-analyze my whole library to fix this?
Usually not. Octave errors are off by exactly ×2 or ÷2, so changing the BPM range can refold every number without analyzing the audio again. Only tracks that are wrong in other ways, like a tempo change partway through, need a closer look.
Faster with Taxonomy DJ
Taxonomy DJ detects BPM, key, and Camelot for your whole library, free and with no track limit. In the Music Library tab, click Add music folder, choose Analyze waveforms, then click Scan.
To fix octave errors for the whole library at once, open Settings ▸ Analysis ▸ BPM range and pick one of five ranges: 58–115, 68–135, 78–155 (the default), 88–175, or 98–195 BPM. Every stored BPM is refolded into the new range right away, with no re-analysis. Slow music fits 58–115; drum & bass fits 88–175 or 98–195.
Because every track then sits in the same range, right-click a track ▸ Filter BPM ±3 finds your real neighbors. To write corrected BPMs into tags for other DJ software, use the batch tag editor (Premium).
Read next: how to find the BPM of a song and changing tempo without changing key.