Logic Pro Smart Tempo: Match Recordings to Tempo
A practical Smart Tempo workflow for deciding the timing reference, building or preserving a tempo map, correcting analysis and avoiding Flex artifacts.
Smart Tempo can make Logic Pro follow a freely played performance, or make an imported recording follow the project grid. Those are opposite jobs. Most Smart Tempo mistakes begin when you choose Keep and Adapt without first deciding which timing should remain authoritative.
Last verified August 6, 2026 against the current Apple documentation cited in this guide. Work on a protected project copy: applying a new tempo map can affect Drummer, MIDI, loops, tempo-synced effects, automation positions, and flex-enabled audio across the project.
Fast answer: choose Adapt when the performance should define the project tempo. Choose Keep when the project grid should stay fixed and the audio should conform. Use Auto only when its decision rule is useful, then inspect the Smart Tempo analysis, correct the first downbeat and any half/double-time error, and switch out of Adapt after the map is approved.
Keep, Adapt, and Automatic
| Mode | What stays fixed | Best use |
|---|---|---|
| Keep Project Tempo | The project tempo map | Make imported or recorded audio follow an existing grid |
| Adapt Project Tempo | The timing of the reference performance | Build a project tempo map from free playing |
| Automatic | Logic decides between Keep and Adapt | Capture when its reference rules match your session |
Apple’s Smart Tempo overview defines the three modes and explains that Automatic chooses Keep when a musical tempo reference is present and Adapt when no reference is present.
A metronome, an existing audio, MIDI, or Drummer region in the recording area, and Cycle mode can count as a tempo reference. If you need the next free performance to define the map, remove or isolate those references. Don’t assume Auto will adapt.
Decide what should follow what
The project should follow a human performance
Use this for a rubato piano, singer-songwriter take, live band, or other performance whose natural push and pull should remain intact. Smart Tempo analyzes the performance and creates a changing project tempo map. The click, Drummer, MIDI, Apple Loops, tempo-synced effects, and later Session Player arrangement can then follow that map.
The recording should follow a fixed project
Use this for an imported loop, percussion part, reference section, or free take that must conform to an existing song. Keep the project tempo, analyze the file, and choose an appropriate Flex & Follow setting for the region.
Do not “Adapt” an established production to one incidental loop. Do not “Keep” a free live performance and then wonder why the click ignores its feel.
How to match a free recording with Smart Tempo
- Save a protected project copy before changing tempo behavior.
- Start with the free performance isolated and turn the metronome off.
- Choose Adapt Project Tempo in the Smart Tempo menu.
- Record or import the performance that should define the tempo map.
- Open the Smart Tempo Editor and preview the analysis with its metronome.
- Correct half-time or double-time detection and set the true first downbeat.
- Add downbeat, beat, or time-signature hints only where the analysis needs help.
- Lock verified ranges before reanalyzing later sections.
- When the map is approved, switch the project to Keep or an intentional Auto workflow.
- Add Drummer, MIDI, loops, and tempo-synced effects only after the reference map is stable.
Apple’s current automatic tempo-matching instructions describe this Adapt workflow and specifically recommend returning to Auto or Keep after the initial recording so later takes do not replace the original tempo map.
Use Free Tempo Recording for a clean first take
Add the Free Tempo Recording button to the control bar when you want to capture a performance without managing mode changes during recording. Logic can mute existing tracks, analyze the result, and then ask whether to apply the region tempo to the project, apply the project tempo to the region, or use an average tempo.
Choose based on the authority decision. Apply Region Tempo to Project Tempo preserves the performance feel as the project map. Apply Project Tempo to Region asks the new recording to conform to an established grid.
Make imported audio follow the project tempo
- Set the project to Keep.
- Import the audio and select its region.
- Open the Smart Tempo Editor and verify the detected file tempo and downbeat.
- Correct analysis errors before increasing Flex & Follow strength.
- Choose Off, On, Bars, or Beats according to how tightly the file must conform.
- Listen for stretching artifacts at transients, sustains, fills, and transitions.
Apple’s Flex & Follow reference defines the options:
- Off: no project-tempo following and no Flex enablement.
- On: the region follows project tempo and manual Flex edits.
- Bars: Smart Tempo markers align the region at every downbeat.
- Beats: markers conform the region at every beat.
More alignment isn’t automatically better. Beats can tighten rhythmic material but create excessive stretching in a performance that should breathe. Start with the least aggressive setting that solves the musical problem.
Fix half-time and double-time detection
A performance around a slow pulse may be interpreted at twice the intended BPM. Busy subdivisions may produce the opposite. The audio can sound unchanged while the bar grid, Drummer feel, and tempo-synced effects behave incorrectly.
- Open the region in the Smart Tempo Editor.
- Compare the detected BPM with the pulse you would count for the song.
- Use the Double Tempo or Half Tempo control for the file or selected range.
- Recheck downbeats and bar numbers, not only the numeric BPM.
Apple’s Smart Tempo Editor guide documents the ×2 and ÷2 controls and notes that editor changes affect tempo information Logic uses for conformity, not the source audio data itself.
Correct the first downbeat and pickup
A correct average BPM with a wrong first downbeat still produces a useless grid. Find the first real bar downbeat, not necessarily the beginning of the audio file. A pickup note may occur before bar 1, and silence at the file start isn’t musical timing information.
Set a downbeat hint at the correct musical position, then add only enough later hints to keep the analysis aligned. Apple’s hint-mode guide says that a few downbeat hints near the beginning are often enough and recommends applying hints before fine beat-marker edits.
Use hints, beat markers, and locked ranges in that order
- In Hint mode, mark the true downbeats and any essential beats or time-signature changes.
- Apply the analysis and listen against the editor metronome.
- Switch to Beat Marker mode only for specific residual errors.
- Lock a verified range before reanalyzing another section.
Time-signature changes require explicit hints. Locking matters because later reanalysis can otherwise alter previously corrected markers. Apple’s range-lock instructions confirm that a locked section is protected from further edits and reanalysis.
Smart Tempo with multitrack recordings
Do not analyze each microphone as if it were a separate performance. Kick, snare, overheads, bass, and guide vocal belong to the same timing event. Create a Smart Tempo multitrack set, include the files that should contribute, and use a suitable downmix or rhythmically clear reference for analysis.
Apple’s multitrack Smart Tempo guide documents the shared analysis workflow. Edit grouped tracks together after the map is stable so phase relationships do not drift.
Why Smart Tempo may sound wrong
The wrong source defines the map
Use the rhythmically reliable performance as the main reference, not a pad, reverb-heavy vocal, or noisy room microphone.
Auto chose Keep instead of Adapt
A tempo reference was present. Use Adapt deliberately for the initial free performance, then switch back after approval.
Flex & Follow is Off
The region won’t follow project tempo. Select the region and choose the least aggressive On, Bars, or Beats option that fits the job.
The map is half-time, double-time, or one beat late
Correct tempo scale and the first downbeat before moving individual markers.
Too many hints create an unstable map
Start with clear downbeats in a few consecutive bars. Add detail only where the metronome audibly leaves the performance.
The audio is stretched too far
Large tempo differences and beat-level conformity can create artifacts. Choose a closer project tempo, use Bars instead of Beats, or preserve the original performance.
If analysis or Flex processing causes overloads, use the Logic Pro system-overload guide. More timing and production tools are organized in the Logic Pro features hub.
Frequently asked questions
What is the difference between Keep and Adapt in Smart Tempo?
Keep preserves the project tempo and can make enabled audio follow it. Adapt preserves the reference performance’s timing and changes the project tempo map to match.
Why did Smart Tempo detect twice the BPM?
Logic interpreted subdivisions as the main pulse. Use Half Tempo in the Smart Tempo Editor, then confirm that downbeats and bar numbers match the music.
Does Smart Tempo change the original audio file?
Smart Tempo Editor changes update tempo information Logic uses to conform the region; they do not rewrite the source audio data. Flexed playback can still sound altered.
Should I use Bars or Beats in Flex & Follow?
Start with On or Bars when you want to preserve internal feel. Use Beats when every detected beat must follow the project and the stronger stretching remains artifact-free.
Can Smart Tempo analyze a live multitrack recording?
Yes. Create a Smart Tempo multitrack set so the related files share one analysis, then edit them as a group to preserve timing and phase relationships.
Should I leave Smart Tempo in Adapt after recording?
Usually not after the reference performance has created the approved tempo map. Apple recommends switching to Keep or an intentional Auto workflow so later recordings do not replace or reshape that original map. Save a protected copy before changing an established production.
