Why is my BPM half or double? Half-time vs double-time

By Mike Farina · 29 September 2026

Your BPM reads half or double because the same groove can be counted at two tempos: a 140 BPM trap beat with the snare on beat 3 of each bar nods like 70, and detectors pick whichever pulse looks strongest. Both numbers describe the same track, so use the genre's convention (trap and dubstep around 140, drum and bass around 174) and halve or double the reading to match.

Why does my BPM read half or double?

Because tempo is partly a matter of opinion, and the software has to pick one.

A tempo detector looks for regular pulses in the audio: kicks, snares, hi-hats, anything with a sharp attack. In most tracks there are pulses at several speeds at once. Hi-hats might tick at 280 per minute, the kick and snare pattern might repeat at 140, and the big accents might land at 70. All three are real. The detector scores each candidate and picks the one that fits best, and on plenty of tracks two candidates, one double the other, score almost the same.

People have the same problem. Ask a room to clap along to a trap beat and some will clap at 140 and some at 70. Neither group is wrong. They're just counting different things.

This is sometimes called the octave error in tempo detection, borrowing the idea from pitch, where a note and the note an octave above share a frequency ratio of two.

What's the difference between half-time and double-time?

Half-time is when the drums feel like they're moving at half the actual tempo. In a half-time pattern at 140 BPM, the snare lands on beat 3 of each bar instead of on 2 and 4, so it hits once every four beats rather than every two. Your head nods at 70 while the hats and rolls keep the 140 grid busy.

Double-time is the reverse: a part that moves as if the tempo had doubled, like hats in fast sixteenths or a vocal flow that suddenly packs twice the syllables into each beat.

Neither changes the tempo of the track. They change how it feels, and feel is exactly what trips up detectors.

Which genres get the wrong BPM most often?

The ones that live on half-time feels. These are the usual suspects, with the ranges producers commonly quote. They're conventions, not rules.

Notice lo-fi goes the other way. Slow, swung tracks with busy hats can pull a detector up to double. Anything in the 60s and 70s with sixteenth-note hats is a candidate.

Swing causes a related problem. Heavily shuffled tracks can occasionally be read at two thirds or three halves of the real tempo, like 80 against 120, because the triplet grid is strong enough to look like a pulse in its own right. It's rarer than halving or doubling, but if a number looks bizarre, try multiplying by 1.5 or 0.667 before assuming the detector is broken.

How do I tell which BPM is right?

There's rarely one objectively correct answer, but there is usually a conventional one, and that's the one worth using so your library sorts sensibly. Here's how I check:

1. Find the snare or clap and count "one, two, three, four" at the detected tempo. Snare on "two" and "four" is a plain backbeat at that tempo. Snare only on "three" means you're counting the fast pulse of a half-time groove. Snare on every beat usually means the count is running at half speed. That tells you what the detector locked onto, not which number to keep: a half-time trap beat reads as a normal backbeat at 70, and is still conventionally filed at 140.
2. Check against genre convention. If a drum and bass track reads 87, it's 174. Nobody catalogues DnB at 87. Same with dubstep at 70.
3. Tap it yourself. Tap along to whatever your body wants to nod to and compare. If your tap is half or double the detector, you now know both candidates. There's a guide to doing that well in how to tap tempo.
4. Play it against a grid. Hearing the beat marks against the music is the fastest way to catch a wrong number.

On that last point, the keyandbpm analyser draws a beat grid under the waveform and lets you press play to hear the track against the beat marks, along with a confidence figure for the tempo. If the marks fall on every other kick, or the grid is twice as dense as the drums, you'll hear it in a couple of bars. It runs in your browser and doesn't upload anything.

Does it matter if the BPM is half or double?

Sometimes not at all. A 70 and a 140 grid line up on every other beat, so for quick cuts the difference is cosmetic.

It matters in three places:

• Sync. DJ software syncing a track tagged 87 to one tagged 174 may try to speed the first one up to double speed, or refuse. Some platforms handle half and double relationships for you, some don't. Consistent numbers remove the question.
• Sorting. If half your DnB is filed at 87 and half at 174, sorting by BPM scatters it across your library.
• Production. Setting your DAW project to 70 when the sample was built at 140 means your grid, your swing and your delay times all come out at the wrong resolution. Delay times in particular double or halve, which is worth checking in BPM to milliseconds.

How to fix a half or double BPM in your DJ software

Two approaches, and it's worth doing both.

First, set a sensible analysis range. Rekordbox, Serato and Traktor all let you limit the range their tempo detection works within, in their analysis settings. If you mostly play 120 to 130 BPM house, a range that doesn't include 60 to 65 means it can't report half-time. If you play everything from 70 BPM hip hop to 174 DnB, no single range fits, and you'll be fixing some tracks by hand.

Second, fix individual tracks. All three apps let you edit the tempo or beatgrid of a track, including halving or doubling it, when you're in their grid editing tools. Halving or doubling keeps the grid anchored to the same downbeat, so it's usually a one-click fix rather than a full re-grid.

If you tag files outside your DJ app, decide on your convention before tagging, then make sure the app isn't re-analysing and overwriting your values. Tagging key and BPM for Rekordbox, Serato and Traktor covers that.

How to fix it in a DAW

Most DAWs detect tempo when you drop in audio, and they have exactly the same problem. The fix is the same: if the warp markers or grid are landing on every other kick, or twice per kick, look for a halve or double tempo command in the clip or warp settings before you start moving markers by hand. Once the clip is at the right tempo, set the project to match.

If you're making a half-time beat, I'd set the project at the higher tempo (140, not 70) and write the half-time drums on that grid. You get finer resolution for hats and rolls, and your file names and tags will match what other people expect from the genre. That's an opinion, and plenty of producers do the opposite, but pick one and be consistent.

For anything beyond half and double, like a sample that's genuinely at the wrong tempo for your beat, you're into time-stretching and repitching. How to fit a sample's key and tempo to your beat goes through that.