Just discovered this long thread started by @yfede and followed-up by @fabian:
I’m not sure if I understood all the great detective work + details I read in there, but did I pick up correctly that Cubase will simply refuse to supply a plugin chunk saved with plugin version 1.1.2 to a currently installed plugin with version 1.1.1? (talking about plugin version, as I don’t think we ever explicitly set a chunk version)
That would mean that if a user upgrades a plugin to a later version, saves his project, and then decides to go back to a previous version of the plugin, he is basically screwed, as his project won’t load the plugin’s settings any longer. And is this then for any version number change, including minor or maintenance version number changes?
It’s strange that the old plugin version 1.1.1 shows as 0.1.1.1, and the new plugin version shows as 1.1.2.0 (even though only the maintenance version number part changed).
Perhaps relevant: the old version was built with Juce 2.1.1 (back in July 2013…) and the new one with Juce 5.3.1.