Understood.kv331 wrote: Mon Nov 04, 2024 3:31 pm Just because it is happening for you does not mean it is happening for the other users. Otherwise we would be flooded with support emails (There are currently 8000+ distinct registered users who installed SynthMaster 3 on Windows and MacOS) Something is clearly different in your system. I tested many times, but can not reproduce so far on neither Windows / MacOS, VST2/VST3/AU.
However - have been a fan of your products for both v1 and v2 and was stunned to see how difficult this was. And while I do not have a video handy as the other user did earlier in this thread - the behavior is the same.
I have been doing DAWs for 20+ years - rarely have I come across an oddball issue I could not solve - but this is one of them. Trust when I tell you I really tried.
Finally - just because the issue is not being reported on a wide scale - does not mean it does not exist.
And unless you are testing with my specific baseline - Windows 10 22H2 running the VST3 inside of Studio One 6.6.4 - you have not tested it fully.
Now - this setup above is NOT my usual test bed. I always do my "pre-work" for Synthmaster (updating expansions, setting defaults etc) in the standalone version and then bring it in as a VST.
But since your installer (on Windows 10 anyway) failed to properly install shortcuts for the standalone - this was my only option. And perhaps the strange method described above - is contributing to this issue.
I have no skin in this game or any reason to make this up - have plenty of other synths I can use - but I can tell you there is an issue. Loading presets correctly (and quickly) should be priority item #2 - right after priority item #1- which is loading the plugin.
VP
