How to place the beatgrid correctly.

How to place the beatgrid correctly

Before changing anything: prepare the track

Three preliminary checks save most of the work:

1. Choose the right moment. Adjust the grid with the track paused, from the grid panel. Working during playback is awkward and less precise.
2. Find a clear first hit. Do not use the initial silence or a pad without a transient. Find the first kick or the first hit with a clear attack.
3. Decide whether the track has a steady pulse. Club electronic music probably does. If it is a live recording, a track with human-played drums, or an edit, be prepared to work in sections.

One practical detail in rekordbox EXPORT mode: the documentation states that you cannot adjust the grid if the computer is connected to PRO DJ LINK-compatible DJ equipment. If the grid panel is unresponsive, check that before assuming something is broken.

The procedure, step by step

The exact names vary between applications, but the logic is identical. This is the procedure in rekordbox, which has the most detailed documentation:

1. Open the grid panel. In EXPORT mode it is called [GRID]; in PERFORMANCE mode, [GRID/PHRASE EDIT].
2. Place the first beat. Move the playback line to the first clear hit and set the first beat of the bar there. The aim is for the red first-beat marker to land on that hit.
3. Adjust the grid BPM. The panel expresses the distance between lines as BPM. If you know the actual tempo, you can enter it manually to change that distance.
4. Fine-tune with TAP if needed. TAP recalculates the grid from the interval between your taps. This is useful when the measured BPM is close but not exact.
5. Fine-tune in milliseconds. The shift buttons move the grid left and right in 1 ms steps; in PERFORMANCE mode the adjustment is more granular, with 1 and 3 ms steps.
6. Use the metronome. The panel includes a metronome that starts synchronised with the grid. It lets you check by ear: if the grid is correct, the click and kick sound together.
7. Reset the grid if you have lost your way. A function lets you set the grid again from the current position using the determined BPM. It is faster than undoing adjustments manually.

If the software uses markers—as Traktor does—the procedure is equivalent: place the initial marker and, if the track changes tempo, add further markers at the change points.

How to check that it is correct

A grid is correctly placed when all three of these conditions are met:

• At the beginning: the metronome click coincides with the kick.
• Halfway through the track: they still coincide.
• At the end: they still coincide.

If all three are met, you have a correct constant-tempo grid. If the beginning lines up but the end does not, the problem is not position but tempo: the track does not maintain a fixed BPM, or the value is scaled incorrectly.

Checking only the beginning is the most widespread mistake. On tracks with steady tempo, the error is not noticeable until the final third, which is exactly where you are not looking.

Double- or half-time BPM

This is the most confusing error, because the symptom does not look like a grid problem. The grid falls “between” the hits, or marks twice as many beats as are audible, and the metronome is consistently out of time.

The cause is that the analysis has interpreted the pulse incorrectly: it has treated something as a beat when it was not. The two variants are:

• Half-time BPM: the grid marks one beat for every two hits. The software “thinks” the music is moving at half its speed.
• Double-time BPM: the grid marks two beats per hit. The software “thinks” it is moving twice as fast.

The documented correction is to rescale the grid BPM, and its effect is described precisely: doubling the BPM halves the distance between grid lines, and dividing it doubles that distance. Some applications also include a specific setting to allow Sync when the BPM difference between tracks is exactly double or half.

It is easy to recognise once you have seen it: if tapping TAP along with the kick gives a BPM approximately double or half the value shown by the software, you have your diagnosis.

Tracks with variable tempo

Some tracks do not maintain a constant BPM: live recordings, tracks with human-played drums, some edits, and many classics. A single grid cannot resolve these:

• If the software allows it, define more than one grid section, each with its own tempo, and place markers at the points where it changes.
• If it does not, accept that Sync and Quantize will work poorly in part of the track, and compensate manually.
• Either way, the practical decision is the same: do not force a single grid onto a track that cannot support it. A forced grid gives a false sense of control and fails just when you need it most.

How to protect the work you have done

There is an official warning here that deserves attention: when a track is analysed again, its manually adjusted grid may be overwritten by the newly analysed one. If you have carefully corrected a batch and then run a bulk reanalysis, you can lose that work.

Protection is available and is called analysis lock: flag the track so that it ignores reanalysis and grid editing. While it is active, neither analysis nor editing in the grid panel affects that track.

Operational recommendation: analyse in bulk first, correct afterwards, and lock the corrected tracks before any reanalysis. And if you are moving to a new major version of the software, export your library first.

Common mistakes

Checking only the beginning of the track. The tempo error does not appear until later. Always check the end.

Placing the first beat on silence or a pad. Without a clear transient, there is no reference. Use a hit with an attack.

Trying to fix double-time BPM by shifting milliseconds. It is not an offset; it is a scale. The more you fine-tune manually, the worse it gets.

Analysing again after correcting. It can erase your work. Lock corrected tracks first.

Trusting the analysis without listening. Analysis gets most electronic music with a clear pulse right and fails on everything else. The metronome is your verification, not the software’s accuracy rate.