Ableton Automation Lane Bug - VST3 - Re-enable Automation - Automation Lane Greyed Out

Audio Plugins
1

Hey, I noticed a Bug, while testing my Plugin (VST3i). I closed ableton per Xcode’s stop (as my debug executable) and when i restored the project, the automation lane was greyed out and the re-enable automation button was lighting up. But the grey automation lane was still working, i could change the automation and the change was audible. The re-enable button does not work and the dottet red automation lane was not usable.
I screenrecorded it and uploaded it to my cloud because the file is to big for the forum: Proton Drive

I found some simliar posts like this, but they all seem to be a little different.

I have no idea if it’s an Ableton Bug, or a JUCE one or something is wrong in my Code. Maybe somebody has an idea?

Don’t now if thats relevant, but pluginval had no problems with saving and restoring parameters.

2

The video shows 2 knobs automated/moved while the Ableton view shows one lane visible.

Are you doing any changes to one automation based on the other?

https://help.ableton.com/hc/en-us/articles/209069409-Re-enable-Automation-keeps-lighting-up

If you’re trying to do “meta” automation (meaning change one parameter based on another) it might trigger that behavior.

3

Hey thanks for your reply. No i just automated the waverform and filter cutoff individualy and both don’t trigger other parameter changes.

4

Sadly, without any code snippet we can only guess.

I’d suggest simmering down piece by piece to first figure out the cause.
Another useful hint would be when you send or receive automation parameter to log the thread it was executed on to ensure no racing is happening.

1 Like