Hey all,
I've had this same problem with Cubase 8.5 and VEP 4 and am at my wits end. I'm running Cubase 8.5.2 with Vienna 6.0.15563 on a Windows 10 Machine with 64gigs of ram. I'm using about 14gigs of Ram in Vienna and about 3 or 4 in Cubase. My processor is and Intel i7-5960X and I haven't overclocked.
I use Vienna Ensemble 6 (used to be 4) with cubase 8.5. I have one internal metaframe on my Cubase machine with 5 projects instantiated in it and also have two remote VEP that I use.
Everything seems to work fine, but then, after what seem like random periods of time Cubase crashes and becomes unresponsive. I can't even close out of it without using the task manager. Once I close out, however I find that the vienna ensemble projects are mostly disconnected, except for one or two usually, in my most recent setup its always the same one that stays connected. Even with Cubase closed, I can't "decouple" that instance. I can't even exit out of Vienna Ensemble Pro, because VEP hangs while trying to close as it tries to decouple the instances of itself (from a sequencer that is no longer open).
If I try to load Cubase after such a crash, without force closing Vienna Ensemble on the host machine it is completely unresponsive and the time between clicks and actions is very long.
The only solution is to exit out of cubase and then force quit the Vienna Ensemble server. Once I reload the VEP metaframe and reload cubase, all functions normally, until, that is, the next crash which is usually a few hours into working. This, of course, is very time consuming and destroys and real functionality the 'preserve instance' brings.
The reason I don't think its Cubase by itself is that once I reload the metaframe all works ok...but as long as the previous metaframe is loaded cubase is very very laggy.
Any help would be greatly appreciated.
F
PS - I've attached a picture of the vienna metaframe with the percussion project still coupled. This is after attempting to close out of cubase and, I think, part of the problem.
