182,279 users have contributed to 42,216 threads and 254,747 posts.
In the past 24 hours, we have 2 new thread(s), 23 new post(s) and 36 new user(s).
I am running a single Mac Pro 12 core with 64 GB of RAM. I currently use VE Pro 7 with Cubase, but I am wondering if I really need to be doing this? I really only work on one project at a time, so being able to preserve my intruments isn't that important. Are there additonal benefits to hosting my sounds in VE Pro over Cubase? Or would I do better to put VE Pro on my iMac and use it as a slave for an additional 32 GB of RAM?
Thanks,
Using it decoupled from (& preserved) Cubase is a massive advantage time-wise and in terms of stability, The save time alone is enormous. It's also significantly more efficient in terms of resources vs loading it all in Cubase. This is literally why it exists.
Hi,
Some DAWs have problems with repeated crashes. With VEP you don't have to reload all instruments.
Also if you are working with a master template you can share it with different DAW-projects. This makes switching between projects less painful. And it helps to get a consistent in a projects with a lot of DAW-project files, if you do the stem mixing inside VEP.
Best, Ben
Also, VE Pro dows a better job spreading the load throughout the cores than any DAW.
Thank you all very much! You have confirmed what I had originally thought and the initial reason that I started using VE Pro. I was recently advised that I was just wasting my CPU by using it on a single machine, and I wondered if something had changed since I started using VE Pro six years ago.
In tests I did, some DAW's use about 1-2% more CPU alone then when combined with VEP. Some DAW's were more efficient without it, but again, not by a signifcant amount. Cubase 10.0.20 was almost unusable without VEP, but they fixed that in 10.0.30, so the difference is less significant now.
This is not a huge difference and I don't think its a justification on its own for using VEP.
The bottom line is that sometimes DAW's are very efficient and sometimes they aren't. VEP happens to be very efficient IMHO, but of course you're adding another program and there will always be some overhead with that. So if the DAW happens to be inefficient, then you may gain a few CPU percentage points by using VEP to handle plugin rendering instead of your DAW. Not by a lot. But a little yes. But some other DAW's are actually more efficient on their own without it. But again, not by a lot.
In my view this should not be a determining factor for whether or not to use VEP, its not a significant enough difference.
HOWEVER...
VEP provides workflow advantages, that is the real point of using it, and the good news is that VEP is very efficient with and without a few CPU percentage points one way or the other, your computer should not really be bogged down more or less with or without it.
Unless you put VEP onto a slave computer, then obviously you just free'd up your DAW machine cpu massively.
With VEP slaves you can have instruments loaded into lots of ram. I have 128gb of ram on my 5,1 and have not been able to max it out yet, so for me that's not a factor, but if I were working professionally I would love to have a VEP slave that is just loaded 24/7 with samples and that other then crashes, never has to reload, while my DAW machine can be up and down and rebooted and run in different modes or whatever I want, work on my taxes, etc...without touching the VEP template over on the slave machine. You can do that on your DAW machine too if you ahve lots of ram, but ultimately I feel I end up taking my DAW machine up and down a lot, etc..whereas a simple VEP slave can just sit there and BE that.
what I like about using VEP on the same machine...
Decoupled and preserved... its great. Easily setup orchestra channel setups and even mixes...and then easily reuse across projects. For me that's probably the biggest thing.
VEP also has workflow enhancements for when working with VSL instruments and MirPro.
VEP is also quite good at enabling and disabling channels, and actually freeing up RAM. Cubase is pretty good at that too, but Logic sucks at it, though the latest version is getting better, but Logic is famous for not freeing up ram even when plugins are disabled entirely. if you're working with limited ram and need to have a large template that you enable or disable certain channesl in order to choose what to be in your ram at a moment...VEP has a lot of nice features for that and actually DOES free up the ram.
If you switch around between DAW's, then its REALLY a no brainer to use VEP for handling your instruments so that you can easily transfer a project from one DAW to another.
The other thing for me is the automation mapping, all of an instance's automation - all of its plugins - in one place in Cubase. It would be beyond unwieldy the old way. Particularly now as most names of parameters are what appears, vs. Parameter x before VEP 7.
I am running a single Mac Pro 12 core with 64 GB of RAM. I currently use VE Pro 7 with Cubase, but I am wondering if I really need to be doing this? I really only work on one project at a time, so being able to preserve my intruments isn't that important. Are there additonal benefits to hosting my sounds in VE Pro over Cubase? Or would I do better to put VE Pro on my iMac and use it as a slave for an additional 32 GB of RAM?
Thanks,
I asked the same question, too, and came to the answer that I don't neet another level of complexity between my Sequencer (Cubase) and the VSTi.
My Computer is powerful enough for the things I do. Loading times are pretty fast. Crashes happen not very often. I don't want another mixer in a mixer...
I use instrument tracks. One for each Instrument, using custom presets and expression maps.
But: to each their own.
