Hi there.
I am using a Windows 11 PC with 16GB of 3200 DDR4 ram and an I5 12500 6 core processor.
I’ve been using Cubase Pro 12 as my live performance DAW with my band for a few years now (since 8), processing in realtime 4-6 live vocals, 8 drum channels, 2 guitars with Neural DSP plugins in stereo, bass, synths and non realtime backing tracks.
This is what my CPU usage looks like with all channels monitor enabled and playing 22 voices on Halion Sonic 7, throug an RME Digface USB @64 samples:
VL cpu meter stays around 30%, but only one core at above 80% while the other are mostly unused.
Lots of clicks and pops.
Does VST Live not support multi core processing? I was under the impression that the audio engine is the same as Cubase and would take advantage of all the processing power available.
I should probably add that I generally set the buffer @128 to have enough headroom, Cubase never glitches but VSTLive does make a click or pop every now and then.
Multi core support should be moved to the top of the priorities.
What’s the point of getting the latest greatest CPU for live use if it’s not getting used properly?
The lack of MC also explains most of the complaints I’ve read here about clicks and realtime useability. Everyone that has problema with VL not handling the same project as X or Y DAW can blame it on this particular point.
And lastly, the CPU meter should also be updated, as it is not displaying real world CPU usage numbers (seems it’s displaying average CPU usage when in reality the single core being used is around 90%), now I understand why I am getting low performance even though the meter is in a reasonable range.
The CPU meter (like in Cubase) shows audio processing time used in relation to available time as given by the audio blocksize (latency), and sample rate. It is slightly averaged.
Basically, we have multicore processing working. But there are mean obstacles that get in the way, when other processes such as plugins, or video processing also try to get hold of cpu cores. Priority raised.
