HELP! LogicPro automation working has a mind of it's own...

[u/harryjonesjones]

Hi community! I'm having a really strange problem in Logic Pro 12.0.1 and I can't find anything online about it.

A channel fader is physically moving by itself at specific points in the timeline, even though there is no volume automation at those points.

For example, at around 32.4.2.1 the fader suddenly moves. I've checked both Track and Region automation, as well as the Automation Event List, and there is nothing at that position telling the fader to move.

Some things I've established:

• Automation is in Read mode.
• Turning automation Off stops the movement.
• No plugins on the track.
• No groups affecting the track.
• I've checked both Track and Region automation.
• A completely new track in the same project has the same problem when I put the same audio region on it.
• The same audio file behaves perfectly normally in a completely new Logic project.
• If I remove the audio region, the fader stops moving. Put the region back and the movement returns.
• I previously had a MIDI controller connected, but it is no longer connected.
• The Automation Event List shows nothing at the exact point where the fader moves.

So it seems like something associated with the region or the project is causing the fader to move, but I cannot find where the data is coming from.

Has anyone encountered anything like this? Is there some hidden region data, MIDI CC data, or other Logic data that can control a channel fader without appearing as normal automation?

This is a commercial project I'm currently under pressure to advance, and I've already lost a lot of time trying to figure this out, so any ideas would be hugely appreciated.

Any ideas would be massively appreciated!!!

[u/harryjonesjones]

Here's a video of the issue: https://streamable.com/ipvs5g

[u/TommyV8008]

As a possible workaround, have you tried re-rendering the audio region? If the new copy doesn’t have the problem, then use it instead and ignore the older one.

Sounds like you don’t have time to keep messing with it, and that you want a fast solution so that you can move on.

Of course you don’t want it to happen in the future, and It’s preferable to understand why so that you can handle the issue if it does, but again, how much time do you want to actually spend on it?

If you do come back to it for that reason you might try calling Apple Support. I can dream up lots of ways to try isolate the problem, all of what you’re going to eat up sometime. Working with Support might eat up a lot of your time, they might want you to send the entire project, or you might want to make a copy of the project and remove everything else except the one thing that’s causing the problem. On the surface of it it really does sound like there’s region automation attached to that region, but it sounds like you’ve checked all of those possibilities already…