Hey guys,

for the first time I seem to be too stupid to make the proper update.

I come from stable v2.6.4c that worked flawlessly (with Soundsources 2.6.1c, Patches 2.6.3c).


I made the Update to 2.8.0d from 10/26/21 on sister site. Did everything as it always had to be done and as it's written in the description, but it's not authorizing. Never had problems with authorizing Omnisphere before, maybe I did a mistake this time?

1. Installed the update (not manually - the pkg worked in my case)
2. Copied the provided prepatched files to plugin destination
3. Started Omnisphere and got my challenge code with the help of urldecoder (without the URL)
4. Pasted it to Spectrasonics_2048.exe keygen and repasted the response in Omnisphere. Restarted the plugin/DAW, but it keeps asking me for authorization.


I also remember a long time a go, there was a keygen that let me patch the plugin-files, while this one is just a keygen without patching function. But the plugins provided with the release were already pre-patched, right?

I'm really struggling with this one..

 

Edit: Just went back to 2.6.4c

Thanks god that worked at least!

Hope that somebody can help me with the 2.8.0 update because I think that Undercurrent is the best electro-organic / hybrid / analog sounding cinematic soundlibrary that ever existed. Forget everything else, forget the most expensive Diva Soundbanks, Kontakt libraries etc.

Btw, just to share some experience - don't know if it's really true, but I was suffering quite a long time under the issue that the presets would dissapear after reopening a project. 2 years ago I think that I found out that this issue has simply to do with the Soundsources, Patches and Software not being on the correct versions (not the exact same versions, but the right versions for each other). Once I started taking care of this, I never had this problem with disapearing patches again.

Anyone observed a similar behaviour?

 

Last edited: Nov 15, 2021

I've seen other users say that after a certain version that there are time bombs set in place to make things like not copying the presets or disappearing presets etc happen but i'm not sure which version it started with but for certain 2.8.0+ is that on Mac you have to codesign the vst/au even after you patch them and authorize

CodeSign:
sudo codesign -f -s - --deep /Library/Audio/Plug-Ins/Components/Omnisphere.component
sudo codesign -f -s - --deep /Library/Audio/Plug-Ins/VST/Omnisphere.vst

After this it all should work for you.

 

I just did an update to 2.8.1c and had a similar issue. I solved it by running the keygen with the patcher in it under Crossover on my M1. Patching the executable inside the AU component package and the VSTs (and then code signing) solved it for me.

 

Any chance you may be able to help me get hold of 2.8.1c update installer for Mac? I have be searching all over.

Diam

 

I got Omnisphere_Software_Update_Mac_2_8_0d last week from somewhere else but then it disappeared off that site. Since I went from working 2.6.4c up to 2.8 the keygen won't work. I still have 2.8.0d if anyone wants to try it.

 

You need to use the 2048 Keygen to patch the AU/VST if not pre patched. The authorisation method also requires you to decode the authorization request online, before generating a response. It is a little more complicated. That should be outlined in the install documentation. There is a 2.8.1c windows version that does not require any Keygen.

 

Try using CrossOver to run the keygen. Patch and generate the response. Then use codesign pasted above

 

Mine got so messed up I uninstalled and reinstalled. I'm on Mac so going to wait till the next release drops and attack it again.

 

Ok well I think my main issue is that I think that I'm having the correct Keygen (Spectrasonics_2048.exe) but everyone is talking about patching the plugins - and it rings a bell, I did that once before a few years ago. But this 2048 keygen is just a challange code responder, no option to patch anything. I must be either totally blind or using the wrong keygen - if so, where can I find the one that also applies a patch?

Regarding the sudo codesign, I'll try that later with the pre-patched files from 2.8.0d release. Maybe that together with the 2048 challange response keygen will be enough. And hopefully enough to run Sonic Extensions )

 

Not sure how to send private messages on this thing, but if you can fire me one, I can try send you the correct file. Maybe tomorrow now though, as Im turning in.

 

;-)

 

Last edited: Nov 16, 2021

That would be great! I sent you a private message. Otherwise a decrypted link to the correct release containing the correct keygen-patcher would also be enough I think.

 

Hi Mate. I saw this message but not a private one. If you have an email or can somehow link me to an address to send it to, I will get onto it right away. Don't have the specific link, as there have been so many, but do have the keygen.

 

tried installing it today on M1, working on macOS Monterey. Apple Silicon Native!

1.installed omnisphere 2.6 complete version.
2.installed 2.8.1c update.
3.patched using old r2r keygen.
4.decoded activation url with https://www.urldecoder.org/
5.entered response code.

Done.

Note: patched au/vst/vst3 on a windows computer, couldn't try crossover and make sure to codesign all plugins.

 

Last edited by a moderator: Nov 28, 2021

Replied to your PM. Hopefully that little tool will get you to the promised land.

 

Thanks man, that was the keygen I was missing!!
Also replied back to your message.

I hope it does get me there haha.

Also to make sure that I don't switch to an unstable combination of patches where the presets won't save, whats the official counterpart to software version 2.8.0d? Is it Soundsources Patch v2.7.0c from August 21? Or does the software update to 2.8.0d already contain the associated soundsource and library patches?

 

Where did you get the 2.8.1c update from? And is it mandatory to not getting the init patch bug, or is 2.8.0d also stable?

 

Look in your mailbox!

 

on sister site. don't know about init patch bug, grabbed it because it was the latest update.