I hope to be able to help some with this and ask for your indulgence for the original posters that I publish here! Thank You!
Source: www.kvraudio.com/forum/viewtopic.php?t=482961

Omnisphere forgets the presets and just shows a blank space

1.)
So from now on I use separate instance of Omnisphere for every patch.
Name the instrument track with the patch name. Also Bounce into audio track for back up.
Hopefully like this should be safer. Even thou now I have 15+ Omnisphere instrument tracks.
I think this is the safest solution for now

2.)
so my advice until you have this figured out is:

1 - load individual Omnisphere instances for each patch/preset if possible or at max [...if possible.. ]
use as little of the multi slots... i have 2 reasons for this advice

1.1 (in my opinion) It saves CPU since that fully multi loaded instance all falls under the same CPU core, at least with cubase and with most DAW under my knowledge.... so even if your other cores are at 10% that one core load will screw you up...

1.2 if it breaks down you'll be able to fix it more easily

2- Save the patches/presets @ -> Utility -> Save patch as -> and create a new Folder
**Note you don't need to fill out all that info/categorys/etc in preset/patch save....
just choose a name for the preset and press save... done

if you just want to overwrite a presets just select --> Utility -> Save patch quick
Hope it helps

 

When you open the plugin, close it when you are ready tweaking. Do not save your project with the plugin on the foreground, always close the plugin and you are set.

 

This issue is not new. I have experienced this issue of Spectrasonics products not recalling presets since the Spectrasonics Atmosphere days. I have experienced it over the years on various Macs, using Logic Pro (versions 8 through to 10.7.4) and also in GarageBand and other DAW hosts. It happens randomly and sometimes affects only one preset, while other times virtually all of the presets (factory presets included). Sometimes it would magically start working again all by itself. This has also been debated and discussed at length on the Omnisphere support pages.

I also read somewhere that you can delete the "net.spectrasonics.V6.plist" from user/library/preferences folder (on Mac, of course). You will not be able to reauthorize until you have restarted. Apparently, that works.

For me, the only way to get around having a blank preset is to name your MIDI tracks as soon as you can. That way you can at least find the preset again and reload it, or copy the MIDI track and apply a different preset and then choose your original preset again and delete the original MIDI track.

I must also add that I have had this issue a few times with Nexus 3 and Kontakt 6 as well, but that's only once in a blue moon.

 

Last advices are big bullshit. Previous omnisphere cracked versions are time bombed.

 

And people question why I stick with Win7? I've not had ANY of these problems you guys have with MACs/ Win 10 /11

 

Because you probably still run Atmosphere?

 

Assumption is the mother of all fuck-ups

 

If my experience is useful, with Spectrasonics Omnisphere v2.8.5f WINMAC [MORiA]:
No problem in Studio One, but no recall of presets in FL Studio.
So:
1. Uninstalled Spectrasonics Omnisphere v2.8.5f WINMAC [MORiA]
2. Removed all traces
3. Installed Spectrasonics.Omnisphere.v2.8.5e.Incl.Patched.and.Keygen-R2R

Now;
Studio One OK
FL Studio OK

 

Hmm Perhaps the cousin of all fuckups is the lack of a sense of humor

 

Very true. In fact? people who laugh at their own jokes are usually the worst sufferers of sense of humour bypasses.

 

I am not laughing at my own joke.
The ROFL is a clue to some others that what I wrote ... is also a joke.

 

I wasn't referring to you anyway. It was merely a general observation.

 

I may also be merely making a general statement of fact.
......
Although the fact that our statements are posted as responses to each other makes me think that we are full of shit.

And that is not a suggestion that I am drunk.
It's just a clue for others to drink.

 

I'm still on 2.6.1 for Omni, and equivalent levels for Keyscape, Trilian and RMX and have stayed there because it all WORX flawlessly.

I have perused the install processes for the more recent "updates" and found all sorts of various junk install methods trying to root around installing the stuff the way it did with 2.6.1 and previous. The spectrasonics stuff is a precarious lot and prone to all sorts of version conflicts, authorization issues, and operational malfunctions if not installed and authorized with the proper keygens just exactly correct and in the right order.

Symlink installers for ANYTHING spectrasonics is just asking for trouble...

 

Well well, since 2015 I have been dealing with this issue, let's see what's new about it

How have been you doing with the legit version, are you still having this issue?

I have been using Omnisphere since Windows 7 and the problem was still there, so is not only the OS version.

Have anybody used these versions and finally fixed this issue? I know there are some last R2R, MORia and vkDanilov versions, which one is the definitive version to put an end to this once and for all?

 

I know this might sound ridiculous then but have you got the relevant windows updates for your computer ?

 

Since I posted this message I installed the vkDanilov release, I have been using it for 1 year and I never got the timebomb problem... until now!
Fortunately I never have stopped saving patches, but I really thought that issue was forever gone :c

 

Spectrasonics Omnisphere v285f Win Mac MORiA