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

Notification

Icon
Error

Forum Jump  
Options
Go to last post
Posted on Wed, Aug 22 2012 01:43
by JohannesR
Joined on Fri, Jan 28 2011, Posts 3
The topic says it all. Strange thing is that if I open a VST2 Host server, it opens instantly.

Is there a way to solve this? It actually mean that when running a large template, even when using the DECOUPLE method - changing between two projects may take 10 minutes.

EDIT: Just thought I would add that I am on Snow leopard. My slaves are Win7.
Posted on Wed, Aug 22 2012 02:17
by Karel
Joined on Mon, Jan 19 2009, Belgium, Posts 2173

This has to do with the amount of MIDI input ports you have set in the VE Pro preferences (in the plugin). Lower them to the amount you actually use and you'll see the VE Pro VST3 initialization time go down significantly.

Karel Bassez
Software Engineer
Vienna Symphonic Library
Posted on Wed, Aug 22 2012 08:26
by JohannesR
Joined on Fri, Jan 28 2011, Posts 3
Thanks!

Did some rearranging, and lowered the number of MIDI input ports to 20 (from 32). I experienced significant improved loading times (close to 60% of what it used to be). Don´t think I can go any lower than that without compromising my template radically.

Is this going to be sorted out in the future, or is it a limitation that one has to live with? Is there a sweet spot number of midi ports where the VST3 version opens instantly? I mean, like if I lower my MIDI input ports to 8 - the problem disappears?

I am thinking maybe I should rearrange my template using VST2 instances, are there any pitfalls besides a little more cluttered setup due to the 1 MIDI input port limitation?
Posted on Wed, Aug 22 2012 09:19
by JohannesR
Joined on Fri, Jan 28 2011, Posts 3
I did some testing. I opened up a VST3 instance of VE Pro server with different MIDI input ports in preferences. Here are my findings:

Ports - Loading time in seconds - Seconds pr. MIDI input port
8 - 1,3 seconds - 0,16 seconds
12 - 2,4 seconds - 0,2 seconds
16 - 5,6 seconds - 0,35 seconds
20 - 15 seconds - 0,75 seconds
24 - 30 seconds - 1,25 seconds
32 - 74 seconds - 2,31 seconds


In my case, that means if I go from 1 VE Pro server VSTi with 32 MIDI inputs to 2 VE Pro server VSTis with 12 inputs, I reduce my loading time with three and a half minutes (three slaves)!!!! That´s crazy ;)



EDIT: And just for fun. 48 MIDI input ports takes 200 seconds to initialize, resulting in a initialization time of 4,2 seconds pr. MIDI input port. At least this implies that the initialization time in increasing almost logaritmic with the number of input ports.
Posted on Wed, Aug 22 2012 12:51
by Karel
Joined on Mon, Jan 19 2009, Belgium, Posts 2173

This is something that will never be solved (has to do with limitations of the VST3 standard). However it's quite rare that people need so many MIDI input ports in practice, seeing as the default of 8 MIDI input ports already means there are 128 MIDI channels available for use.

Karel Bassez
Software Engineer
Vienna Symphonic Library
Posted on Wed, Sep 05 2012 19:11
by flashman
Joined on Sun, Mar 20 2005, Posts 140

Welll.....my template uses over 500 midi tracks, and a lot of my colleagues have much bigger rigs still  - 750+. Mostly games and trailer people but it's not unusual at all to use huge numbers of midi tracks and therefore ports. The VSL way of using a lot of keyswtiches helps a lot but most of the Kontakt and Play instruments still come on individual tracks which really boost the numbers. It would be nice to think one day soon the midi device limit in Macs and the VST limit discussed above will be sorted.   

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.