Hey,
I installed and updated Omnisphere 2 to the latest software update (2.6.2), library and soundsource(2.6.1).
The issue i'm having is everytime i save a project, when i go to open it again it, Ominsphere didn't save the preset and launches in 2.3.2 software.
It also gives me a message saying "This path library requires a newer version of Omnisphere".
I've already looked everywhere for a solution, but nothing helped me yet.

 

https://imgur.com/fUGqKQz

Here is screenshot of Omnisphere when i open it on a saved project

 

How can it load 2.3.2 if you updated to 2.6.2?
Doesn't sound like you installed 2.6.2
Plus, "saving a project" in your daw is not the same as saving a preset in Omni.
Anyway, I think it's because you were somehow able to open newer patches which require 2.6.2

 

The thing is, if i start a new project in FL, Omnisphere loads up with 2.6.2 software. It just goes back to 2.3.2 when i reopen a project after saving.

 

Spooky! Sorry my friend, I have no idea.
If it's the version on AZ from The Pirate, maybe you can tag him so he can help you.
Plus, if this is 'a thing', it's probably been answered somewhere here on AS already...

 

Last edited: Jan 19, 2020

get rid of the 32bit version cus its still unpatched, look through the plugins folders

 

@canti47 The issue you are having is typical of a Spectrasonics upgrade that left over dll's from a previous install. Most likely, it is the 32 dll from the previous version being scanned by FL Studio.
The easiest way to find out is to run a plugin scan in FL Satudio searchin for term Omnisphere. In a perfectly installed Omnisphere after version 2.4 there should be one dll. The 64 bit version. Any other dll must be delete.

Edit: As I explained to @p4V3l below, after version 2.4 any 32 bit Omnisphere dll is not compatible with the 64 bit dll. All it does is create conflicts. Both get scanned, and because both are authorized, the 32 bit one ends up "cancelling' the 64 bit.

 

Last edited: Jan 19, 2020

It has nothing to do with unpatched. If it was unpatch it would not open. The problem is that there is a 32 bit dll that was PROPERLY patched and authorized. That is why it opens. in other words, you dont delete the 32 bit dll because it is unpatched. You delete it because it is not longer compatible with any version after 2.4.

 

yeah i should have just said

thank you for clarifying pirat

 

Holy! Thank you bro!
Just needed to delete 32bit dll and it started to work how it was suppose to be.
I was already getting really frustrated