ROLLBACK TO PRE-VEP-VST3 VERSION

[garrcrowley_yahoo.com]

WINDOWS10-CUBASE11 (elicenser) VEP 7 (ilok) KOMPLETE KONTROL MK2 SONARWORKS, KONTAKT 5-6 (I run everything but a newer Klibrary out of K.5.

The issues I'm personally running with VEP7 are kind of consuming the work day now, it's a pretty miserable, anger-frustration  filled work place right now, probably for you guys also.

I don't want to even take the time to list the myriad of problems I'm running into. Ilio has a book now built on my phone calls

However-ALL-as in EVERYONE of my issues stop when I delete VEP7 from projects, so that's what I'm going to do for now. But I've $1,000's of dollars of VSL instruments as the basis for my templates and in in-process projects that I want-actually-need  to continue using from VSL.

So, for me, right now VEP7 is toast-burnt, and I don't need the aggravation anymore, but I need to find a way to use the  VSL instruments.

. All of my VSL product has been converted to Ilko.

What I'm wondering is can I roll back to VEP6, and run the ILOK libs through that?

Or, as everything from VSL is still on the e'licenser, can I convert back from the ILOK  and run e-licenser versions again.

Or ---is there a working version of VEP7 to roll back to that predates the VST3 problems?

I feel for you guys having to deal with all of this from all of us.

I'll continue to keep watching the forum(s) for a resolution to these vst3 issues, to hopefully go back to VEP.

Thanks!

g.c.

[Paul]

Hi Garr, 

Sorry to hear about these troubles, we're working on the VST3 hotfix right now. 

Let me get to your questions: 

1) What I'm wondering is can I roll back to VEP6, and run the ILOK libs through that?

• A: No. 

2) Or, as everything from VSL is still on the e'licenser, can I convert back from the ILOK  and run e-licenser versions again.

• A: Yes, with all libraries you purchased before March 17th, 2022. All newer licenses will only work with iLok. 

3) Or ---is there a working version of VEP7 to roll back to that predates the VST3 problems?

• A: Yes, there is 7.1.1406, but without VST3 support. 

Hope I can get back to you with a solution soon.

Best, 
Paul

[garrcrowley_yahoo.com]

Thanks Paul. I'll do the 7.1. rollback to get back to work .I'll keep watching you guys and see when you have success with your albatross.

So sorry you guys have to go thru this.

Paul, at your convenience, could you also advise me as to the following:

I've been told that even though the VSL libs are all ilok we still need to NOT delete them from the elicenser, something I didn't understand about VEP or VSL needing see the initial reference to the original licenses. Do we need to sustain the elicenser as long as w work with the VSL instruments?

Thanks again for such a quick followup. The best

g.c.

[Paul]

Hi, 

There is actually no way to delete the licenses unless you destroy the key.

You don't need to keep your eLicenser key containing the old licenses around UNLESS you want to open old projects on a computer that is not connected to the internet. 

With an internet connection, the VSL Helper will take care of that conversion for you. 

VST3 bug will be fixed in the update tomorrow. 

Best, 
Paul

[Cochise Studio]

Hi Paul

Where can we find a link to VEP7 with an earlier installation for windows? I need to roll back, I can no longer open several projects.

I haven't been able to find a link or a solution to roll back.

Thank you.

[Paul]

Hi, 

Open your Vienna Assistant, go to Vienna Ensemble Pro and click on the three dots. 

Select "Rollback" and choose the version you want to use.

I wonder why you can't open those projects, would be very interesting to check that out, if you want to send them to support@vsl.co.at with some reproduction steps!

Best, 
Paul

[Davka]

Just updated to VEP 7.2.1516 on Windows. Can't open my Hollywood orchestra template on this version. also couldn't find 7.1 version on Vienna Asisstant... Where can i download 7.1 version?

[Franekp]

Hello. I am also having problems after updating to the latest VEP7 v.1516. Opening VEP7 projects with Studio One causes the most failures, in so far as as soon as I try to view connected vst3 products such as Halion Sonic (SE, or 3, or the new 7), and Padshop and Retrologue, will always cause a VEP7 crash. The same problem occurs even if just trying to use VEP7 in standalone mode - although this never used to happen up to a couple of weeks ago.

Sometimes, using VEP7 in conjunction with Pro Tools or Cubase v11  as DAW's seems to work better, but then before long, VEP7 again crashes (after various nonsense messages appear concerning alleged missing licenses - which I certainly do possess).

[Andreas8420]

Hi everyone!

As mentioned, you can use the Rollback feature inside the Vienna Assistant (right-click context menu). Please contact us directly if you would like us to look at your crash reports at support@vsl.co.at - thank you!

Regards,
Andreas