Why won't automation move with global tempo change?
May 11th, 2020, 08:33
Rhythm tracks (drums, bass, etc.) were recorded at 155 BPM at a pro studio, using Logic. The vocalist then recorded vocal tracks at home, using Logic on a different computer, and using a rough mix of the studio session as a guide, imported as Track 1. On the vocalist's home computer, a click wasn't used. The rough mix was imported with the global BPM for the file simply set to the default, 120. Many separate vocal tracks were then recorded, and volume automation was used extensively to sync up the various vocals. All of these vocal tracks, with automation, need to be sent back to the pro studio for mixing. The automation can be printed into the stems, but ideally the automation tracks could be left intact, so the studio engineer can adjust automation as needed. However, if the global BPM is changed to 155, to match the studio's file, the automation remains attached to the 120 BPM grid. That is, the volume automation does not stay with the recorded signals. A YouTube thread indicates a solution for having automation move with tempo. It is to convert track based automation (TBA) to region based automation (RBA), and/or to "unlock the automation folder." But I haven't found any instruction on how to convert TBA to RBA, nor can I find an automation folder. I've tried simply cutting-and-pasting the volume automation (copying it from track-based and pasting into region-based), but this doesn't seem to paste anything. I've never used RBA and this is all new to me. I would indeed have thought that automation would move with any global tempo change by default. Under Functions, I have locked SMPTE, but this makes no difference: the automation stays immobile on the timeline while the audio expands outward as BPM is increased. I'm guessing there's a simple solution. Hope so! Many thanks.Reply