Why is VEP better performing than Cubase ? When I connect to VEP inside Cubase the same plugins ( Halion 7 ,Kontakt and U-he Diva ) works whitout performance peaks and MUCH lower CPU load . Plugins that I cant use in cubase because they make the CPU going crazy ( Cubase 11 , 12 and 13 ) like Pharlight in Kontakt 7 works absolute fine when contained in VEP via cubase in the same computer. Thats very weird ! And it is not a new problem since it is the problem is in C11, C12 and 13 . There must be fundamental problem in the Cubase engine ! I have tried different ASIO guards setting for VEP and so on , but no difference .
Hi and welcome to the forum,
I’m not an expert in this area, but my expectation is, that you are not comparing the plug-ins, but the whole system. So you are comparing Cubase (with tones of features and functions) against VE Pro. The plug-in itself is not the only part of the system, which is using the CPU as the host.
Btw, are you on Windows or Mac?
Thank you for the answer !
My point is that Cubase is networking with VEP in the same computer and using the the plugins ( kontakt , diva Halion ) hosted in VEP but played from Cubase . VEP is in other words a VST instance in Cubase . And when I play my plugins in from VEP there is a huge difference in CPU load compered to play the same plugin directtly in Cubase. So when I change a track in Cubase connected to VEP ( normal CPU load ) to a track connected to exactly the plugin hosted in Cubase the CPU load goes bananas .
And i dont have anything else in Cubase active . Just 2 tracks . One connected to VEP and one track to Cubase .
So having 2 programs ( Cubase + VEP ) running at the same time works better then only have Cubase running …
I have a Win 10 computer
Hi,
Not really. Just the VE Pro “receiver” plug-in is an instance of Cubase. The VE Pro Server is running totally out of Cubase (which is its beauty), even on totally own thread. Thanks to this, you can run the VE Pro server independently on Cubase. So you can keep your instrument template loaded in the VE Pro and open (plus activate) multiple projects in Cubase. Thanks to the fact the VE Pro Server remains open with the very same template, the computer doesn’t load all the sample libraries again and again. So you can load multiple projects very fast.
I totally agree. And this is also the big benefit of using VE Pro as an externl VST instruments host.
Hello everyone,
I’m Michael, new here in the forum. The post is quite old, but still interesting. I’m not a Cubase user, I just use various plugins from Cubase and MAGIX Samplitude Pro X8 as my DAW. As a producer of electronic music, I work a lot with plugins from Roland Cloud, and they eat up CPU power like crazy, so I was constantly forced to use the track freeze function. A few days ago, I heard about VEP and the wonders it can do for CPU usage, so I decided to buy it on the spot. And yes, it’s true. It brings incredible improvements. According to my research, this is probably because VEP is a standalone program (the VST plugin only handles MIDI and audio communication with this program) and because this program has been optimized for multi-core support in a highly efficient way, better than any DAW has been able to do so far.
I use VEP on the same computer that runs the DAW. This purchase was definitely worth it for me.
But I don’t think it’s because of Cubase. Samplitude has the same problem, Digital Performer has the problem, I think it has to do with the versatility that a modern DAW brings. VEP only has to do one thing: generate sounds.
VEP has some other functionality you may find useful, but if cpu performance improvement by better core loading (which is basically what this is) is all you need Audiogridder does the same and is free.
1 Like
Thanks for the recommendation. I bought VEP yesterday. 
Anyway, Audiogridder sounds interesting too. I’ll give it a try.
Audio gridder works better for loading individual plugins. You get the same performance benefit you see with VSTI’s but it’s easier to use for plugins. AG can load VSTI’s as well and it has the same advantage as VE pro. I find AG quicker and easier to use generally . VE pro works best for composers who have a large template that can stay loaded between projects.
M