This comparison can break when relaxing IEEE compliance and enabling
full optimisations.

On some platforms, the superclass implementation can throw if it detects
that the preset data is malformed, but it's not clear exactly how the
system determines this.

We now apply only the JUCE state.

JUCE no longer depends on built artifacts of the AAX_SDK

Opening some JUCE VST3s in FL Studio's patcher can cause crashes because
of data races on objects accessed from setActive() and process().

According to the VST3 specification, these functions should never be
called simultaneously, so I think this is a bug in FL Studio.

This can be tested by toggling 'Distortion' on and off in the
DSPModulePluginDemo, and checking the latency reported in the node
statistics in AUM.