Tempo mapping guides · Pro Tools
How to tempo map in Pro Tools.
Pro Tools has two built-in tools — Beat Detective and Identify Beat — but both are manual. Importing a MIDI tempo map is the fastest route, and it's the method engineers on the Avid forums recommend. Here's the full picture.
The built-in way
Beat Detective and Identify Beat.
Beat Detective detects beat triggers and converts them into a tempo map. Identify Beat is the fully manual fallback: you tell Pro Tools where each bar starts.
- 01
Select the material
Select the audio (or a bounced click track) and open Event → Beat Detective. Define the selection — Capture Selection if it aligns with the grid, or Tap End B|B if you don't know the length.
- 02
Analyze
Click Analyze, then raise the Sensitivity until beat triggers land on the beats.
- 03
Generate the map
Choose Bar|Beat Marker Generation and click Generate to write the tempo map into the session.
- 04
Work in short sections
Upbeats and meter changes confuse Beat Detective — work in 4-bar sections and verify each one before moving on.
The fast way
Import a MIDI tempo map instead.
MIDI carries tempo and meter information — importing a MIDI file with a tempo map is the fastest way to get the grid right.
- 01
Export the MIDI tempo map from TempoSync
The file contains the full tempo map and click events for the whole track.
- 02
Import into Pro Tools
File → Import → MIDI (or drag the file into the session). The tempo map comes along with the MIDI.
- 03
Verify against the recording
Play back with the click and check the tempo ruler follows the performance.
Identify Beat (Command/Ctrl+I) still has its place for spot fixes: place the cursor on a bar start, press Ctrl+I, and type the bar|beat position.
The TempoSync workflow
From recording to tempo track.
1. Upload your recording — a live take, a drum recording, or anything recorded without a click.
2. Export the MIDI tempo map, along with a WAV click track if you want one.
3. Import the MIDI file using the steps above. Your tempo track follows the recording.
Comparison
Built-in tools vs TempoSync.
| Built-in | TempoSync | |
|---|---|---|
| Availability | All editions — but fully manual. | MIDI import works in every edition. |
| Effort | Trigger tweaking per section, or bar-by-bar Identify Beat. | Automatic detection on upload. |
| Output | Tempo map in the current session. | Tempo map, WAV click track, and MIDI file — portable. |
| Learning curve | Beat Detective has a real learning curve. | Upload, export, import. |
FAQ
Tempo mapping, answered.
Beat Detective or Identify Beat?
Beat Detective for dense, rhythmic material; Identify Beat for quick spot fixes. Both are slower than importing a ready tempo map.
Why does Beat Detective miss triggers?
Upbeats, fills, and meter changes confuse the detection. Work in short sections and adjust Sensitivity per section.
Does importing MIDI overwrite my existing tempo map?
Pro Tools merges imported tempo events into the session's tempo ruler — verify the result before importing into a session you care about.
Can I bounce the click track to audio for Beat Detective?
Yes — if Beat Detective struggles with the original recording, bounce the TempoSync click WAV and generate the map from that.
Skip Beat Detective entirely.
Upload the recording, export the MIDI tempo map, and import it into Pro Tools. The tempo ruler writes itself.
No subscription. Audio is deleted after analysis.