Following this post, some answers have been given and it may be interesting to know which plugins are greedy in cpu cycles and if this is the case for all users.
IK B3 → LINK
Arturia Augmented Strings → LINK
Sampletank VST3 → LINK
Arturia Stage-73 → LINK
DX7 from Arturia V8 is higher than all the others I use from the V8 collection, although it is only noticed on my old Mac Pro
Have you tested Dexed?
It is so close to the original DX7 that I can hardly tell the difference with my 1985 recordings.
2 advantages: it’s free and in GP the cpu indicates between 0 and 1 %.
And there are some 16,000 sound banks available (with many duplicates).
I will give it a go thanks.
I found Noire in Kontakt to be high on my old PC setup, but don’t notice any issues now.
Korg Triton extreme uses a lot of CPU
The Morgan Amp Suite from Neural uses a lot of CPU, especially in stereo mode. The AC20 model in there is manageable (barely), but the PR12 and SW50 models use quite a bit more horsepower for some reason, and when combined with other plugins can easily push my 2017 i7 laptop past 60% and into dropout territory.
Yamaha Montage M ESP is pretty CPU intensive.
It seems to be worse than Diva (which isnt that bad these days).
I hope the next update gets it an efficiency boost. Even fairly “simple” AWM only presets are pretty intense.
One thing I have found that can vary WIDELY with VSTs is how they handle graphics in their window display. Some developers are very careful about this, especially if their products have visualizations that update at a significant frame rate. Some like MeldaProduction, Mario Neito’s Harmony Bloom, will actually go the extra mile and offload the graphics computation to a GPU if available. But the law of the VST land is YMMV.
In my experience one thing you should always try out IMHO with any VST is the effect of just closing each VST window once you have it dialled in. If performance is the goal, just closing all the VST windows may help a lot, depending on the VSTs. If you need to see values ongoing, it may be advantageous to just map that VST control to a GP widget—easy peasy.
I say closing VST windows “may” help because there’s no possible guarantee, but this simple measure is absolutely worth a try.