Multi Processing verbessert Performance aber führt zu Abstürzen

VST Live
1

Hi there,

I am working with the newest Version of VST 3 (3.0.10). The problem exists as well in 3.0.17.

Without Multi Processing enabled even a small amount ouf VST instruments leads to CPU spikes and audio crackles. With Multi Processing enabled the performance is way better without audio drops. However, when activated, on every song change VST Live crashes and after a restart it gets stuck on preloading.

Is this a known issue already and do you see a solution yet?

Best regards

Fabian

2

Hi,

sorry to hear that. Can you please check if crash-togs were created?

Windows : C:\Users\YourUserName\Documents\Steinberg\CrashDumps
Mac : /Users/Your_UserName/Library/Logs/DiagnosticReports

Do you see files named with vstlive. Please drop them here,
Michael.

3

Hi Michael,

thanks for your fast reply! I tried it several times. As soon as a click on a song, everything freezes and the window shows “no response”. It stays like this forever, the only thing I can do is click on the “x” to close the window and Windows shuts the process down. A CrashDump is not created.

Anything that I might missed? How can I enforce a crashdump/ log?

Best regards

Fabian

4

I tried to investigate a little more and it seems like there might be more that is broken.

I use EZDrummer and route each drum (kick, snare etc.) to different group channel for individual processing (eq and comp). With multiprocessing activated the plugin still processes all drums but all group channels except the kick remain silent. So it seems like the workload is spread across CPUs somehow but it is not working properly.

I also tried 3.0.17 again and as soon as several tracks with recorded audio kick in VST Live freezes as well and then crashes. This is independent of multiprocessing (same behaviour with multiprocessing on and off).

5

Quick update from my side: this issue still persits in versions 3.0.20 and 3.0.21. I know it might be a very specific issue. But do you see any chance to get a fix on this one? Is there any information I can provide you that might be helpful for this topic?

Best regards!

6

Have you tried increasing the ASIO buffer size?

7

Hi CliveJ,

Thanks for participating in the discussion!. Yes, I did indeed. As expected, this gives more “headroom” in terms of computing power and therefore decreases potential dropouts. However, the increased latency makes it unusable for live performances then. I aim for 265 Samples which is a good compromise between computing power and latency.

Following up on this thought, the next thing would be to buy a more powerful PC. But as as modern machines (especially portables ones) are optimized regarding multiprocessing, this might be the wrong approach.

It looks like VST Live has some issues with multi-output VST instruments (at least if you configure them to make use of this great functionality), in my case EZDrummer. I hope this can be resolved because it clearly is unexpected/ buggy behaviour.

8

265? I can run at 64 but settled on 128 - but then again I’m using an HP zBook Fury i9 windows Laptop. Plenty of headroom :grinning_face_with_smiling_eyes:
I’m surprised you’re having issues with multi-output given that Halion can m.o. and is included with VSTL. Maybe ezDrummer has its own issues.
MP is not always suitable - performance varies depending on your setup and whether the cores are real or “e” cores. If you have e cores I’ve heard it suggested that you should turn them off in the bios. I happily run without MP.