The two versions of VE are the pro version and the non-pro version.  The non-pro version is the old Vienna Ensemble.  It only exists if you need it for compatibility with old projects,

The Invalid project occurs if the conversion to iLok fails. The conversion seems to be unreliable for large projects.  I have noticed two scenarios that work reliably for me.  

One: if you still have e-licenser control center installed, you need to do the "offline conversion method".  Just plug in your e-licenser key to do the conversion.  

Two: if you uninstall the e-licenser control center software, then the "online conversion method" works reliably.

You can monitor the conversion by showing the Vienna Helper app (it's in the right side menu bar).  It shows up if a conversion is needed.  The Vienna Helper app should show only "converted" or "cache hit" entries.  If you see errors or broken pipe messages, then your conversion failed and you'll eventually get an invalid project message.

same problem here (all older projects before the iLok update cannot be opened)

  .... sorry, but that's absolutely ridiculous if this isn't a bug, cause it was definitely not communicated that older eLicenser projects are not compatible

went back to eLicenser version

Hi,

Working on the fix for this, should be there soon. 

Meanwhile, please uninstall 7.1.1249 with the UNINSTALL option in the Vienna Assistant, then roll back to 7.1.1245 manually for now:  

Mac VE Pro 7.1.1245
Win VE Pro 7.1.1245

Sorry for the inconvenience, new territory :-)

Best, 
Paul

Paul, what is the procedure going forward with the iLok version and loading pre-iLok projects?
Are these projects intended to just load without problems or do we need to save new versions while still having eLicenser present?

I believe that old projects loaded perfectly fine with the first iLok VEP7 version so I hope it is just a matter of you getting a fix done so it works again:)

EDIT: With 1245 old projects are all loading fine!

1263 results: VS Pro Equalizer doesn't work. Extant instances are kaput, new instances have no analyzer at all.

The Kontakt 6.7.1 overload upon connecting may have ceased, or reinstantiating the whole thing may have done. But it now, even as I see signal, makes no sound (its keyboard, MIDI from Nuendo, it just doesn't sound.).

Learning Automation in BFD3 while connected to Nuendo or Cubase hangs fatally. VEP is behaving a bit like it's coupled to Nuendo and it is not. Every operation is slower than I've seen since like VEP 4, saves of server project worse than saves of instances. Disabling channels while connected or re-enabling, scary. So any change I want to make I have to close the Nuendo proj to do safely. Add plugin, could crash it. Edit plugin, scary.

1263 may have solved the invalid project per se...

OK, it's more than the Kontakt won't sound. Just now everything except the Kontakt and the BFD3 quit sounding.  at one point instantiating an EQ seemed to stop the sound. 

The no-Synchron in MIRacle is hurting me. I had a killer snare sound in this project, that's gone, EQs don't work. EDIT: oddly, it looks like an EQ on a VI or Synchron channel is fine. All of them in the drums instance are kaput. At this point the project loads with these x-d out like they aren't there. I suppose EQ settings that go back are what wouldn't load. WRONG. The ones I just set up, my day's work, are x-d out upon restart. The correspondence with BFD3 outputs isn't solid, some channels are dead. This I've replicated twice.

This is a nightmare.

The no sound thing is outputs quit, or don't even start, but an output channel can be fine one moment and gone the next. I spent all day and a save I made towards the end ot the day, the server project opened with the EQs and other plugins I had reworked in instance 3 x-d out again. But fortunately the instance saved correctly. But this instance finally wouldn't sound at all. I'm enabling 4 stereo outs, 0 giving me sound (it's all receiving MIDI and showing signal) and I simply gave up today. This instance would alternate with another group feeding the output working while drums don't. Rarely would both sound. The other instances have similar problems except its EQs and such loaded normally every time.

I hope, they'll fix all this after this weekend. 1263 is unusable, thus I can only work with the eLicenser 1120 version in vePro... Sad.

Hey Paul, any updates on all the issues. As of now, 1263 is unusable. I have to stay on eLicenser 1120...

This is a new one. BFD3 in VE Pro (yes it's a big instantiation of) made the project completely unable to perform.
I was waiting 7, 8 secs for playback to recover, hangs, can't view VE Pro for long periods...

I finally went to using it in Nuendo and it performs very well, and the VE Pro project is performing, not well but I can stand it, without it. The opposite of my expectation. But I think this system runs very, very well, just this iLok (I think the layer of translation needing a Vienna Helper is the culprit) is ruinous.

I have just read through this entire thread hoping to see how this problem has been solved (as it says in the header to the thread). But, I can’t see a solution.

I’m on a MacBook Pro running Big Sur after having had to downgrade from Monterey 12.3 with Apple’s help. Why? don’t get me started. But Big Sur is stable and working for me at the present time.

Now, having used Vienna Assistant to transition to iLok, (many more hours to go) my Vienna Ensemble Pro 7 software crashes as soon as I run a project in Digital Performer 11. The crash report is 151 pages of impenetrable code. The project uses 4 instances within VEP7. I’m wondering if the problem might be new locations for some of the libraries used. I had to be creative to free up enough space for the réinstallation of the now iLok encrypted files and some libraries are in new locations. I thought that was taken care of by Vienna Assistant after I changed the location before installing, but maybe I’m wrong.

Any ideas would be welcome.

Sigh…