Home Vocal Recording and Mixing
Beat not lining up with REAPER’s grid? How to find its real tempo before you record
Published November 7, 2026 · Updated November 11, 2026
Usually one of two things is wrong: the beat’s real tempo is not the number you typed in (labels are often rounded, or simply wrong), or the beat’s first downbeat does not sit on a bar line. Fix it by moving REAPER’s grid to the beat, not the beat to the grid. First set the beat item’s timebase to Time so a tempo change cannot stretch it. Then select exactly one bar of the beat, from one downbeat to the next, and use Create measure from time selection (detect tempo) (Alt+Shift+C) or the ruler’s set-tempo-from-selection command. Finally drag the beat so its first downbeat lands on a bar line, and check a bar near the end. This is fixable in a few minutes for a steady beat. A beat whose tempo genuinely wanders needs a tempo map, or you record without the grid.
You drop a beat into REAPER, set the tempo the seller listed, turn on the metronome, and within a few bars the click and the kick are no longer together. Or the grid lines sit just before every snare. It looks like REAPER is broken. It almost never is. The grid is a ruler, and right now it is measuring with the wrong spacing or starting from the wrong place.
This matters for vocals more than it seems. Punch-ins, loop recording, comping, tempo-synced delay and copying a hook from one chorus to the next all assume the bars in REAPER are the bars in the beat. If you are only singing straight through to the beat, you can record without fixing anything. If you want any of those tools to behave, fix the grid first.
Why the beat and the grid disagree
| Symptom | Likely cause | What to do |
|---|---|---|
| Off by the same amount everywhere | The beat does not start on a bar line (silence, a tag or a pickup before the first downbeat) | Move the beat item, Step 4 |
| Starts together, slowly drifts apart | The real tempo differs slightly from the number you entered | Measure the real tempo, Steps 2 and 3 |
| Grid clicks twice per beat you feel, or half as often | Half-time or double-time reading of the same tempo | Pick the reading that puts bar lines where you count “one” |
| Drift that speeds up and slows down | The beat itself is not at a fixed tempo | Tempo map or ignore the grid, see below |
| Beat also sounds higher or lower than it should | A speed problem in the file, not a grid problem | See the sample rate fix linked below |
Small tempo errors add up. As an illustration (arithmetic, not a measurement): 32 bars of 4/4 is 128 beats. At 140 BPM that takes about 54.86 seconds; at 139.5 BPM it takes about 55.05 seconds. Half a BPM of error puts you roughly 0.2 seconds adrift by bar 32, which is clearly audible against a click. One 2010 forum thread traced drift to exactly this kind of cause: parts exported at 125 BPM against others at 124.1, each in time on its own and drifting together.
Step 1: Lock the beat so a tempo change cannot stretch it
Do this before you touch the tempo. REAPER’s default project timebase is Beats (position, length, rate). The official user guide explains that with this setting, changes in tempo cause items to be resized and their play rate adjusted. So if you import the beat and then change the BPM, REAPER stretches the beat to the new tempo, which is the opposite of what you want here.
Select the beat item, press F2 to open Item Properties, and set Item timebase to Time. The guide lists the options as the track or project default, Time, Beats (position, length, rate), Beats (position only), and Beats (auto-stretch at tempo changes). You can also set a whole track’s timebase from the track’s right-click menu, with Track timebase.
Set those vocal items (or the vocal track) to Time as well before you change the tempo, so nothing you have recorded moves or stretches. If you later move the beat in Step 4, select the vocal items with it and move them together.
Step 2: Mark exactly one bar of the beat
Turn snap off (Alt+S toggles it, according to the user guide) so your selection is not pulled to the wrong grid. Zoom in on the start of the beat and find the first clear downbeat, usually the first big kick. Drag a time selection on the ruler from that downbeat to the next downbeat, one bar later. Zoom in on both edges and adjust until each edge sits right at the start of the hit, not on the tail.
Choose a bar with a clear kick on beat one, and avoid an intro with no drums if you can. A sloppy edge here becomes a tempo error everywhere else.
Step 3: Let REAPER set the tempo from that bar
The user guide gives two routes, both from a time selection:
- Create measure from time selection (detect tempo), on the ruler’s right-click menu or
Alt+Shift+C. This makes the selection exactly one measure by inserting a tempo marker. It is the same command the guide uses to tempo-map a live performance bar by bar. - The ruler’s right-click menu also has commands to set the project tempo from a time selection. Use one of these if you want a single tempo for the whole song with no markers.
Pick one. The guide notes that once tempo or time signature markers exist in a project, you can no longer set the project tempo from a time selection. If you tried the marker route first and want the other, remove the marker and try again.
Then sanity-check the number. Labels are often rounded, so a result like 139.6 for a beat sold as “140” is plausible, and you may simply type the label’s value into the BPM box on the Transport Bar if it lines up just as well. Detection is not infallible: a forum user reported REAPER reading a 120 BPM click as roughly 68. If the number looks nothing like what you hear, recheck your selection edges.
Step 4: Put the first downbeat on a bar line
With snap still off, drag the beat item left or right until its first downbeat sits exactly on a bar line. Starting the beat at bar 2 rather than bar 1 leaves you a bar of space for a count-in. Because the beat is set to Time, moving the item moves the whole beat unchanged.
Now check it. Turn on Options › Metronome enabled, play from the middle and from the last chorus, and look at where the late kicks fall against the grid. If they still land on the bar lines at the end of the song, you are done. If they creep, your one-bar selection was slightly off. Redo Step 2 on a bar later in the song, which spreads any edge error over more time when you compare.
If the beat really drifts
Some beats do not hold one tempo: anything built from a live-played loop, or exported from a tool that was not locked to a grid. You will see it as drift that changes direction. You have three honest options:
- Tempo-map it. Repeat Step 2 and
Alt+Shift+Cbar by bar, or section by section, so REAPER’s grid follows the beat. The user guide describes exactly this for a performance not recorded to a click. It is slow, but the beat stays untouched. - Stretch the beat to the grid. REAPER can change an item’s playback rate in Item Properties, with an option to preserve pitch, and it has stretch markers for finer warping. This changes the audio, and a large stretch can be audible, so treat it as a last resort.
- Ignore the grid. Turn off snap and the metronome and record by ear. Markers on your sections still work for punch-ins. You lose tempo-synced delay and grid-based copying, but the vocal can still be great.
What this fix will not do
- It will not tighten your vocal timing. A late phrase is a separate fix, covered in how to fix vocal timing in REAPER without re-recording.
- It will not fix a beat that plays at the wrong speed and pitch. That is usually a sample rate problem; see how to fix audio recorded at the wrong sample rate in REAPER.
- It will not make Media Explorer’s Tempo match work on a file with no tempo information. Why that control often looks dead is explained in how to use REAPER’s Media Explorer to audition and import beats.
- It will not fix a beat that sits too high or too low for your voice. Whether to shift it, sing the line differently or ask for a new version is covered in what to do when a beat is in the wrong key for your voice.
- It will not fix a beat that is too loud to sing over. That is headroom, not timing: how to record vocals over a mastered beat that is too loud.
- It will not guarantee a perfect detection. Always confirm by ear and by eye at the end of the song.
The cleanest order for any new song is: import the beat, set it to Time, find the tempo, line up the downbeat, then record. The rest of the session setup is in how to set up a new REAPER project before you record.
When a beat and REAPER’s grid disagree, move the grid, not the beat. Set the beat to Time so tempo changes cannot stretch it, measure one clean bar, set the tempo from it, drag the first downbeat onto a bar line, and check a bar near the end. If the beat itself wanders, tempo-map it or record by ear.
Sources
- Geoffrey Francis, Up and Running: A REAPER User Guide v7.85 (November 2026), official HTML edition: section 2.2 Project Settings (the project timebase determines REAPER’s behavior when project tempo changes; default Beats (position, length, rate); track timebase override); section 7.16 Changing a Media Item’s Timebase and the Item Properties list (Item timebase options; Playback rate; preserve pitch when the playback rate is changed); section 9.16 Tempo Based Music Production (timebase behavior on tempo change; 9.16.5 Beat Correction, Create measure from time selection (detect tempo), Alt Shift C, tempo-mapping a performance not done to a click). dlx.reaper.fm/userguide/html
- Same guide, section 10.8 Time Signature/Tempo Changes and Markers (ruler context menu options from a time selection; after tempo or time signature markers are added you can no longer set project tempo from a time selection; markers pinned to beat position unless the project timebase is time), section 12.2 Project Timebase, Time Signature and Related Settings, the toolbar reference (Snap, Alt S) and section 3.8 Using the Metronome. dlx.reaper.fm/userguide/html
- HomeRecording.com forum, “Can’t Line Up My Drums With The Tune!” (2010): parts drifting apart traced to 125 BPM against 124.1 BPM. homerecording.com
- HomeRecording.com forum, “Beat Detection/Sync Issue” (2012): imported tracks drifting off REAPER’s metronome at the same nominal BPM; a reply reporting tempo detection reading a 120 BPM click as about 68. homerecording.com
- HomeRecording.com forum, “Matching an imported drum to the grid”: an imported drum pattern that would not line up with REAPER’s grid at the same BPM. homerecording.com
Every source above was retrieved and checked on November 7, 2026. REAPER behavior is taken from the official user guide, read in its HTML edition; forum threads are used only as evidence that the problem is common. The drift figures are arithmetic for illustration. The steps were checked against the documentation, not tested in a session, and no testing is claimed.