I am on Windos 10. Are you using Cubase? What version of VE PRO 7 are you using?
-
-
Cubase 10.0.20, VEP 7 build 834.
Just tries 7.0.834 and it is just as bad for me. Observing what connects/disconnects fast vs what doesn't might point to a particular plugin....but hard to tell. Looks especially slow on one of my 4 machines. This machine where it looks like the instance takes especially a long time has Halion 6, Halion SE. Omnisphere, UVI Falcon, Best Service Engine and few others.
Unfortunately in its current state VE PRO 7 is not useable for me because of the slow load/unload times. I hope they take this serious and dig in. A bit concerning how there is so little posts on this problem lately.
-
What's weird for me (W7) on master/Daw - W10 on one of three slaves -- is 'first project open of the day' (I leave my puters on) - the start up of a Cubase (10.x) project is VERY slow. BUT all subsequent project opens of THAT day are 'fast'.
come back the next morning and FIRST project start is VERY slow (faster for all starts - throughout the day). Not a deal breaker but a bit annoying.
Rob
-
What's weird for me (W7) on master/Daw - W10 on one of three slaves -- is 'first project open of the day' (I leave my puters on) - the start up of a Cubase (10.x) project is VERY slow. BUT all subsequent project opens of THAT day are 'fast'.
come back the next morning and FIRST project start is VERY slow (faster for all starts - throughout the day). Not a deal breaker but a bit annoying.
Rob
Yes Rob! That is the exact same behaviour I have even with VE PRO 6......however I can explain some of that behaviour because of a strange bug in the HALion platform (not sure if it is a Steinberg problem or Vienna issue).
I have a tremendous amount of HALion 6 and HALion SOnic SE instances in my template. I tracked down a problem where VE PRO connects extremely slow to an instance only the very first time if HALion (6 or SE) has a patch that utilizes a convultion effect. So if the patch has a Halion convolution effect or a Guita amp convolution effect than this causes the slow connect/disconnect for the just the first time. After that it is fast as normal in VE PRO 6.
Perhaps you have something going on similar in your template which might help determine if it is a VE PRO bug.
-
What's weird for me (W7) on master/Daw - W10 on one of three slaves -- is 'first project open of the day' (I leave my puters on) - the start up of a Cubase (10.x) project is VERY slow. BUT all subsequent project opens of THAT day are 'fast'.
come back the next morning and FIRST project start is VERY slow (faster for all starts - throughout the day). Not a deal breaker but a bit annoying.
Rob
Yea - good to know. I don't use Halion - but I bet this 'sort of thing' is happening -- somewheres 😞
Yes Rob! That is the exact same behaviour I have even with VE PRO 6......however I can explain some of that behaviour because of a strange bug in the HALion platform (not sure if it is a Steinberg problem or Vienna issue).
I have a tremendous amount of HALion 6 and HALion SOnic SE instances in my template. I tracked down a problem where VE PRO connects extremely slow to an instance only the very first time if HALion (6 or SE) has a patch that utilizes a convultion effect. So if the patch has a Halion convolution effect or a Guita amp convolution effect than this causes the slow connect/disconnect for the just the first time. After that it is fast as normal in VE PRO 6.
Perhaps you have something going on similar in your template which might help determine if it is a VE PRO bug.
-
Did you ever get this fixed? Was there some configuration that sorted it?
I currently have the same issue and more:
+ Long close time that appears like a hang (same as you) for many minutes and longer than load time;
+ A long wait after Cubase/Nuendo has connected to all the VEP instances. Watching the CPU monitor on the Windows VEP slave machine it goes up as each instance is connected and then once all are connected, and while in Cubase there is a progress spinner, the CPU on the slave goes down to 1 or 2% as if VEP has closed, stays there for 4 or 5 minutes then quickly goes up to about 30-40% and Cubase completes and I can start work. This is the same for coupled or decoupled - no difference.
+ And also a super slow gui in VEP when connected to DAW.
Thanks!
-
Nope never fixed. I am losing any faith they will ever fix it. I am also surprised there are not many more users complaining or experiencing these problems.
I suspected it might have to do with HALION....so I removed that plugin and made virtually no difference so I doubt it is related specifically to that one plugin in my case.
Incredibly frustrating as VE PRO 6 basically works fine so it 100% has to be on Vienna's side to fix this.
-
Thanks for the reply.
Hmm - I wonder if it's a Windows defender thing maybe scanning remote calls if that's even a thing. Or maybe a paging or caching thing - don't know. Strange to see the slave machine CPU drop to just OS level during that 'hang' period.
So frustrating. If I find a solution I'll post it.
-
I have experienced the same issue on Cubase 10/Mojave (Main DAW) and W10 (slave comps)
My template has my 6 slave VEPro instaces saved in a Freeze state (this is for various workflow reasons).
When I unfreeze an instance, VEP6 only takes a couple seconds to unfreeze and connect to the slave comp.
VEP7 takes over 5 mins!!! It is also much slower when refreezing that instance in a project.
I had to just revert to VEP6 on all my computers for now. Hoping this gets resolved.
-
I have experienced the same issue on Cubase 10/Mojave (Main DAW) and W10 (slave comps)
My template has my 6 slave VEPro instaces saved in a Freeze state (this is for various workflow reasons).
When I unfreeze an instance, VEP6 only takes a couple seconds to unfreeze and connect to the slave comp.
VEP7 takes over 5 mins!!! It is also much slower when refreezing that instance in a project.
I had to just revert to VEP6 on all my computers for now. Hoping this gets resolved.
Hi magnumpraw -
It's a drag huh. Did you have any issues moving back to VEP6 with projects saved in 7?
Thanks!
-
Hi magnumpraw -
It's a drag huh. Did you have any issues moving back to VEP6 with projects saved in 7?
Thanks!
No, anything saved with 7 would not open in 6. Luckily I discovered this in a week where I was strictly doing upgrades and testing. I had only made an hour's worth of changes to one of my templates when I found the issue. It was an invonvenience to revert and recreate what I had done, but not the end of the world. I am running 6 for now while in production deadline mode.
Will look at 7 again once this gets sorted.
***I should also mention that I found the load time was greater relative to the size of the VEP project.
-When unfreezing the VEP instance in Cubase and connecting to my Synth-5 computer that has only 25GB of RAM loaded, VEP7 connects in 30 secs or so (still longer than on VEP6 though).-However, when unfreezing the VEP instance in Cubase and connecting to my Synth-1 computer that has about a 100GB RAM footprint, it can take up to 7mins to unfreeze and connect.
Both of these processes only take seconds in VEP6
-
My Ensemble startup time is about 5 minutes, all of it because it is "scanning plugins". The bizarre thing? I have 5 plugins - Synchron Player, Synchron Pianos, Vienna Instruments Pro, Kontakt 6..1.1, and Omnisphere. Closing Ensemble is not as bad, but it does still take about 2 minutes.
I am running a core i7 8700k with 64 GB of ram, Kontakt runs on a 10 TB spinning drive, everything else is installed to an M2 SSD (the libraries are all stored on a spinning drive, but the actual software and plugins are on the SSD).
This has nothing to do with the number of plugins, since I only have two plugins that are not Vienna products, and omnisphere + Kontakt are not anything unstandard. I would be surprised if anyone writing music does not have these two products installed, Ensemble should not have any issues with these two plugins.
VEP 7 is also pretty unstable, frequently crashing whenever I have a MIDI track loaded in Cubase with an instrument already loaded in Ensemble and I delete the track from within Cubase 10.4. If it didnt take 5 minutes to re-open it and another 10 minutes to load my orchestral libraries in, it wouldnt be so bad, but it sure does put a damper on creativity to have it crash and know that its going to be 15 minutes before I can start working again.
VEP 6 had no such issues, and by the time I upgraded to VEP 7, VEP 6 was so wonderfully fast and stable. I expected issues initially, but not a year after its release.
-
Yes.....very depressing that these issues persist. I like you are forced to stay with VE PRO 6 and am doubtful I will ever be able to use VE PRO 7. Not that I don't have some severe iassues with VE PRO 6....I do and upgraded to VE PRO 7 as I assumed that would be the only way to get these problems resolved....... waiting like the rest of you.
The fact is that there does not seem like a huge amount of people complaining, so I am doubtful they will take this serious enough to solve the issues. I don't understand how this can be so hard to solve when these pfoblems were not an issun in VE PRO 6.
-
-
I'm having the same issue. Template with zero plugins loaded, cubase 10 closes and opens very slow. If I disable all the outputs of Vienna in vst instruments, it's a little bit better. Activated and disablilng those outputs takes FOREVER. I'm still using VE 5 because of the awful folder organization, which is by vendor and developer instead of the neat folders I created. I got tired of searching in a separate window for program files - vst plugins - Eqs, compressors, etc.
Maybe folder organization will come in version 10 lol.
BTW I loaded an orchestral template with over 200 vienna 7 outputs engaged in cubase, could not use it at all.
-
From another user:
"The issue is they added a ton of automation lanes to VE Pro that means cubase auto creates all these auto lanes per return lane from an instance. So say you have 130 return stereo lanes, each one in the Cubase mixer now creates 20 auto lanes too. So now you have the Cubase mixer trying to create 2,860 mixer lanes every time it tries to open a session instead of 130. And there's no way around this with the VST3 standard -- if the plugin presents auto lanes they will be created in the DAW mixer."
-
