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

Notification

Icon
Error

Forum Jump  
Cubase 10 Super Long Load and Close Times VE PRO 7
Last post Fri, Oct 18 2019 by casalena, 31 replies.
Options
Go to last post
2 Pages<12
Posted on Tue, Oct 08 2019 18:43
by magnumpraw
Joined on Tue, Oct 04 2005, Los Angeles, Posts 140

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.

Posted on Wed, Oct 09 2019 19:13
by santamorphic
Joined on Wed, Jun 04 2008, Posts 155

Originally Posted by: magnumpraw Go to Quoted Post

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!

DAW Client: Logic Pro X, Cubase 10, Nuendo 10, iMac Pro 10/20 Core, 64GB RAM
VEPro Server: Windows 10 Pro x64, 4/8 core, 256GB RAM, SSDs
Posted on Thu, Oct 10 2019 16:53
by magnumpraw
Joined on Tue, Oct 04 2005, Los Angeles, Posts 140

Originally Posted by: santamorphic Go to Quoted Post
 

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

Posted on Thu, Oct 10 2019 20:27
by littlewierdo
Joined on Sun, Apr 24 2016, Posts 214

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.

Posted on Sun, Oct 13 2019 18:06
by dlpmusic
Joined on Sun, Jan 19 2003, Posts 269

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.

Posted on Sun, Oct 13 2019 19:10
by santamorphic
Joined on Wed, Jun 04 2008, Posts 155

Out of interest, is anyone having these issues _not_ using Cubase/Nuendo?

DAW Client: Logic Pro X, Cubase 10, Nuendo 10, iMac Pro 10/20 Core, 64GB RAM
VEPro Server: Windows 10 Pro x64, 4/8 core, 256GB RAM, SSDs
Posted on Thu, Oct 17 2019 03:33
by casalena
Joined on Tue, Feb 15 2011, Posts 18

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.

Posted on Thu, Oct 17 2019 07:43
by santamorphic
Joined on Wed, Jun 04 2008, Posts 155

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."

DAW Client: Logic Pro X, Cubase 10, Nuendo 10, iMac Pro 10/20 Core, 64GB RAM
VEPro Server: Windows 10 Pro x64, 4/8 core, 256GB RAM, SSDs
Posted on Fri, Oct 18 2019 01:37
by casalena
Joined on Tue, Feb 15 2011, Posts 18

Just an update - I built the same exact template with VE 6 and it loads more than 70% faster.  Even in standlaone.  Loading plugins, even moving buses or channels around takes forever.  Engaging 32 outputs in cubase took over a minute, with VE6 took 10 seconds.  It's pretty bad.

Posted on Fri, Oct 18 2019 07:26
by santamorphic
Joined on Wed, Jun 04 2008, Posts 155

Originally Posted by: casalena Go to Quoted Post

Just an update - I built the same exact template with VE 6 and it loads more than 70% faster.  Even in standlaone.  Loading plugins, even moving buses or channels around takes forever.  Engaging 32 outputs in cubase took over a minute, with VE6 took 10 seconds.  It's pretty bad.

That would be in line with the earler automation lanes post. I will be going back to VEPro 6 for my next project.

DAW Client: Logic Pro X, Cubase 10, Nuendo 10, iMac Pro 10/20 Core, 64GB RAM
VEPro Server: Windows 10 Pro x64, 4/8 core, 256GB RAM, SSDs
Posted on Fri, Oct 18 2019 14:52
by casalena
Joined on Tue, Feb 15 2011, Posts 18

The only thing I miss is the manual color pallette for track colors :)

2 Pages<12
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.