Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Logic Pro 12.0.1 regional automation unpredictably changes track parameters and doesn't go back in empty timelines

I have been having trouble with the regional automation mode, especially the built-in gain plugin under utility. Sometimes my default parameter value of the track's plugin get changed by the regional automation and sometimes it does not. I have already clicked on both the "Regional automation takes priority over track automation" and "use present parameter value for regions without region automation" in the project settings. This is unpredictable behavior.


I also noticed a weird behavior where sometimes the parameter value goes straight back to the default after the a region with automation, but sometimes it doesn't until the next region without automation comes in? Shouldn't the parameter level be the default value in empty regions? I don't understand why sometimes there's delay of this.


Thank you very much. I'm on macOS 26.5.2 with logic 12.0.1.

2 replies

I usually don't mix Track Automation with Region Automation, I use either Track or Region Automation. That's why I don't have any "priority" issues.

Your second issue may happen because of the used automation mode. When set to "Touch", the automation slaps back to the default value, unlike "Latch" (or "Write").

Thanks for the reply!


I'm not mixing track w region automation together. The issue I have is the default value for some of my regions get changed by other regions in a random way, even with the two setting mentioned selected (they helped but not every time). And in the second case they are all in read but doesn't slap back and changing the mode did help unfortunately ; ;


One thing even weirder I just noticed is, I copied the track where the automation would slap back after the region. But the copy doesn't behave the same way, instead it stayed on the last value of the previous region during empty timelines. At this point I believe it's a bug.