I had the same issue in FL studio.
My workaround is to comment out the audioProcessorParameterChanged callbacks in AudioProcessorParameter::sendValueChangedMessageToListeners in file modules\juce_audio_processors\processors\juce_AudioProcessor.cpp (line 1441):
void AudioProcessorParameter::sendValueChangedMessageToListeners (float newValue)
{
ScopedLock lock (listenerLock);
for (int i = listeners.size(); --i >= 0;)
if (auto* l = listeners [i])
l->parameterValueChanged (getParameterIndex(), newValue);
// audioProcessorParameterChanged callbacks will shortly be deprecated and
// this code will be removed.
/*
for (int i = processor->listeners.size(); --i >= 0;)
if (auto* l = processor->listeners[i])
l->audioProcessorParameterChanged (processor, getParameterIndex(), newValue);
*/
}
Would be great to see a fix soon. The current release is unusable for plug-in developers because of this bug and i want to use the great new 5.3 features
I’ve been waiting on this one as well; just built my plugin against the latest on develop, a632b57e7, looks good here too. Tested VST & AU in Live 10.0.1 on OS X 10.13.
I’ve found a new way to resurrect this issue. In a pretty simple test the orange light of doom illuminates whenever I put in a call to updateHostDisplay, such as I may do when a parameter name is updated, which seems like a strange reason to knock out automation.