Hi Tim,

To which build of VE Pro 6 have you downgraded?

Please also try VE Pro 6.0.17226 from https://www.vsl.co.at/en/MyVSL/downloads_archive, as this was probably the version you had installed before upgrading to VE Pro 7!

We are in fact unable to reproduce the issues you are experiencing in-house, but we´ll keep investigating!

Best, Marnix

Thank you. The version of VE Pro 6 above is working great

Now everything loads as it did before

@marnix said:

Hi Tim,

To which build of VE Pro 6 have you downgraded?

Please also try VE Pro 6.0.17226 from https://www.vsl.co.at/en/MyVSL/downloads_archive, as this was probably the version you had installed before upgrading to VE Pro 7!

We are in fact unable to reproduce the issues you are experiencing in-house, but we´ll keep investigating!

Best, Marnix

Maybe my tempate is too big for VE Pro 7... I have about 2000 midi instruments/articulations in one server slpit between 4 VE instances. VE Pro 6 is handling it well now though

Hi Tim,

I've sent you a private message.

Thanks :)

Has this problem been fixed? I am still on ve pro 6 hich works great. But would love to move to ve pro 7 at some point. Has anyone expreienced better results with hanging times with the new version?

Hi, 

We are aware and hope that we can fix these issues soon. 

Best, 
Paul

@Paul said:

Hi, 

We are aware and hope that we can fix these issues soon. 

Best, 
Paul

What is the status of these issues? No mention of any fixes regarding these issues in the 7.0.877.  Very frustrating to buy many licenses but not be able to use them as it does not work as well as version 6 does on my systems.

I have occasional hangs while rendering w. Cubase 10.0.30 and VEP 7 for the last 3 versions.
I do_not have slow loading or unloading. The initial build of VEP 7 did unload more slowly in general.

It looks like a big stuck note on the VEP side. I have to restart the computer to get a successful render.
It's not a gigantic project in the sense which was mentioned (this latest has 90 channels in the VEP mixer) but there is a lot of active automation with these projects.

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 had crashes in late VEP 6 which logs showed belonged to Synchron Player. Martin Saletag noticed those during our communications and appeared to have addressed them I think at build 834 of VEP 7. At least as to the crash component.

I work around this now, if I restart the computer before a render I don't get a hang. If it's been running for a bit I can pretty much count on it hanging. It must be at the same place in this project, it produces a 131kb file every time, hanging after a couple seconds, maybe. I am using 9 or 10 instances of Synchron Player in this. But it's only like 10GB RAM used by VEP and I have 32.

@marnix said:

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.

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

@civilization 3 said:

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.

Yeah, it's all 7 here. The initial build basically would only be force-quit (albeit I never hung around to see it quit much_later) but the first update addressed that for me.

So the problem would seem to have more than one parent.

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.

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.