Hello Paul.

Thank you so much for the prompt reply. There is no way for me to accurately measure the load time as I never had a reason to take such a measurement while on the USB dongle.

All I can tell you is that in the past the exact same project would (most notably the instance tabs that run along the top) whiz right by. Albeit a very small template it's load speed was very impressive.

Please keep in mind that I am referring to the load time of the small project only. No streaming at all. I normally launch VEP / open my saved template / launch my DAW (CB 11 Pro) / open very small CB template.

FWIW: My Cubase and VEP projects reside on my second SSD drive (D:)

So, what I did was to use a stopwatch. I launched VEP / File / Open Recent Server Project / Clicked on my template. It took 14 seconds before the 5 instance tabs were fully loaded. I am by no means complaining. I simply am saying that I do see a noticeable difference in load time now.

Thank you again for your time and assistance. Peter

My Small Orchestral Template

Good morning @santamorphic My apologies for not getting back to you sooner. A few days ago I launched Vienna Assist and noticed that updates were available for my products which included VEP 7.x. Ever since applying said updates, my very small template loads incredibly quick. In fact, I think that it would be safe to say that it loads even faster than it did before.

For what it's worth I am running Windows 10 Pro (up to date) and Cubase 11 Pro. My PC and OS have been optimized for audio.

Thank you for your input and the link. Have a wonderful day!

Peter

Hello Paul,

I have same proble. After migrating to iLOK version a times of LOADING/SAVING has extremly increased.

For example:

My instance of Woodwinds (13 instruments) orginaly on eLICENCER version was loaded in 5s.

Now it is 38s.

It is 44011samples/2750MB.

When I have 6 instances. It takes 2,5minutes save whole project.

Also is not possible CONNECT button in VEP plug in  DAW to connect to instance  only when you click directly on the name of the instance.

@tonelabaudio said:

Hello all.

I have a very small lightweight template that I use. The only instrument being used is the Synchron player with a minimal amount of channels. All channels disabled at startup.

I moved over to iLok yesterday and find that this small template takes longer to load than it did prior to the switchover.

Thank you in advance. Peter

Yes, I am noticing the same behavior.  I was running VE Pro 6 pre-iLok and it loaded very fast, even a relatively large template with 40 channels.  The same template running under VE Pro 7 post-iLok definitely takes longer to load.  After the 40 channels load there is about a 25-27 second delay before the little icon stops spinning to show that the file is fully loaded and ready to play.

I also double-checked my pre-load times and I have them set for an SSD drive, which is what I am using.

Jerry

Thank you for chiming in Jerry. What I have noticed is that load times seem to be vary from one day to the next. My workflow / app launch sequence is unchanged.

Hello, everyone.

I confirm also that loading and saving times are longer since upgrading to iLok.

I'm running a main pc / slave pc system, with Cubase 11 Pro.

Everytime Cubase goes into autosave procedure, takes a lot of time for it to react again. That didn't happen using the eLicenser.

Hope you can sort this out.

Hi Guin - 

Yes - the problem is particularly bad when working with Cubase and the latest VEPro. 

If you're not already... to get faster saves maybe check out "decoupled" mode of VEPro. If you use that, a project save in Cubase or any DAW will be much quicker. You just have to remember to save the VEPro server project separately and load that up before opening your Cubase project.

But even the connection to these decoupled instances is many, many times slower than it was with the eLicenser version. 

Personally I've rolled back to the eLicenser version as the iLok version is currently unusable for me.

The performance issues when working with VEPro iLok and Cubase/Nuendo:

Extremely slow connection to VEPro instances (I tested with pared-down project of 128 instances decoupled with a Kontakt instrument inside each instance. VEPro 7.0.1113 connects to all instances in approx 12 seconds and VEPro 7.1.x takes 5 minutes 23 seconds.)

Extremely slow switchover to MIXDOWN mode to do an offline bounce (With the same pared-down test project VEPro 7.0.1113 takes <10 seconds to switchover and begin the bounce. VEPro 7.1.x takes 2 minutes 14 seconds to begin the bounce and another 2 minutes 14 seconds at the end of the bounce to come out of MIXDOWN mode.)

With this second problem, batch offline bounce and batch export events is basically unusable as the switchover to MIXDOWN mode and back happens with every event that’s rendered.

The above are pared-down test projects. With a real-world project I'm working on, the problems are worse as there are more instances. 

VSL are aware of the issue but it is not a priority for them to fix as it might be a third party issue (they mean Steinberg I assume?). But that's a bit hard to swallow as this problem was introduced with the change to the latest iLok version of VEPro without changing any other part of the setup.

I might be wrong but this appears to be a regression of a problem that was fixed in an earlier version as the exact same issues were present and then fixed in a VEPro release. https://www.vsl.co.at/community/posts/t52574--SOLVED--Cubase-10-Super-Long-Load-and-Close-Times-VE-PRO-7

Anyway - hopefully VSL will read your message and it will help increase the priority to fix it as it indicates that it's not just a single user with the issue. 

Hi, santamorphic,

Good call with the decouple mode, thanks. That sure speeds up the saving session times on Cubase.

Never had the need to use the decouple function before, but it's a good thing it's there. Saving the server status was actually something I already did by intuition.

That said, I still hope that the good people from VSL will take its time to optimize the save times. It's understandable that switching from a licensing procedure to other will have its ups and downs, and things will get better with the following releases.

Yes. And among the perfect storm of new operating systems, new chipset on Apple, and switching to iLok. Yikes! It's a lot to juggle.

Just a quick update to this thread.

I've acquired a second iLok dongle (2nd version), and after moving all licenses from cloud to it, didn't notice any loading/saving improvements.

Anyway, I guess it's always good to have a second iLok dongle close, just in case.

Good call, Thomas G!

I uninstalled the Pace software from both main and secondary PC, and reinstalled it.

Yes, it seems that finally the saving project time is similar as it was on eLicenser.

Thank you!