Hey guys -
An edge case issue here, where setting the param (via setParamNotifyingHost) can cause an infinite loop in AAX plugins.
Since it’s in code marked as “will be deprecated” in Juce, I just commented it out and don’t see any negative side effects so far.
Anyway, just letting you know.
It’s only in AAX, and it seems only to happen when I set the param value from a thread other than UI (basically, I have a worker thread that changes a couple values in certain cases).
More generally, I’d love to know why we have these two listener systems, are they both needed / used for some DAWs? Why send parameterValueChanged, and then audioProcessorParameterChanged?