I am really happy to report I've discovered something in the sense of a root cause :)
On a hunch, I checked out and recompiled this commit. Now, this particular VST3 plugin's patch is persisted as I'd expect. Interestingly enough, some parameters do not persist (global volume) but others do. That curiosity aside, being able to persist patch selection is obviously fundamental so this is a win.
It does not solve the other IOT instruction crash I reported but I work around that by ensuring I disable the plugin before I save and exit Qtractor. I use automation to activate it before the part plays so this is fine.
So basically, 55c7d1335c34d10ebd76733c679d248af567e860 is the commit that introduced the inability to persist patches from this author. The odd thing is, other VST3 plugins I have do not appear to be impacted in this fashion which is why I mentioned what I knew about these MONSTER plugins and how the author seems to develop them in what I deems as "a very strange way". In other words, they are clearly not "standard" in as much as that word actually means anything. I also have a suspicion the "developer" would have no idea as he says there is no source code.............. uhm, yea.
I am really happy to report I've discovered something in the sense of a root cause :)
On a hunch, I checked out and recompiled this commit. Now, this particular VST3 plugin's patch is persisted as I'd expect. Interestingly enough, some parameters do not persist (global volume) but others do. That curiosity aside, being able to persist patch selection is obviously fundamental so this is a win.
It does not solve the other
IOT instructioncrash I reported but I work around that by ensuring I disable the plugin before I save and exit Qtractor. I use automation to activate it before the part plays so this is fine.So basically, 55c7d1335c34d10ebd76733c679d248af567e860 is the commit that introduced the inability to persist patches from this author. The odd thing is, other VST3 plugins I have do not appear to be impacted in this fashion which is why I mentioned what I knew about these MONSTER plugins and how the author seems to develop them in what I deems as "a very strange way". In other words, they are clearly not "standard" in as much as that word actually means anything. I also have a suspicion the "developer" would have no idea as he says there is no source code.............. uhm, yea.