Update:

I downloaded the latest version of Elicenser Control center and now I can open up the Cubase project normally. I do get sound fromthe samples loaded in VEPro, but the interface is completely unresponsive when connected and if I try to save the project Cubase stops responding.I use the settings I had before the hassle with Windows (2 cores per instance, Fast GUI enabled, Kontakt multicore disabled), so I'm really starting to feelthis is because of the Windows updates...Any ideas?

I've run into a  little problem with VEPro and Cubase: Cubase freezes when I first load up my VEPro template and try to make a new project, or open a existing one. I get past the "loading mixconsole" message, but the project itself never comes up. When looking from the task manager, VEPro seems to be fine,  but Cubase is not responding. If I force VEPro to shut down, Cubase immediately starts responding and the project window comes up. If I open a Cubase project first and then my VEPro template, VEPro gets stuck on loading the channels.

Has anyone else experienced this kind of behaviour? Things were working fine before and then I had to reinstall Windows because an update messed up my whole system, so I'm beginning to think some windows update is the culprit here...

Software versions:

Windows 10 Pro 1909

Cubase 10.0.50

VEPro 6.0.18442

(Already sent a email to support with dump files, but might as well ask here...)

Sorry for my ignorance, but if I were to do this I wouldn't be able to process, for example, my individual percussion instruments individually inside Cubase? That goes against my preferred workflow, which kinda sucks.

Sorry to flood this thread with messages, Paul, but this is getting quite ridiculous. I'm currently balancing my template and it's almost quaranteed that the noise burst happens at least once in every session (I reinstalled VEPro 6). I know you guys are doing what you can, but do you have any idea about what might help? Even with the safety measures I've taken it's quite hard to ignore the issue when my meters are flashing red.

So I did a little test with VEPro 7: I went around my template enabling/disabling pretty much all my instances of Kontat, Play and Engine. Happy to report that I didn't get any volume bursts. Looks to me (with the little amount of testing that I did) that the issue is with VEPro 6.

Hi Paul, any news about the issue? Happened a few times today too, with instances of Kontakt, Play and Engine.

Sure!

Windows 10 Pro 1803, 17134.706

VEPro 6: the latest version

Cubase Pro 10.0.20

Kontakt 5.81

Play 6.1.1

Engine 2.6.0.33 (I can't be certain, but I THINK that most, if not all noise blast occurences have happened when I've enabled tracks with Engine 2, with multiple patches loaded into one instance)

Focusrite Scarlett 2i4 1st Gen, Driver 4.36.5

Hi, I know this has been a problem before and I've begun encountering it recently. Happens sometimes when I enable a disabled track inside VEPro. Not sure what is causing it, I've disabled ASIO guard for VEPro and set it to low for the whole project. I understand an occasional bug, but this is on another level. Disabling my monitors everytime I wish to enable a track is getting quite tiresome. ;) Any ideas?