Have any of you that are getting no presets saved, teseted it in demo mode
to make sure its just the patched version that has this error and not the plugin its self ?

 

SO2 don't know but SO3 no problem

 

Yes it does with more than one instance of Omnisphere. Works like a charm with only 1 but when another is added all hell breaks loose.

 

I was thinking. May be silly but hey... Worth a shot. If the Audio16 file is part of the issue? Maybe make it read only in properties and in security? Same with reg file? Just a thought or two. I did it and we shall see. Opened up fine no issues no patch loss... So.... Far... lol

Same with anything default. Like default patches and multi's. Lock them the same was as well?

 

I tried saving one project with omni in live mode...on the next load i got empty omni ... With my new pc system I have yet to experience loosing of the patches, but I did once when I tried your suggestion with LIVE mode. With normal mode I haven't ...yet . Although, I am NOT a big omni user, I don't use it that often at all.

 

Maybe it was already posted, but my personal solution is saving the patches of your song in the folder "user", I created one called "Songs", then another called "insert song name here", then if the patch I am saving is the patch #3 of the multi I name the patch "3 Deep Chord" for example.
Also I save the multi with the name of the song/project so the volumes and aux of every patch are saved as well.
My O2 stills behaving unpredictable, sometimes the patches are loaded, some times I have to load them manually with my solution, but is not big deal, just 1-2 min loading your patches and then I can continue making music, just remember, if you change anything in Omnisphere you should save the patch/multi ("Save patch quick" option) to prevent the risk of not loading the patches next time.
Oh and there is also an option to save the MIDI learns you have made in the multi, so you should save it too.

 

Last edited: Apr 25, 2016

Siiiigh...

 

Thx dude, that sounds pretty solid.

 

Hey all. There is a bug in Omnisphere 2 that somehow checks if your DAW is legit. If it is not... That is how you get this problem. I always used the REG. Code with FL Studio. I never actually signed in from the About in the ? menu. After I signed in ( I did purchase FL Studio ), all issues with Omnisphere 2 stopped. I think that is why DAW's like LMMS which are free... Do not have this issue. I always thought the REG. Code I got from my imageline account was good enough... But, seems for some reason it was not. So, after I signed in. All issues and bugs stopped for me. Might be different for you but thought I would mention it.

 

Hmm. This is interesting. I haven't had any issues with Omnisphere 2; but I do run a legit copy of Cubase Pro 8. Maybe that has something to do with it. I'm an advocate for at least owning the DAW you use. And this may be one more argument in favor of that. Thanks for the info.

 

I think it sound strange. I am having some trouble understanding why Omnisphere would care if you are using a legit DAW or not.

 

Well I haven't changed anything in my DAW since the problem appeared, but now from months I have had just 1 time the problem from 50 times I have opened Omnisphere. Nevertheless I still using the solution I posted above so I will never lose anything.

 

I have a legit Cubase 8.5 but it happened here a few times. So either it's not that, or it's not JUST that,

 

I have a legit version of MPC Renaissance and Logic Pro X...still having the same problems as everyone else. Omni2 loading INIT files when loading previous projects...

 

The best way to solve all of the problems is to buy the damn thing already

SOLVED!

 

Saving your custom patches separately in the plugin and the DAW is just good practice but if for some reason you're still having problems with empty Multis on load-up try freezing the track before saving/closing your project.

 

Saving patches works for me.

 

Works 4 me 2 in cubase pro 9

 

Hi,

Since I updated to omnisphere 2 I had this issue with recalling patches.

I tried so many different things but nothing worked so war.

I also mentioned a guy with the same issue on a legal O2 but he contacts Spectrasonics and they helped him out but he did not tell how he fix it.

So, there is an Issue but how to fix that that’s the big question maybe not for all user but for some of us and I still hope to see a fix for that.

But for now, on I have to live with that issue and hope that one genius guy will get us out of this.

 

Like @koschke with his reply before this one already mentioned, even some people with legit copies have been known to experience this issue. Apparently you need to delete a certain file and let Omnisphere rebuild it to resolve the issue and make sure it won't happen again from then moving forwards. Too bad it's impossible to find online what this particular file would be and only somebody with a legit license could contact the Spectrasonics support and ask them.

I just made a habit out of bouncing out early and I don't use Omnisphere all that much anyway. Maybe anyone else here can be of better help, I don't know. Can imagine it to be a huge problem if you'd use Omnisphere a lot, but then again, those are the kind of people that should just buy the product.