I had to do that several times with a few plugins in Pro Tools. I remember Kontakt forgetting what instrument I was using. Drum Lab didn't recall what kit or edits I used. It's such a pain, but leaving notes on the track helped a ton.

 

I have been doing that but I like to edit and assign stuff in Omnisphere to macros in Live etc. Thanks anyway

 

This FU##ing issue still remains. Sry it is just so annoying. Anyone found a fix for it yet. I have been scouring the internet for a resolution myself but cant find an answer.

 

This is the one that really kills me. I can save the multi, the project, the individial patches that were edited or created. But once you lose the original patch, you have to re-enable all the parameters for host automation, reconfigure the Synth's device container in Live, remap the macros, redo all the macro boundaries, and then copy and paste the automation envelopes. What a smack in the face to any creative spark you might've had going.

And then it works... if and only if you set the macro boundaries correctly. Does something sound a little off in my mix? Why is that distorted lead getting so screechy? Fuck me I guess I'll putz around with my macro mapping for another 15 minutes before I write a single note.

 

I feel your pain bro . I'm in the fucking cunting middle of doing the remapping dance "again" myself. It has now got to the stage where I am getting afraid to even use O2 anymore. What a useless crack! Don't get me wrong I am grateful for all the wonderful software we have been given but ffs 99% of what I have just works. Its almost like this crack of O2 was a middle finger at us "mere" end user mortals just b4 the geniuses decided we don't want to play with you leechers any more and took the fucking ball away.

 

Last edited: Sep 27, 2015

I get that you're frustrated but perhaps before you jump to completely ludicrous conclusions you should get to the bottom of the issue. The teams would never do something like that and it's not related to the crack, especially since it's a keygen not a crack or a patch. The key is either accepted or it's not, there's no middle ground. Also, this is an issue that has appeared in older versions of their plug-ins as any search will yield these very issues, along with posts specific to Omnisphere 2. The reason that there aren't more complaints is because this issue seems to be very sporadic. Apparently, their support recommends deleting some file but I have no idea which one. Perhaps someone that owns it legitimately can contact support and get back to us with an answer.

 

I spent some time looking around for Spectrasonics files in the usual suspects - Program files, Common Files, Documents, AppData, ProgramData, etc... Compared to many other VSTi Omnisphere really doesn't leave almost anything on your computer. A few files in Program Files, A few in AppData that seem to be related to presets or templates, the licenses in ProgramData (and a couple other things), but there's not much to pick from if you're looking for a file to delete. Deleting the authorization files seems to be our best hope.

Your post really went under-appreciated here. I wonder how many actually tried this. Even if it's only a temporary fix, it seems like it'd be worth the little effort it takes. I did something very similar to this two nights ago. I've since run some tests where I create a couple Live projects and just repeatedly change/edit patches and save the project (but not the patches) and haven't lost any patches yet. Here's what I did:

1. Move the authorization files to another folder. On Windows this is located at C:\ProgramData\Spectrasonics\AUDIO16
there's another authorization file starting with AUDIO. Can't remember the number. I moved that one too.

2. Open DAW and run Omnisphere unauthorized, then close it.

3. Delete the AUDIO16 file that's created and return your authorization files to their folder.

This is just a hail mary, but maybe you should try deleting the license files and then running Omnisphere unauthorized like I did. It will create a new AUDIO16 file and just maybe that's part of the solution. Worth a shot, right?

So far so good
I've tracked down someone who agreed to help out with this. If we're lucky he'll have a better answer. In the meantime I'm crossing my fingers that the problem stays fixed.

 

Oddly on the same project in Logic, one Omni patch looses on reload and the other two stay. Happens randomly it seems. I don't want to mess too much with the auth files since I can't afford to have problems if it doesn't go right.

 

Still the same issue here, i think the problem is the cracked version, i understand the Catalyst said but for me it isn´t possible that nobody that had paid for Omni 2 had this issue. I have searched this problem for a long time on the web and could not find anything on any page or forum. It seems that only happens with the audioz version.

 

Maybe u can map some parameters in a midimapper like the plug from cableguys and save your edited preset a bit?
I do not make us of O2 so i cant test it for you.

 

Thing is, it's not cracked. It's keygenned. R2R (almost?) always uses keygens, which I understand is a more difficult process, but allows the user to update the software without needing a new crack every time. The patch that goes with the keygen only messes with the protection, and as @Catalyst said, the protection either accepts the generated key or it doesn't. Clearly your copy of Omnisphere 2 accepted R2R's key or we would be in a "R2R's keygen doesn't work" thread instead of an "Omnisphere doesn't work" one.

There are reports of this issue going back to Omnisphere 1. Stylus RMX and Trillian too. The only thing that's worth questioning is why so few for Omni 2, but even for that there are a couple. There's no telling if those reports are actually a retail license or a warez version, but one was on KVR I think, which is notorious for being hateful toward people who use warez. Consider this: users with a retail license would probably have contacted support before complaining on a forum like we're doing.

Another thing to consider: we all got Omnisphere 2 from the same installer. It seems highly unlikely that the installer was unique to the degree that it could have caused this problem where others function properly, but still worth mentioning that every single person with a warez version of Omnisphere 2 got it from the exact same installer.

And what if a retail owner comes in and says you're supposed to delete the authorization files to fix it. Will you still not do it? Sorry man--not trying to be mean but--if you're not willing to even try the only known potential solution nobody's going to have any sympathy for you. You don't have to delete the Auth files. Just move them out of their folder and run Omnisphere once, then put them back. That's been working for me for a couple days, and Omnisphere reverted to authorized like nothing happened. There have been very few posts in which anyone was unable to authorize with R2R's keygen, and most or all of those were either user error or conflict with previous versions. Have a little faith that even if something were to go wrong (spoiler: it won't) you could always generate a new key. If the keygen worked for you once, why would it not work again?

Unfortunately the problem is that Omnisphere is so massive that parameters are not automatically visible to the host (DAW). You have to manually enable them. So no matter what I do, if Omnisphere loses the patch, I have to re-map everything from scratch, starting with re-enabling the parameters. Once I do that, they are somehow not compatible with the previous mappings. However, I really do appreciate you taking the time to offer a solution and I will give it a try anyway

 

Last edited: Sep 30, 2015

Is replacing the backed up file (mac plist) any different for this fix than auth'ing it from scratch again?

 

Sorry, I'm not computer savvy enough to answer that for you. I just know that this worked better for me than simply deleting the authorization files and reauthorizing. The only differences that I know of are superficial and don't offer any insight into the way the plugin works. They are:

a) I replaced it with the same authorization that was there before, and
b) Running Omnisphere unauthorized created a new AUDIO16 file which I then deleted.

Beyond that...

 

I can´t find this audio16 in my mac, i know you are on pc, if somebody knows please tell me

 

I have this problem as well, and at least in Live, a solution is to freeze the track where you have Omnisphere. Once you freeze the track, it loads perfectly. As far as the mapping is concerned, I haven't messed with it. How do you actually automate stuff with omnisphere in Live?

 

The problem occurs most when you use multi mode, in multi you can´t freeze the track. I use always in multi, and the automate for me is impossible to save. I have to enable every parameter in omni 2 every time that i open the song, a really pain...

 

@anvier

Found this in another thread a while ago while I was looking for Omnisphere solutions

@pfc1990 I like to do glitchy stuff so I make a lot of edits and don't like to freeze. I'll write a melody, leave it there as a placeholder then go back and mess with mod wheel routings, pitch bend range, and map all sorts of parameters to macros

 

Last edited: Sep 30, 2015

Couple of things:

1) It is cracked, it is not a true keygen which means the binaries have been patched aka: the RSA key has been replaced. By definition anything that involves patching a binary in order to circumvent copy protection = cracked.

2) Omnisphere 1 had (among other things) a multi save bomb that prevented patches being recalled. More precisely, not all the multi data was being saved. There was a secondary BigDigit number that performed some calculations on the RSA key to confirm it's authenticity (in case it was replaced). If this test has been bought forward into Omnisphere 2 (which I suspect it has) then it would explain the weird behavior problems many have seen.

 

Thanks man, i did it in mac and it seems to work for now, i´ll prove it for a couple of days and went to inform if still works.

Really thanks for the tip Cav emp.

Edit: still works fine for me, Thanks Cav Emp

 

Last edited: Oct 15, 2015

Well you could be on to something here then.