If you read carefully and watched the video, what a load!
One insert in the stack. You don’t even have to insert effects in the mixer, just send to empty GRUP channels.
Three layers with Halion, and it’s already crackling from just one layer! Oh yeah, and another audio track without effects.
Is this really a load? That’s ridiculous. My CPU load is at 2%.
This means the audio engine can’t handle it, or there are some issues with the mixer.
But I know one thing: this definitely shouldn’t happen!
And even if I just create a new project, there are no artifacts! They only appear after a restart and saving, so it’s definitely a bug; otherwise, everything would be cracking and the artifacts would be there right away!
Here’s a new project starting from scratch.
Multiprocessing enabled!
Audio track
Stack
25 Layers, even
2 sends to empty Group channels
No problem!
Close and save, open, run, delete layers, and add 3 layers. All the artifacts are very audible. We reduced it to 1 layer and they’re still there!
The problems only appear after restarting the VST Live.
video doesn’t help, do you have a project with “off the shelf” plugins?
I sent you a test project in a private message.
And let’s move on to another topic in which I have already laid out everything in detail.
Thanks for the project! No artifacts yet but still looking closer.
But what is different about that topic? And what is it about anyway - title says “option gets deselected” but that’s not what this is all about, or?
it’s not important right now. I’ve written everything in a private message.
And everything regarding artifacts in sound is described in detail here This is the only thing that matters in this new topic Please move to this topic)): Artifacts in the sound with multiprocessing enabled in the settings
Check your personal email, I’ve added some information for you!
Hello! Were you able to reproduce this audio artifacting bug? All you had to do was open my project, close it, and save it. Then reopen it! Add 3-4 layers, and press play! You should see some crackling (distortion) in the audio.
We can reproduce the problem and are working on it.
We have narrowed the problem but the fix can‘t quite make it for todays version, but certainly for the one thereafter, incliding some performance improvements with multi processing. Once more thanks for your help!
Excellent! There’s no need to rush, and no one demanded this be done by Friday. The main thing is that the problem is now clearly understood, and we’ll wait for this fix and improvements! It took longer to prove it existed than it did to fix it.
Thank you! Sincerely, Sergey
Please try again with the next version. At least with your project there are no more hiccups. Thanks once more for helping!
Thank you, I will definitely check everything!
I can report that the artifacts are still there. You apparently forget to delete layers. If you save them with the project (they’re not there by default), the artifacts aren’t as audible, but they’re still there! And as soon as you delete the layers and add everything, the artifacts are still there. So, no miracle happened… the problem still exists… You have a testing method in a private message; I haven’t changed anything, it’s the same project.
Or read everything here, step by step: Artifacts in the sound with multiprocessing enabled in the settings
I thought the problem had gone away, but it turned out to be the multiprocessing feature in the settings turning off on its own again, another bug that still exists.
check next version (today9 and let us know if all works out for you.
I tested VST Live 2.2.119, and the multiprocessor in the settings no longer disables itself, even when opening another project or creating a new one.
I’d like to express my gratitude! Thank you!!! 
Everything was fine, even when opening a project from the menu of an already running program or creating a new one.
But when exporting from Cubase, after importing into VST Live, after saving and rebooting, I noticed that the multiprocessor had been disabled automatically in the settings.
but I’ll keep watching and maybe I’ll figure out the pattern, then I’ll add more
Correct, sorry, should be fixed with the next version.