If anyone can provide a reproducible scenario, we will fix it. If the program exits ordinarily, there is no way in the code this could happen.
Yes, it’s easy. Open VST Live with any project with multiprocessing enabled in the settings, and let’s say you need to open another project from within the running program.
After loading, 100% multiprocessing will be disabled in the settings! I’ve described this more than once, but what’s the point?
I’ll leave it at that. I don’t care about any bugs anymore. I’ve uninstalled VST Live, so you’ll be fine.
That was the missing link, thanks for providing a way to reproduce.
The report was that the MP setting was deliberately disabled when starting VST Live (which only happens when loading two projects in between), and that was what we were examining thoroughly. That very important step was missing. Anyhoo, will of course be fixed with the next version.
Background: MP is disabled when loading a project and (should be) re-disabled after loading was finished, the bug led to preventing the latter from beeing executed.
It looks like the problem (MP preference resetting) can still occur.
This was indeed a double trap, there is a timeout to prevent user from toggeling MP too fast, which leads to problems. When debugging this case, the timeout never stroke, but with release - and if the newly loaded project is not taking much time to load - the setting still was not restored. Finally fixed with the next update, sorry for the inconvenience.
Thank you, this is good news, and what about the artifacts in the sound, when will this issue be resolved?
All but you report it’s fixed. We could reproduce the issue with your project, but no more after the fixes. In addition, we are still improving and will offer that soon, but artefacts should no longer appear as of now.
VST Live Pre-Release 2.2.117 had artifacts, and they didn’t go away. I didn’t test VST Live Pre-Release 2.2.118 because I don’t have VST Live installed at the moment, I deleted it. Perhaps you forgot to add layers again when checking, or multiprocessing was disabled in the settings, it turned off on its own.
Don’t pay attention to the laudatory reviews of some users Artifacts in the sound with multiprocessing enabled in the settings - #39 by Cucuso , I would understand if he had met all the conditions described in the first post… but this is absolutely not objective and only confuses, it supposedly works for him (possibly within the framework of his specific project).
testing with 3.0.38
I don’t have version 3, only 2, but now I specifically installed 2.2.118 and wasn’t too lazy to check it (even though it’s really it drives me annoys), I can report that everything is still cracking!!!
And this is what they call fixed??? Although I’m not surprised. And even though I don’t have version 3.0.38, I’m more than sure that it doesn’t work there either…
And this is a completely new project created today, because I deleted the old ones together in VST Live
Here’s another example of artifacts that you supposedly fixed… different from the one described earlier. I accidentally discovered today that this combination also produces crackling.
I simply added an audio click track, and I didn’t even need to send audio in the mixer or create layers. And if I delete the click track, there’s silence again—no crackling! Watch the video, and I’ve also sent you a new test project file in a private message. You can verify this yourself: the crackling is already present, even though the click track is muted. Of course, it’s possible that for this bug to manifest on your machine, you’ll need to resave the project.
And the tested version of VST Live 2.2.118
Thank you, will check again.
We can reproduce it and are evaluating, thanks for the project!
Now you have two of my projects with different approaches to this artifact bug. I’d really like to see results and finally fix it! Just be kind enough to test both versions yourself before releasing them, before you claim you’ve fixed it… so that such ridiculous answers don’t arise later
Because I sit and describe bugs and spend my time on this, so that they are properly formatted, not to see such answers…
I had hopes 
You have no idea.
Anyway, we found the (second!) problem with your (new) project and could fix it. Thanks again for your help, we worked very very hard on this, maybe we can get to a friendly understanding after all.
Yes, I’m definitely not your enemy! Otherwise, I wouldn’t have even tried to help and would have long ago withdrawn. But I don’t abandon unresolved issues halfway through. I’m used to seeing any task through to its logical conclusion, just like with the VST Live export and import from Cubase. I also fought with you for six months until you finally got it done! But the end result is more important when it works! And I always respond with gratitude when the issues are closed and everything is fixed.
Great thanks
I checked VST Live 2.2.119, and there are no more artifacts in the sound!!! Thank you!!! for the great work you did to fix this bug. The issue is resolved, so I’m closing this thread.
Once again, I bow deeply to you in gratitude.
Glad that it finally worked out, thanks once more for your help!