Change one BPM in Manual Tempo mode

Show the MIDI controls in the Transport window or Edit window toolbar if they are hidden. Disable the Tempo Ruler Enable, commonly called the Conductor button, so Pro Tools enters Manual Tempo mode. Click the current tempo field, type the desired BPM, and confirm the entry. The session now uses that manual value instead of events in the Tempo ruler.

You can also select the tempo field and tap the T key to estimate a pulse; Avid's help describes averaging recent taps. Typing is preferable when you already know the exact value. Enable the click and play several bars to confirm the grid. If the tempo field appears unavailable, check whether Conductor mode is still enabled.

Use Conductor mode for tempo changes

Enable the Conductor button so the session follows its Tempo ruler. Display the ruler through View, Rulers, Tempo if necessary. Place the insertion point at the desired bar and beat, then add a tempo event using the control in the ruler or the relevant Event menu command. Enter the BPM and transition behavior available in your Pro Tools version.

Add further events wherever the pace changes. Play across every boundary with the click enabled and watch the Bars|Beats grid. The Tempo Editor and Tempo Operations window provide more detailed curve and range workflows in supported versions. Because menus evolve, use the Reference Guide installed for your exact release rather than copying screenshots from an older tutorial blindly.

Know the difference between tick and sample timebases

Tick-based material is anchored to musical Bars|Beats positions. When tempo changes, its absolute sample-time location can move so it remains at the same musical location. Sample-based material is anchored to absolute time. This is a fundamental arrangement decision, not just a display preference.

MIDI naturally changes playback timing with the musical grid. Audio requires more care: a tick-based audio clip may move with bar locations without automatically changing its recorded duration unless the relevant Elastic Audio processing is active. Inspect each track's timebase indicator and Elastic Audio state before expecting a complete song to follow a new BPM.

Make audio follow the new tempo

For audio that should stretch with the session, work on duplicates or playlists, choose a suitable Elastic Audio algorithm, and analyze the material. Rhythmic drums, polyphonic mixes, monophonic lines, and vocals may need different processing choices. On appropriate clips, Pro Tools provides a Conform to Tempo command after Elastic Audio analysis; it can fail when tempo or bar duration cannot be determined reliably.

Check event markers and downbeats rather than accepting analysis automatically. Listen for transient smearing, phase changes, warble, and altered ambience. If a clip comes from a free-tempo performance, building a tempo map around the performance may preserve it better than forcing the performance onto a fixed grid. Commit or render only after the map and algorithm are approved.

  • Save a new session version before editing tempo.
  • Choose Manual Tempo for one value or Conductor mode for a map.
  • Audit every track's tick or sample timebase.
  • Use Elastic Audio only where duration must follow the grid.
  • Check clicks, sync points, markers, automation, and final exports.

Build a map for audio recorded without a click

Do not guess one average BPM for a performance that breathes. Identify a clear downbeat, select a known musical range, and use Pro Tools' Identify Beat workflow to establish bar-and-beat locations. Avid documents that the command calculates tempo from the selected time range and specified meter, inserting Bar|Beat information and related events.

Continue through the performance at musically meaningful intervals, checking the click between markers. More markers create a tighter map but can exaggerate tiny timing fluctuations; use enough to represent the performance and support editing. Confirm meter changes separately. Once the grid follows the recording, MIDI, markers, and tempo-synced work can be built around it.

Review automation, plug-ins, and synchronization

Tempo-synced delays, modulation, MIDI arpeggiators, and click behavior may update with the map, while plug-ins using milliseconds remain fixed. Automation and clips can be anchored in different ways, and external MIDI or video synchronization introduces additional clocks. Check the session at every major tempo point rather than listening only to the first verse.

Video and post-production sessions demand special caution because picture sync is based on absolute time. Changing a music grid can move tick-based items relative to picture even when sample-based production audio remains fixed. Duplicate the session, make explicit sync-point notes, and verify timecode positions before delivering stems.

Troubleshoot common Pro Tools tempo problems

If typing a manual BPM has no lasting effect, the Conductor is probably enabled and a tempo event controls playback. If MIDI follows but audio does not, inspect timebase and Elastic Audio rather than adding duplicate tempo markers. If clips shift location but retain duration, they may be tick-anchored without time-stretch processing. If a conformed clip sounds wrong, restore the duplicate and correct analysis or select a more appropriate algorithm.

A click that drifts against live audio usually means the performance needs a tempo map or the existing map needs more accurate beat anchors. A sudden error at one bar can be a misplaced tempo or meter event. Keep changes reversible, document the Pro Tools version and processing mode, and bounce a short reference with the click before printing the clean final mix.