Automation playback issues

[jacintorecords]

Hi all, long time lurker, first time poster.

For a while I've been having issues with automation when using non-MOTU plugins.
I can record automation fine with any plugin, but when playing back, MOTU plugins work great yet all 3rd party plugins are super buggy and only play back correctly when I rewind to bar 1 (RTZ, as they say). Besides automation, all plugins work perfectly.

I tried running plugins as AU as well as VST 2 and 3. I tried erasing preferences (com.motu.DigitalPerformer.plist as well as com.motu.DigitalPerformer and com.motu.MotuAudioSystem folders). Problem persists.

Tried with and without Rosetta mode, problem persists. Tried with Waves, UAD, UADx, Plugin alliance, same issue across the board.

I opened DP in safe mode, quit, reopened DP: problem persists.

I'm running DP 11.34 (had same problem on at least the last 3 or 4 versions of DP11).
MacBook Pro M3 Max
OS Sonoma 14.1.2.

If anyone had a similar issue or can shed some light, I'll be very grateful!
I'm considering upgrading to the latest OS but I'm worried other things will break in the process.

[mikehalloran]

all 3rd party plugins are super buggy and only play back correctly when I rewind to bar 1

When this happens, it's because only the changes are being recorded. It's not a bug if the plug-ins do not output continuous data.

[jacintorecords]

Thanks for your reply.
My issue is when playing back automation data that’s already been recorded (or penciled in).

Unless I’m rewinding (with the rewind button only, not stating the wiper) and playing back from bar 1, no automation info is read by plugins, including bypass on/off.

This wasn’t the case in the past, since I started using DP in 2006.

Am I missing something?

[mikehalloran]

Thanks for your reply.
My issue is when playing back automation data that’s already been recorded (or penciled in).

Unless I’m rewinding (with the rewind button only, not stating the wiper) and playing back from bar 1, no automation info is read by plugins, including bypass on/off.

This wasn’t the case in the past, since I started using DP in 2006.

Am I missing something?

Yes, you are.

We can see Volume and panning and other continuous data in DP If we want. Anywhere we go, DP will find that. MOTU plugs output it as well.

Many 3rd party plug-ins do not output continuous data, only changes can be recorded. When that happens, there’s no point of reference if you don’t start from the beginning. If the command only says 30% louder and you didn’t start from the beginning, 30% of what? I don’t know how else to explain it.

This subject comes up every few years in just about every DAW and notation forum.

[CharlzS]

Maybe Event Chasing? It's in the Setup Menu. Try Set All.

[jacintorecords]

Maybe Event Chasing? It's in the Setup Menu. Try Set All.

Tried it, didn't fix it.

Yes, you are.

We can see Volume and panning and other continuous data in DP If we want. Anywhere we go, DP will find that. MOTU plugs output it as well.

Many 3rd party plug-ins do not output continuous data, only changes can be recorded. When that happens, there’s no point of reference if you don’t start from the beginning. If the command only says 30% louder and you didn’t start from the beginning, 30% of what? I don’t know how else to explain it.

This subject comes up every few years in just about every DAW and notation forum.

I understand, but that shouldn't be the case with bypass status, which is binary, or if I pencil in 0% wet on measure 2 for a plug and then move up to 100% and down again. Automation is being written but is not read unless I RTZ. This hasn't been the case for the past 18 years using DP, and is not the case when I use DP11 on my colleague's computer. I'm certain something is buggy or I somehow messed up a setting. I used to automate Waves One Knob Filter everywhere and the automation would read perfectly. It's crazy to have to RTZ on a 2 hour film just to successfully have a plugin automate a move.

Do you Rewind every project to bar 1 every time you want to hear plugin automation? I would usually go back a couple of bars at the most and that was enough for DP + the plugin to "get their bearings".

Thanks again for your help. I might try an OS update next.

[mikehalloran]

I understand, but that shouldn't be the case with bypass status, which is binary, or if I pencil in 0% wet on measure 2 for a plug and then move up to 100% and down again. Automation is being written but is not read unless I RTZ.

No, you don't.

The plug is sending a change state. If DP doesn't know the original state, it can't execute the change. Not all plugs are like this, of course, including MOTU's but it does save resources.

Again, this is a decades old issue. Usually, it shows up on Finale user boards, however. "How come (...) doesn't work unless I start playback from the beginning?"

[HCMarkus]

My issue is when playing back automation data that’s already been recorded (or penciled in).

Unless I’m rewinding (with the rewind button only, not stating the wiper) and playing back from bar 1, no automation info is read by plugins, including bypass on/off.

I'm feeling pretty sure that the recorded plugin data is an absolute reference. I'll be out in studio later today and will check and respond with my findings.

I don't recall having had any issues with automation of plugins, regardless of manufacturer.

[HCMarkus]

Fab Filter EQ3 responds great to some random moves... Click anywhere on the timeline and FFEQ3 immediately jumps to the appropriate settings at that point in time. Here's the recorded data:

Screenshot 2025-05-04 at 1.34.29 PM.png (30.42 KiB) Viewed 923 times

[mikehalloran]

I don't recall having had any issues with automation of plugins, regardless of manufacturer.

It depends on the manufacturer. Eventide has never given me any grief on that. There was a rotary speaker that did but I don't recall who, anymore.

[jacintorecords]

I tried making automation changes in Ableton Live with some of the 3rd party plugins I usually use and they work fine, just like they used to in DP in the past. They also work on my colleague's DP, just not in mine.

I understand the "change of state" argument - it's not what i'm dealing with.

I upgraded to OS 15.4.1. it didn't help but fortunately nothing broke either

I appreciate everyone's help, will keep trying!

[HCMarkus]

Maybe reinstall DP...

Happy nothing broke moving to Sequoia. Same here; I just moved last week.

[mikehalloran]

If DP 11, MOTU does have tech support. Perhaps you can tell them what plug-ins are giving you grief, something you've not shared with us.

[jacintorecords]

Thanks, I’ll do that.

This happens with all non-MOTU plugins including: all of Waves (rComp, rVerb, the whole “one Knob” series, Waves tune, to name a few), all UAD and UADx plugins (1176, la-2a, atr-102, etc.), all Sound Toys (Decapitator, Echo Boy, Alter Boy, etc).