Is there any way to tell if a preset is being loaded as opposed to a session? If we can detect that, then when loading a preset into an existing instance of our plugin, we can load only the parameters and other things that presets would affect, and skip over saved data that was generated from “analyzing” the audio data prior to loading the preset.
We have VST3- and AAX-specific code to do that in our pre-JUCE plugins, but I don’t know if there is a way to make that distinction in JUCE. If not, then users will lose any analysis work they’ve done prior to loading the preset, and will have to clear the old data and re-analyze to get it back.