Artifacts in the sound with multiprocessing enabled in the settings

Greetings, developers!
While you haven’t responded to this thread ( The multi processing option in the preferences (audio page) sometimes gets deselected here - #61 by sergeantt67 ), I decided to conduct another experiment and add more information on this issue.
This issue has been around for a long time, and all users experience it to some degree. Let’s create a new project:
1 track with a backing track (24/48 Wav audio file)
2 The stack is empty! (No VSTs, not even in the mixer section!) Just set it to an audio input.
3 In the mixer, create two group channels (also without a single VST insertion!)
4 Make two sends from the stack in the mixer to these group channels.
5 Add layers; I added as many as 25 of them.
6 Press play and hear that the audio track sounds CLEAN, without artifacts!
7 Save and close VST Live
8 Reopen VST Live and the test project we saved!
9 Once open, delete all the layers we created.
10 Turn on Play.
11 Add 3 layers.
And out of nowhere, we’ve got artifacts, and this is essentially in an empty project!!!, where there’s not a single VST except 3 HALion Sonic!!!
So, this is definitely your problem, or something’s wrong with the audio engine, or you’re having problems with the mixer!
Either way, this needs to be fixed!!!
Watch the video!

Moreover, the artifacts only appear after restarting and saving the project! You can delete the group channels in the mixer and recreate them, and the artifacts will disappear! But only until you restart VST Live.

And this problem only concerns Group channels in the mixer

Снимок экрана 2026-03-14 131046

If you use SONG GRUP Снимок экрана 2026-03-14 131055, there are no problems with them, even after restarting the project! At least in version 2.2.105

1 Like

The topic of artifacts is generally relevant. with a fairly low processor load of 3-4%. Artifacts sound like when the processor is throttling. It’s worth noting that I noticed when starting the project. And in general, using the program takes up a lot of RAM. which is quite strange. PC has to make a large swap file.

1 Like

What’s your ASIO buffer size?

Hi! Yes, this happens with any buffer size from 64 to 256. And the buffer size doesn’t matter in this context! Because artifacts only appear after saving and reloading. They are NOT present in a newly created project until you save and reload it!!!
If you use SONG GROUP, you won’t have any problems! At least in version 2.2.105
Moreover, artifacts only appear after restarting and saving the project! You can delete group channels in the mixer and recreate them, and the artifacts will disappear! But only until you restart VST Live.
If you watched the video carefully, the project is practically empty: a backing track and three layers with a halion! And an empty stack with only an input assigned, which in the mixer makes two sends to two group channels (which don’t even have inserts from VST). And the CPU load is at 1%!!!

I anticipate more questions! I’ll answer right away: There are no artifacts as soon as we create the project!
The bug only appears when saving and reloading the project!
Better yet, try reproducing it yourself and then ask questions.
Or write that I don’t have such a mistake, but only on the merits, without going off-topic, otherwise the developers will suffer reading unnecessary questions and answers.

1 Like

Hi Anton! Please give real-world examples, not generalizations.
Describe the conditions under which they occur, but be specific! Developers aren’t good at guessing; they need facts and steps to reproduce a given bug!

Sorry Sergey - I meant Anton - I knew you would have experimented with the buffer.

1 Like

That’s all correct! But the logic is simple: with multiprocessing enabled, VST Live is able to work without audio artifacts until a reboot! This is definitely a BUG!

In any case, if anyone has problems, it’s best to write them down point by point, and the sequence of actions you took when you encountered them!

Many people, faced with this noise, simply stopped using multiprocessing and disabled it in the settings! But we need the truth, not temporary fixes!

So coming back to your original post and video - does the same happen if you remove/add layers while in stop and then hit play?

Hi again! Do you mean in the second part of the video, after saving and reloading, that I add 3 layers on the fly? It doesn’t matter. You saw the 25 words of adding on the fly in part 1. Did you hear any crackling sounds? There isn’t any and there never will be.

I mean your step 10. If you do not hit play before adding the 3 layers?

Here you go, opening a saved project to dispel your doubts. Play after adding layers, the crackling sound is clearly audible.

If I understood you correctly, you wanted to see this, add layers, and only then launch it?

Or if you don’t add them at all? Then everything will be fine, there won’t be any artifacts.

Well, no layers please)

I even reinstalled a clean Windows system just to make the experiment purer.

Thank you. So why add the fact that it is playing while you add layers? It is immaterial and confusing the issue.

Is everything clear now, or is there something else that needs to be added?

Just that the simpler the description, and the minimum steps to reproduce the problem makes it easier to diagnose the issue. :grinning_face:

If only Google Translate translated more accurately)) Otherwise, you write something, and when it translates it, you wonder: “Did I really write that?”:rofl:

1 Like

Are you sure that using multiprocessor in VST or FX is disabled? Because if not it makes a mess… but it’s not VSTlive, it does it with any software. That’s why I have multiprocessor enabled on VST (some are enabled by default) and disabled on DAWs.

I’m sure, and it seems you didn’t pay attention, there are no FX in this test, a completely empty project, except for an audio track and three words with Halion. Oh, I forgot, there is also a stack, but it is also empty, only the audio input and two sends in the mixer to empty group channels are assigned to it. Also, no problems arise until the project is reloaded and saved. So, it works without artifacts before reloading, but not after can’t ?:rofl: :rofl: :rofl:
Okay, we can even delete the group channels if we hear artifacts and immediately recreate them, and there won’t be any problems again. But only until the reload! So these are definitely mixer or audio engine issues—it’s simply a bug!

And yes, I specifically removed all VSTs from the mixer and stack so there would be no reason to say that a third-party VST (especially when that VST is from a different manufacturer) is to blame! For us, it’s a black box, and we don’t know what’s going on… the developers’ favorite excuse.

Hey @sergeantt67,

I’m a little away from my music computers, but can you test if when the artifacts are introduced, “reset audio devices” then changing buffer size (any value, doesnt matter low or high) once or twice fixes the problem?

I have been having some high cpu/artifacting after reloading project or editing (MP enabled) and this was the way that was fixing it.

I wonder if they are related.

1 Like

I turned it on today and thought the problem was gone, but no, it’s still there. For some reason, multiprocessing was disabled in the settings :rofl: (this is also a bug that’s been described many times, where multiprocessing randomly disables itself).
It’s still a bug, so I shouldn’t have been so happy.

Yes, besides deleting group tracks, that will disappear, but only until a reboot. Your advice about resetting the audio device in the menu also works, but only until a reboot!
But these are all workarounds, not a solution! I don’t need software that can’t even output sound without artifacts!