Ableton Forum

Anytime I use a Melda Production plug-in in a project, parameter envelopes become disabled when exporting or freezing. The only way to render those tracks without errors is to bounce them in real time to another track, or to map a parameter to a macro everytime you need to automate it.

I'm on the current versions of Ableton, Windows 10 and Melda plugins.

I see no other posts on this issue here, but in the KVR forums it has been reported and discussed for more than a year:

https://www.kvraudio.com/forum/viewtopi ... 8&t=490288
https://www.kvraudio.com/forum/viewtopic.php?p=6828485

Vojtech from Melda expresses frustration at the issue and wrote this last month:
"...for some reason Ableton Live disables automation when updateDisplay() is called, which is a call that lets the host know that the parameter names might have changed, so pretty much something unrelated to processing and if it was, it's no excuse to disable the automation..."

For users of Melda plugins and Ableton, this situation really sucks.

Can someone from Ableton please respond? Thanks.

This is not an official support forum, if you have a bug or issue you need to report, you should contact [email protected].

analog_rome wrote:Anytime I use a Melda Production plug-in in a project, parameter envelopes become disabled when exporting or freezing. The only way to render those tracks without errors is to bounce them in real time to another track, or to map a parameter to a macro everytime you need to automate it.

I can verify this in macOS 10.12.6 with Live 9.7.5 using the MSaturatorMB. I wasn't aware of this bug, so thanks for raising this.

disableton

Version 12 update: This issue seems to be gone with Melda version 12. Tried with MSaturatorMB.

I had the same issue with SoundToys plugins recently. Found the simple fix with help from their customer support - make sure your project sample rate is equal to or greater than your export sample rate. For example:

Project sample rate (Preferences->Audio->In/Out Sample Rate) = 44,100
Export sample rate = 48,000
AUTOMATION ERROR ON EXPORT

The fix...

Make the project sample rate = 48,000 or higher
Export sample rate = 48,000
WORKS

Hopefully solves the problem with other plugins as well.

mintheuniverse wrote: ↑

Wed Jan 06, 2021 5:16 pm

I had the same issue with SoundToys plugins recently. Found the simple fix with help from their customer support - make sure your project sample rate is equal to or greater than your export sample rate. For example:

Project sample rate (Preferences->Audio->In/Out Sample Rate) = 44,100
Export sample rate = 48,000
AUTOMATION ERROR ON EXPORT

The fix...

Make the project sample rate = 48,000 or higher
Export sample rate = 48,000
WORKS

Hopefully solves the problem with other plugins as well.

This fixed it for me! Thanks heaps <3