Welcome Guest! To enable all features please Login or Register.



Forum Jump  
Multiple smaller Instances or one large instance ?
Last post Fri, Jan 20 2023 by Paul, 8 replies.
Go to last post
Posted on Thu, Sep 01 2022 16:05
by michael-stram
Joined on Fri, Nov 01 2019, Chicago, Posts 15

Completely redoing my VEP servers and was wondering this for a while.

What's the most effective way? Per server, multiple instances ( brass instance, Winds Instance, etc ), or one large instance?

On the daw side what's the performance hit if one server has multiple instances? Does initiating the outputs hit the performance harder than one large instance?

I don't mind having 10 instances of VEP running if the hit is minimal. I feel like I can organize smaller chunks better.

Posted on Tue, Dec 13 2022 09:37
by Crabman74
Joined on Sat, Jul 18 2020, Earth, Posts 4

I have the exact same question! Mihkel Zilmer said, that from VePro7 onward it would be more effecient to have multiple smaller instances instead of one large one (https://youtu.be/rxFg2atVvho).

I'm not really sure I can confirm this. I worked with an orchestral template consisting of four instances (strings, winds, brass, perc). Performance got worse, the more instruments I added into each instance (damn black friday...)

I now split everything into smaller chunked instances with way less audio outputs each: flutes, oboes, violins, horns, etc. The result is actually even worse, but I'm not done tweaking.

Perhaps a VePro developer can enlighten us, what would be the most performance-friendly approach. Or at least something like a matrix, under which circumstances/scenarios what approach is the better choice...

Would be awesome to have someone could give information on this, depending on the usecases and hardware circumstances to help us determine the most performant approach for our scenarios...

Thanx someone in advance!

Posted on Tue, Dec 13 2022 18:04
by Paul
Joined on Sat, Aug 03 2002, Vienna, Posts 13625


The difference between the 2 approaches is small, but you will stay more flexible with smaller instances. 

Don't forget that you can activate/deactivate channels and even whole instances and even automate that process, which will help you get the best performance out of your system!


Paul Kopf
Product Manager - Vienna Symphonic Library
Posted on Wed, Dec 14 2022 01:04
by evang42
Joined on Fri, Apr 08 2011, Posts 32

I really wish it was possible to say "INSTANCE A should only have X audio outputs and use Y cores" while "INSTANCE B should only have z audio outputs and use B cores" and so on.  One can only dream (along with FINALLY NATIVE Apple Silicon support) for VEP 8....

Posted on Wed, Dec 14 2022 16:02
by Andreas8420
Joined on Mon, Dec 02 2019, Vienna, Posts 191

Hi evang42,

It has always been possible to assign individual thread counts for each instance (or have them use the global settings). Does your percussion instance only use a fraction of the given computing power? Reduce its thread count! :-)

The option to use this feature is a significant advantage of the "multiple instances" approach with VE Pro.


File Attachment(s):
vep7_individual_threads.png (403kb) downloaded 24 time(s).

You cannot view/download attachments. Try to login or register.
Technical Support - Vienna Symphonic Library
Posted on Fri, Jan 13 2023 12:52
by dts_marin02
Joined on Sat, May 31 2014, Posts 3

I hope an upcoming version/update will make the multiple small instances workflow easier.

I hate working with big instances with fixed ports and outputs and want to have a more modular template that I can quickly drag and drop things as I need them.

Currently navigation is awful when you have a lot of instances.

My wishlist for improvements:


 • add preference to move connected/disabled instances at the bottom of the list and make their text a darker grey color. Currently there's no visual distinction.

 • add toggle to hide connected or disabled instances entirely

 • add a small rectangle before the instance name to show the color of each instance. 

• add search functionality


 • collapsable instance groups (instance folders). 

Posted on Fri, Jan 20 2023 16:59
by tonaldonal
Joined on Fri, Sep 06 2019, California, USA, Posts 3

@Paul (or anyone) - could you kindly point me to the documentation that explains how to "automate" the activation/deactivation of VEPro Server Instances please? 

I'm on latest VEPro 7.1.1406 on MacOS 12.6.2, using Logic 10.7.6.

Ideally I'd love if VEPro Server Instances would automatically deactivate (and release samples and memory) if they had not had an active connection from the VEPro plugin in my DAW after a certain amount of time.  And then become active again (load samples into memory) again once there was an active plugin connection from Logic.

Right now, I'm clicking the Enable/Disable (power icon) in each Instance in VE Pro Server when I don't think need an Instance for a particular Logic project, but it's very manual... and I have 30+ Instances.  And I don't want to disable ALL instances every time I switch project since that defeats the main advantage of having VEPro in the first place; samples are loaded and ready to go!

Posted on Fri, Jan 20 2023 19:42
by Paul
Joined on Sat, Aug 03 2002, Vienna, Posts 13625


Check out paramater automation in Logic, it works like this

Automatic timers would be too dangerous, this needs to be done "on purpose". 


Paul Kopf
Product Manager - Vienna Symphonic Library
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.