Btw, this might be the best demonstration of the whole VST Real-time CPU Meter spiking issue, without ASIO Guard, I’ve seen:
It’s a long 14 minute video, much of which is spent watching repetitive cut-copy-paste operations.
But if you follow it closely and watch (and understand) what’s going on, you’ll see the following…
Cubase 7.x (with ASIO Guard OFF) with Vienna Ensemble Pro 5 running on the same PC, at the same time.
Cubase struggles to run even a few instances of Aether reverb.
The user then moves the reverbs to VEP 5 where it’s able to run tons of them using much more of the available CPU.
Cubase is also set to have multi-core turned off so that it can hog one, unfettered core.
Everything plays very well at this point.
As soon as the user turns on multi-core in Cubase, that’s being used up by VEP 5, you can see Cubase immediately spike. This is similar to a hyper-threading situation.
Unfortunately, the user never demonstrates how this configuration would have worked with ASIO Guard turned on, but my guess is that it would not have helped in this situation, as VEP probably appears to Cubase as a “live input monitoring” use-case (not sure, and would love confirmation on this). But for “normal” plugins, it would have helped. Would it have helped as much as running VEP on all but one of the cores and letting its engine do its thing? Ahhh, my guess is probably not. I don’t think ASIO Guard is that good yet. But again, it’s version 1.0, surely it will get better.
In the meantime, if you really want to use Cubase and really want to squeeze every last bit out of your computer (or multiple computers) VEP 5 may be a viable option.
In the video, Cubase is restricted to only one core which may not be practical depending on what you’re doing. You’d have to use VEP for just about everything.
But, you could get around this by using Windows “Affinity” to limit Cubase in multi-core mode to say, 2 cores and then let VEP have the rest.