It's very, very random. In my experience it happens... well, frequently enough to willingly end up with 40GB of copies of what is fundamentally the same 1.5GB file, but not quite frequently enough to really be a Buzz-kill (sorry, couldn't resist that one ). I consider myself reasonably good at reproducing bugs, but reliably reproducing this one continues to elude me.polac wrote: ↑Mon May 31, 2021 10:09 amI cannot reproduce it with Serum here, songs are loading fine, but i'm doing not much songs lately. I have also some Valhalla stuff installed here to test.I've had this with Valhalla suite stuff and with Serum, which is a non-JUCE VST. So it's not JUCE-related, as far as I can tell, but it is plugin-specific - I think. I've never had the issue with Brainworx stuff, for instance, and to the best of my recollection it's never happened with Surge.
I do have some project files after the bug has triggered, not sure if there'd be anything terribly illuminating in them though - to all appearances, it's just as if there's a brand-new VST with the default patch. If you're interested, let me know and I'll try to find some.
I've tried disabling Load/Save in GUI Thread in the past, and as far as I can tell it has no effect - however, for some reason it seems like the Load/Save checkbox isn't "sticky" - regardless of whether or not I have "run in separate process" ticked, Load/Save always defaults to ticked in a new instance of Serum, and I definitely can't remember to always tick it when doing a new project.
(However, Async Load/Save in the CTRL-ALT bridge popup does remember whether I've checked it or not - this is the same as Load/Save in GUI Thread, just a different label, right?)
And I'm sad to hear about the lack of songs lately... hopefully that's just a temporary dry spell, all the work you put into making Buzz fun for others to make music in should come back to you tenfold.
For me, it's VST2 - I use VST2 whenever possible.