I have no clue. Haven’t necessarely imported a project to disable the function 
But if it works in the next version I hope that this issue will be solved 
As I understand it, the OUT channel with the MAIN output is essentially like a bottle with a narrow neck (main). When multiprocessing is enabled, the layer, audio track, and stack begin to struggle to see who will be the first to exit this bottleneck, which results in artifacts (crackling and the like).
But if each channel has its own output, then there’s no conflict; everyone goes their own way without pushing each other.
Although, on the other hand, the same Cubase has many more tracks and easily copes with this task even with the ASIO Grid disabled.
Sorry, that is entirely wrong.
We explained it before, so here it goes again: only audio processes (Layers, Stacks, Modules, Tracks, Channels and their inserts etc) that are entirely independent from others can be processed in parallel.
As an example, 100 Layers can be processed in parallel, but after that, if one or multiple have Sends to Group channels (example), the Group channels cannot be processed until the sending channels (here, Layers) have finished their work, and that continues down any such chain. So some configurations (those highly independent from others) will benefit big time, while others will not. And there is always some overhead to schedule processes and keep track of said independence.
The scheduler will always keep track to never have depending processe in parallel, otherwise ther would be much more significant problems.
Right. But only until the next brickwall (input not finished) is hit.
2.2.82 ‘Problem’ still exists… VST Live didn’t crash when I latest activated the function…
2.2.82 multiprocessing does not save its state when enabled, after any reboot it turns off, rolled back to 80
2.2.83 is the same, multiprocessing in the settings doesn’t save the enabled state. I don’t see any point in checking anything further; I’m rolling back to 80.
Sorry, you are correct. We broke it while fixing it, when it was reported broken (it wasn’t)…fixed with the next version.
The only version where it didn’t turn off was 2.2.80.
But there’s also a crackling sound if you add three layers with a HALion Sonic, one delay, and a guitar rig (7) + a backing track on one track!
We add layers and make one send from the stack to the delay, and then all the artifacts in the sound start appearing. That is, one MAIN output is no longer capable of handling such a heavy load (6 VSTs and one send).
But if we give each of them their own physical audio interface output, send it to layers 1-2, to 3-4, the stack with its groups and effects, and to 5-6 the backing track, there’s no crackling.
I wonder when this will be fixed!
Not everyone has six outputs on their audio card.
if it works with individual outs you probably have Multi Processing active, and then those pathes can be processed concurrently, that’s not a bug and nothing to be fixed. Else suspect a routing problem or insufficient resources. We could check for routing problems if you provide a .vlprj file.
So, with multi-processing enabled in the Vst Live settings, 1 stack with delay send, 3 layers with Halion, the backing track should produce this kind of crackling? So, is this normal? If so, the issue is resolved.
The routing is already visible in the video: all outputs are routed to the stereo output, and yes, the R9 5950x (16 cores) is only 1-3% utilized.
Please try to switch monitor on on one of the backing track and let me know if it stops! I have same problem with multi thread and it solves if I have a monitored track in tracks!
Hi! No, it doesn’t help. I checked. You already gave this advice. The only thing that helps is giving each one its own output. But that’s nonsense. Even if you turn off ASIO Grid in Cubase, there’s no crackling, no sound problems at all. Something weird with the audio engine or mixer. So, 6 VSTs are crushing VST Live, and it can’t process them all on one output, with the multi-processing option enabled?
Very strange, I can manage 50 more or less VST plugins, 8 stacks, tens of backing, in multiprocessing with no crackle, given at least an audio track monitored and routed to main out….
But I have no layers, no VST instruments, have you layers with VST instruments?
Nb: on win11 with generic asio and with umc1820 asio driver
Just trying to help. You ask questions but didn’t answer if there is a difference with MP on or not. Most probably it is a routing issue, or a plugin behaving differently than expected. Maybe try to replace the heavier ones with comparable ones to narrow the cause.
No, and that question doesn’t help either.
Send a project so we can check routing is all of the help we can offer.
Looking at PMs I see you did send some, don’t know if that should show the issue? It would help if you could send it again. Sorry, but there are just too many posts to handle while trying to actually do some fixing at all.
if multiprocessing is enabled, then there is a crackle, if you turn it off, I can create at least 40 layers and everything will be perfect, the sound is without artifacts. Or another way to get around this crackle is to ask everyone their own way out! the layers are all on one output, the stacks on the other, the backing on the third output. But the question is why I can’t do one way out without cracking! (where there are only 3 layers, 1 stack and a backing track already cause a crackle when the multiprocessor is turned on). I have sent the experimental project file https://drive.google.com/file/d/1TG5QsBv0d9K4JAzglYOehCldZxMteMkl/view?usp=sharing
I’m not demanding anything from you; maybe it’s supposed to be like this, I don’t know. But it should be described somewhere (in the instructions) that multiprocessing should be enabled in the settings provided you have multichannel outputs for layer, stack, backing track, microphone, and so on. And enabling it using just one output is not recommended; it should look something like this…
Then perhaps stupid questions won’t arise… But until there’s proper instructions, questions will always arise!
Let’s update the topic
Let’s create a clean project, one stack, one audio track (backing track), and two sends to SONG GRUP from the stack. Multiprocessing is enabled in the settings!!!
Turn on playback and add layers on the fly. No audio crackling artifacts are heard!
Stop playback and delete the SONG GRUP with its effects.
And re-create two GRUP channels, now adding delay and reverb, and create two sends from the stack to them.
Turn on playback again and add layers on the fly. No audio crackling artifacts are heard!
Save and close the test project!
Open the saved project and launch it. And guess what? We’ve suddenly got artifacts in the audio that are oh-so-audible! There were no artifacts before restarting the project!!! So, this is really a problem with your audio engine or mixer that needs to be addressed.
Watch the video!
I even checked that I can delete and recreate them, and there won’t be any artifacts again! You can even leave these delay and reverb channels empty without any effects!
Just two sends to these channels are enough, and everything works without artifacts, but only until you restart the project.
I support. There is an artifact problem. Provided that the project is not heavily loaded.