Is anyone also having trouble with the actual build of VEPro and Omnisphere on PC 64Bit? I tried to load several sessions I started yesterday and always there are no sounds loaded inside Omnisphere. Very strange issue ?!? 

Worked again after rebooting!

My previous thought, that the reboot helped, was wrong. The reason why it worked again in that situation was because I opened an earlier version of a project afterwards. Found out that up to a certain state all saved logic sessions are affected. If I open session-files (of the same cues) that are older than about 3 days, omnisphere loads correctly. So the problem is that the plug-in in logic doesn't safe the current state of omnisphere anymore.  

Is it safe to go back to build 7043, and if so, do I have to do that on all machines?

Be careful if rolling back.

Try and save the VEPro projects or Metaframes independently of Logic if you can. Give those saves unique names so you know which version of VEPro saved them successfully. If you can go back to a working version of your Logic project, then save out the VEPro projects (with unique names, i say again) THEN roll back (ie re-install an earlier VEPro) and see if they open.

Try and keep all your options open by saving everything you can think of!

I had a big issue a while back where a certain (beta) version of VEPro was not backwards compatible. it was a nightmare that unfolded and unfolded project by project.

When you roll back (if you decide to) use the VEPro uninstaller (inside the application folder) first. Then re-install the version you want. Do it on all machines everywhere. Save you install packages somewhere safe too (as VSL website does not necessarily archive all versions, al least not as far as I know).

It's good you can go back to early Logic versions. That will be your life saver.

Good Luck.

PS If an earlier version of your Logic project has the right sounds (but out of date compositional development) open that older project, after rolling back VEPro. Then preserve the VEPro instance and save that outside of Logic. Then, load your current Logic project, (the opreserved instance will stay up) and re-connect the VEPro plugin to the saved out VEPro project. Do NOT load plugin data from the later Logic project into VEPro. It should work. But as I say - backup up everything so you can go back to where you were (even if that point in time is not working).

Hello bcslaam,

Hmm, we cannot reproduce this behavior here with the latest builds - please install VE Pro 5.2.12808, make sure you haven´t activated Decouple Mode in the Server Interface Plug-in and see if this still happens.

If it does, please send a zipped copy of a small PT session, which illustrates the issue, to , so we can better look into your problem.

Best, Marnix

Thanks for replys. Well today it didnt happen. Loaded fine. Weird. Maybe it is a win8/pt thing. Hope it's not one of those things that happens intermittantly just when you dont want it.

Out of interest was there VEP update that improved it earlier in this thread? Something to watch out for?

BTW Decouple mode was off. Will update to 12508 and report if required

Cheers

I've found that if you previously save a multi in omnisphere with any name (in the user directory), omnisphere will load the session as usual.

And, if you have more than one omnisphere in the project, only the first one is affected by the problem.