Working with tempo and audio regions, Automatic tempo matching – Apple Logic Pro 9 User Manual

Page 595

Advertising
background image

The length of imported audio regions and the project tempo are directly linked. If you
change the tempo at a particular project position, the length of regions at, and after, this
position changes. You won’t hear a difference in the playback speed of the imported
audio, but all MIDI or software instrument regions will be out-of-sync with all audio
regions. Audio regions that are lengthened (by increasing the tempo) may overlap with
other regions on the same track, resulting in the earlier region being played in full at the
expense of the beginning of the following region. All audio region loop lengths (set with
the Inspector Loop parameter) change, resulting in irregular loops and strange polyrhythms
between tracks. Fortunately, you can circumvent these problems with Logic Pro.

This chapter covers the following:

Automatic Tempo Matching

(p. 595)

Setting the Project Tempo to Match an Audio Region

(p. 597)

Time Stretching Regions

(p. 599)

Using Beat Detection to Create Tempo Changes

(p. 601)

Importing, Removing, and Exporting Tempo Information

(p. 603)

Automatic Tempo Matching

The following audio files automatically match the project tempo and will follow any
tempo changes made in the global Tempo track.

• Audio recordings made in Logic Pro (7.0 and later)

For example, if you record a bass solo at 100 bpm, you can change the project tempo
to 120 bpm and the bass solo automatically plays back at the new tempo.

Note: The function only works in the parent project (the project the audio files were
created in). If you drag a file recorded in a given project to another project using the
Finder, the file cannot follow the project tempo. However, files copied between two
projects are able to follow the project tempo.

• Apple Loops files

• Audio bounces made in Logic Pro (7.0 and later)

595

Working with Tempo and Audio
Regions

18

Advertising