I am having EXACTLY the same problem. I'm on Cubase 12, and everything has been working fine until this latest update. I can't connect any existing instances, instead what's happening is exactly what's occurring in the video posted. 

I had the same problem with Dorico. I've updated VEP on my slave machine but not on my host. I never did before and it still worked because both versions were on elicenser. If it's the same for you, you'll have to download the latest vep for ilok on both your slave and your host. 

@Karmand said:

WHY?

I just did the upgrade when prompted to update VEP7

I had the same thing happen yesterday with a new i9 slave PC, and new install of VEPro 7.1.1427. 

Roll back to 7.1.1298 and that should fix the problem.  There seems to be a bug in .1427 that causes VEP server to create a new instance instead of connecting to existing instances.  In my case, the new instance truncated the first 4 characters of the name of the instance I was trying to connect to (i.e. connecting to "Strings" would create a new instance named "ngs").  Using the new instances will not work - reloading a project and reconnecting to VEP will just cause VEP to create more new instances. 

Use the rollback feature in the VSL Assistant - in the Vienna Ensemble Pro install icon, under the version, click the three dots - at the bottom is "rollback" and you can select the version to roll back to. 

I'll try a rollback asap (not in the studio for a few days now). I hope that works! Thanks for the info

Hello everyone,

We are investigating these issues, but unfortunately, we cannot reproduce them on our side on any of our configurations. It would be great if everyone experiencing the issue could get in touch with us via support@vsl.co.at and send in the following:

- what OS (and version) is used to run VE Pro (host & networked machines)
- what DAW is used, and which version
- what plugin format for the VE Pro plugin is used
- if the issue is reproducible with a fresh new project
- as well as sending in an affected project file.

Thank you!

Best regards,
Andreas

@Andreas8420 said:

Hello everyone,

We are investigating these issues, but unfortunately, we cannot reproduce them on our side on any of our configurations. It would be great if everyone experiencing the issue could get in touch with us via support@vsl.co.at and send in the following:

- what OS (and version) is used to run VE Pro (host & networked machines)
- what DAW is used, and which version
- what plugin format for the VE Pro plugin is used
- if the issue is reproducible with a fresh new project
- as well as sending in an affected project file.

Thank you!

Best regards,
Andreas

Just sent you screenshots to the support mail address.
How can I please do a proper rollback on a Win machine? If I go with a clean install, I guess it downgrades to the last installer version (2021 something), which might induce some additional trouble. Worked fine with last update (and I once again blame myself for falling to the "update before working on a project" trap).

My current setup is currently unusable, cannot connect my template on any of my existing or new projects. And I'm afraid things will go south when trying to work with the generated instances after this is resolved.

Yeah, I rolled back to 7.1.1298-Apr 14 2022

Seems to be working ok now. Thanks. Rolling back was fairly easy tbf. 

Cheers

Mike

Hi

is there a solution yet? 

I have the same problem. Have 

Hi Honeyhill,

Rolling back to 7.1.1406 is currently the best way to go. 

A new version of VE Pro is in the pipeline!

Best, 
Paul