Preventing unwanted track automation changes

[EGEmedia]

I am using a PreSonus faderport as a control device for track automation in Auditon CC 2019. The device works fine but I am having a nightmare in that I can mix a scene, move onto the next scene and when I go back I find that the mix of my first scene is all over the place. Is there any way of locking a section of keyframes, or am I using the wrong mode? I first tried using Touch mode which I think was probably not the best idea, so switched to using Write mode, which should only make changes to the section being played but I am having the same problem.

If you use a control device what is your workflow to ensure that what you have mixed stays mixed!

Thank you.

[ryclark]

Have you tried the Latch mode? It supposedly only starts recording new automation when you make your first adjustment and stops when you stop playback. Thus it should only start adding new keyframes when you actually first move the fader after you started playback.

[SteveG_AudioMasters_]

The other thing that could potentially help you is to look critically at the Keyframe Automation settings. Thinning out the data can leave you with perfectly good automation, and rather fewer unnecessary frames. Aside from any other considerations, this will also reduce the size of your session file somewhat!

[EGEmedia]

I don't think that's the cause of my problem but will have a look at those settings as automation does generate an excessive number of keyframes. Thanks for responding.

[EGEmedia]

Thanks for the reply. I hadn't tried latch mode but I've been doing some tests on a dummy project and latch mode and touch mode seem to do the same thing. I can't spot the difference anyway. Write mode will over write any keyframes with the position of the fader, over writing with the starting position if the fader isn't moved so that might be the dangerous one

In tests I've been unable to replicate the problem I'm having in my project.

[EGEmedia]

For anybody else trying to get their head around these various modes a good tutorial here

Audition CC tutorial: Using the mixer for track-level automation | lynda.com - YouTube

From this, I think the reason Touch and Latch work the same using the Faderport is that Audition doesn't know whether I am touching the fader or not, In touch mode releasing the fader returns automation to follow existing keyframes but Faderport doesn't provide that information.

[ryclark]

That seems a bit odd because the spec for the Faderport says that the touch sensitive fader supports both Touch and Latch. Maybe worth pursuing on a Presonus forum? Or maybe one of Audition's Devs might chime in, except I believe that they may be on holiday this week in the US.

[EGEmedia]

It feels as if it might have a microswitch under the fader knob but it's not doing anything. There's also no Latch mode button on mine ( the original version ).

Anyway I think I have just found the problem, I did a "Ripple Delete" on another track and track automation dissapeared on a completely different track. Undo the Ripple Delete and keyframes come back. I will avoid Ripple Delete from now on on on this project!

[EGEmedia · Accepted solution]

This is what has been happening...