More often than not, whenever I load a big project or a big template (multiple instances on a local server, not an external machine), VEPro would stop loading the template (or perhaps freeze) and then I need to force quit VEPro and try to load it again.

Usually, it gets it by the fourth or fifth time. Is anybody else experiencing this?

VEPro 7 latest version, on the new Mac Pro 28-core 192 RAM macOS Catalina.

Thanks!

Hi, 

Sounds to me like a loading process in one of your used plug-ins is hanging. 

You can send us a sample from the hang, to

=> Open Activity Monitor

=> Choose Vienna Ensemble PRO

=> Click the small "i" in the upper left corner

=> Click "Sample" in the lower left corner

=> Save the file and send it to us 

There's a good chance we can tell you what is causing the hang (but we cannot change the loading procedure of a plug-in, VE Pro is only the host) => so you can contact the producer of the plug-in and check what can be done. 

Best, 
Paul

Yeah, I'm seeing the same behavior here too...

This is really weird...

Hi,

If you can find a way to reproduce this scenario, we can at least point to the culprit... any step-by-step instructions / samples (as described above) and setup information will be helpful: !

Best, 
Paul

Hi toodamnhip, 

It is mostly the dynamic loading processes that get in the way of each other, and VE Pro cannot influence that, being "just" the host. 

The plug-in standards / names etc are VERY rarely changed... none of your sequencer projects would open those plug-ins, no matter where they are hosted. 

Best, 
Paul

As a long time user and Fan, For me, if VE Pro wants to be a truly DEPENDABLE hosting format, it needs to forget what is "possible", and instead, realize that users desperately need CERTAINTY that One stupid sub program cannot FREEZE an entire template. So, VE Pro needs to build into its capabilities a diagnostic tool of some sort.

There are many possible levels to this:

It can be a timed out based approach, where if VE Pro does not hear back from a program that's trying to load it will bypass and move on.

It can be a special opening mode where audio is shut off allowing a user to see which programs aren't loading and bypass them before turning on the audio aspect back on. And it can be many other approaches, all equating to isolating any hanging VI, bypassing it, and NOT HANGING!

I am not a programmer, I do not care one iota about programmers or their "needs" or "limitations" I care about what end users NEED.

As of this moment, VE Pro is an extremely vulnerable program to rely on for the sole source of one's orchestral or VI library. It is subject to the weakest link of any 3rd party VI that goes retarded. If you have 60 VIs, realize that any one of their "updates" can potentially sink Vienna and therefore one's whole template or song.  If Toontrack screws up its naming protocol like once happened to me, VE Pro is sunk. If ever problematic Mach 5, with its low IQ method of searching for its sounds can't find its brain when trying to load, 99 other working VIs can ALL be stopped dead in their tracks. Terrible terrible terrible! 

This is the REAL #1 issue users need addressed. I believe it can be done. It starts with a no excuses attitude and THREE- realizations:

1) that VE Pro is extremely vulnerable.

2) That it is completely unacceptable for any one malfunction of a VI to stop the entire template from loading. 

3) That something CAN be done about it.

January 2023, same problem, not addressed by VSL. Massive template, lovingly created, now tripping up over a Kontakt plugin. VSL DO something about this - it disqualifies you as a serious tool. I'm in the middle of a Netflix project and cannot load my orchestra - it's simply not good enough to say 'VEP is just a host so contact your third party plugin provider'. You need a timeout-and-move on from non-functioning plugins so that the template can be loaded! Why don't you have that???

I fully agree! Vienna is passing the buck and NOT being responsible for their customers who RELY on their product for their careers! Fail VSL, FAIL FAIL FAIL! No more "features", no more "updates". Please focus on RE-designing your product to allow users to BYPASS any stuck loads. ASAP please!

How can one KNOW what plug-in is hanging the load? Every time I've had VE Pro get stuck, I haven't had as clue WHICH plug in failed. When one has hundreds, the "trial and error" to determine the "culprit" could be a disaster, resulting in days of lost work. In a "lucky" scenario, maybe a user might have just updated "one" plug-in so as to make it obvious. But in reality, its not that simple. Unless I'm missing something?