I thought I would possibly save some others from the frustartion I have been having.  I believe I have traced the problem to corrupt preference files that unfortunately have corrupted my huge template.....and now I probably have to rebuild unless Vienna is able to help.  Here is some of what I wrote to them just as an FYI....

I am baffled to what is going on here with the latest version of VE PRO 7.  I have many machines with a lot of experience.  The ne machines can run Cubase as expected....but running VE PRO yields terrible results.  The text below is what I sent support.  If anyone has any thoughts please share.....

Thanks

Super frustrated.....I upgraded am Intel 5960x (8 core)  with a very large orchestral template that ran at 50% CPU.  I upgraded to a machine (9900k) I was using for about a year running Cubase.  Now that machine should be at least 30% faster...but it is not it is running terrible with a idle load of 82%.  I thought maybe there was some component causing an issue....so I built a whole new machine based on the 8 core RYZEN 3700x which is similar in benchmarks as the 9900k processer.  It is running it just as bad with 82% load.  Please advise.  I have a 14 core Intel that also works beautifully.  I can not figure after wasting 3 full days now why a 5960x machine works so much better.  I have a very large template and I tested much smaller 16 instances of each plugin, i.e., Kontakt, Omnisphere, etc...  With a small setup/template the new machines perform as expected and better than the older 5950x.  It is only when he template gets large that the effect of poor performance becomes more exaggerated.  I hope you can help solve this.

Hi Paul,

Any chance the developers can comment on this issue?

Probably not going to get much response as most of us turn ASIO GUARD off for VE PRO.  Every once in a while I turn it on to see how much better the slave machines perform under CPU loads.  The problem besides the changing track 2-4 second pause is that my exports take like 2-5 minutes to begin the process and 2-5 minutes to end the process.  I would love to have the option to use ASIO GUARD with Cubase but this will have to be fixed on Vienna's side to get this working better.  Steinberg has already looked into this multiple times for me.

Any chance the developers can look into this issue?

I too see this on many instances of Kontakt but not 100% of the time.  I usually keep my disk stream buffer as low as it can go....but turning it up form 6k to 18k seems to mostly fix the problem....takes a little more RAM but nothing else seems to fix it.

Ah...ok that explains it.  It obviously loads the VST3 version inside Cubase.

Is there any plans for future support of hosting VST3 instruments?

I use a ton of instances of Halion 6, ans SE.  It works just fine.......but you will not be able to use it as a VST3 instance nor does VE PRO allow any plugin to communicate back to Cubase the way it can when you load an instrument inside Cubase.

Best way to think of it in real world use is that you can off load that CPU/RAM usage from Cubase to VE PRO which is great....but you lose all the communicartion back to Cubase without jumping through cumbersome automation manual assigning which I never bother with.

A reply from Paul would be appreciated....I asked almost 2 months ago....

I see this all the time on one of my machines.  Never does it after a fresh computer restart....but loading a file a second time is 50/50 if it will freeze or not.  Then I have to force quit in task manager and try again.  Sometimes it can take 4 or 5 tries before it finally fully loads.  It does always get stuck in the same spot so I suspect it is aparticular plugin.

Hi Paul...

Do you have any info regarding this issue?

BUmp....hopefully Paul can reply to this....

Hi Paul...

Can you comment on this issue?  Would be great to be able to resize the main plugin interface.

If I load HALION 6 in Cubase I am free to resize the main interface all I want.  I can not resize Halion 6 in VE PRO 7 at all.  If I float some of the individual elements like the browser of Halion 6 I can resize that but not the whole main interface.

Is this something that the VE PRO team could fix?  It is quite a pain to not be able to do this.

Originally Posted by: casalena

Fixed in latest update for me, runs just like V6 now.

Yes!  I can use VE PRO 7 now! I still have some long standing open issues with Cubase/VE PRO....but Steinberg is aware and said they are currently working with Vienna to solve hopefully soon.

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.

Done quite a bit of testing....definitely not Windows Defender....again....same machines and VE PRO 6 works well.

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.

Check Windows Defender settings and exclude your sample drives.

Originally Posted by: Paul

Hi, 

These problems definitely are connected with the sheer size of the projects, and we have not found a way to reproduce this on our 32 /64 GB machines. 

It could be a mix of different plug-ins, the way Cubase handles, e.g., automation (creating a myriad of possible auitomation lanes for each track) and probably also how Audio Inputs are handled. 

This is a tough nut to crack, but I hope we can crack it. 

My apologies that we couldn't solve it until now. 

Best,
Paul

Thanks for the reply.  All I can say is that it works fine in VE PRO 6.  I believe I sent you a long time ago my VE PRO session files.  Maybe if I remove all plugins from the VST folder and have VE PRO load with all plugins missing that and compare that withe VE PRO 6 and 7 that could rule out any plugins if the descrepancies still happen?  Any thoughts on that test?

Originally Posted by: TimBlast

So I had a couple days with no projects to work on so I decided to try VE PRO 7 again......

 

and its the same issue...... VE PRO 6 server would load up in 20 minutes and then Cubase project will open in 4-5 minutes.... close in 1 minute

now the Ve Pro 7 is loading my server in 35 minutes and took 1 hour to open in Cubase ....... Tried exporting a mixdown and it took 26 minutes (for a 40 second track) I had to force close both cubase and ve pro 7 to get out of a project... how is it getting worse??? why is there no patch for this problem?? 

Rolling back to Ve Pro 6 again.... I don't know what did I spend the $99 for.... 

I wish Vienna would look into this more seriously.  We clearly are having similar issues and we both use Cubase.  I had some time to test a couple of days ago and can't pin point it.  Huge problems in my giant templates but when I test a particular instrument with say 32 instances and nothing else VE PRO 6 and 7 behave in a similar manner so I am not sure if doing small tests will reveal any problems.  In my huge template it as as bad as what you are seeing and much too difficult to slowly eliminate instruments, etc....  Frustrating for sure.

I did some more testing today.  I removed all the Halion 6 and Halion Sonic SE plugins from the VST folder so that the projects would load with "missing" plugin instances to see if these plugins were causing all of the problems of slower loading and closing compared to VE PRO 6.  

The load tmes definitely improved a bit but still overall the load times were much longer than VE PRO 6 ewith those plugins.  Although Steinberg may have a bit of work on their end I am definitely seeing VE PRO 7  with load.close and export times that are vastly longer than VE PRO 7 and am surprised that all Cubase 10 users are not seeing what I am seeing.

To me VE PRO 7 is not useable....extremely disappointed that no one else is chiming in if they are having issues.  I wish Vienna would engage in this conversation as I am spending a lot of time testing their product and am getting no where.

This may not be related to your problem.....but I had issues where I had a machine running just PLAY but a huge amount of instances for SD2 an SD3.  All ran fine for years until a particular Windows update.  I had not updated the PLAY version in a long time but updating the latest version of PLAY to my surprise solved my issues with the projects not being able to load everything.

I installed the latest version of VE PRO 7 yesterday to test....again the load/close times are much worse than VE PRO 6.  

VE PRO 7 - Open 5:52  (VE PRO 6 Open 3:20)

VE PRO 7 Close about 7 minutes.

The seond tme I open it took VE PRO 7 4:05 vs VE PRO 6 does it in 1:55.  Close time was the same 7 minutes.

The reason for the shorter second open is due to a strange Halion bug utilizing patches that have a convolution reverb or amp effect in them....I have about 100 of these so the problem is extreme.  Steinberg knows about it and hopefully will fix it at somepoint soon.  None the less..... clearly there is a VE PRO 7 issue that is making the problem MUCH worse than in VE PRO 6.  I wish Vienna would take this serious....I know it does not affect many of us but I paid for a lot of licenses and my confidence that they will solve this or that they are even concerned is what worries me.

Originally Posted by: civilization 3

I want to be clear, my hangs on render can't be related to loading or quitting issues, which both are very responsive here.

My issues may be slightly different as I never got around to try and render any projects as my load/quit times were so long that I had to go back to VE PRO 6 to work.

Originally Posted by: marnix

Hi all,

We still cannot reproduce the problems with exporting mixdowns in Cubase here, but our developers are currently investigating what could possibly cause projects, which have been created in some VE Pro 6 builds, to take so much longer to load in VE Pro 7.

Thank you all for your patience!

Best, Marnix

I assume no progress has been made?  It has been months now and I purchased many licenses that are useless to me compared to VE PRO 6 which works well.  Not sure why this is so troublesome to pin point.