Does anyone have Omnisphere 2.3.2h working on Mac?

I had Omnisphere v2.0.3d installed and working ever since it was released with no problems, I decided to update it and it keeps prompting for a challenge code over and over. Here's what I did:

* Installed all the updates = 2.2.0e, 2.2.0g, 2.3.0c, 2.3.0h, 2.3.1, 2.3.2h
* Then I copied the Omnisphere.vst and Omnisphere.component files to my desktop and used BatChmod to reset permissions on them both. For BatChmod I set the username to my username, checked all the boxes for R-W-X and checked the box for "Change ownership and privileges". Then I copied the VST and Component files back to their original location.
* Then I used the same hexwars patch to generate the Challenge Code which I used for 2.0.3d back when I installed that. It accepted the Challenge Code generated by the hexwars tool and said to delete the Omnisphere VST instance and re-add it. But whenever I re-add Omnisphere to a MIDI track, it prompts for the Challenge Code again.

Am I doing something wrong? These were all downloaded from audioz.

 

I haven't touched the OSX one in a while, mainly using my windows machine. In reading your steps, I see one possible missing one. Did you patch the plugins? Setting the permissions isn't modifying the actual plugins to take the keygen information.

 

Omnisphere 2.3.2h update working fine for me on macOS 10.12.3 and LPX 10.3.1.
Changing permissions is not necessary - you need to extract and patch the component and vst files using the keygen with windows.
Same procedure after each new update.

 

Use the R2R keygen, and patch plugins, then they should work w/o having to enter sn again.

K-))

 

why is everyone updating anyway ?
if it aint broke why fix it ?
whats in new version that is needed ?
just curious , best of luck with your dilemma !

 

Maybe because of the preset reset bug.

 

oh , maybe so ?
hehe -
havent had any problems here - what exactly happens ?
all your presets get reset ?

 

I think you have to use the r2r patch/keygen

 

wuzzle,

I only patched the last update that I installed. I installed 2.2.0e, 2.2.0g, 2.3.0c, 2.3.0h, 2.3.1, and 2.3.2h all back to back, then I only patched the final update 2.3.2h. Do I need to patch them all after each installs?

 

I got it working thanks to another post here on audiosex:
https://audiosex.pro/threads/succesful-omnisphere-install-fails-with-update.29707/

I typed up the steps I took to get it working, just in case someone else has this problem and finds this post.
* Install Software Update v2.2.0e
* Install Software Update v2.2.0g
* Install Patch Library Update v2.3.0c
* Install Software Update v2.3.0h
* Install Software Update v2.3.1
* Install v2.0.1c Soundsource Library Update (came with the v2.3.1 software update)
* Install Software Update v2.3.2h
* Navigate to “Macintosh HD\Library\Audio\Plug-Ins\VST” and copy “Omnisphere.vst” to the desktop. Then navigate to “Macintosh HD\Library\Audio\Plug-Ins\Components” and copy “Omnisphere.component” to the desktop.
* Then launch “BatChmod”, browse to “Omnisphere.vst” on the desktop, change the owner to your username, change the group to “wheel” and check all the R-W-X boxes, check the “Change ownership and privileges” box, then click Apply. Then browse to “Omnisphere.component” on the desktop and do the same. Note: I'm not sure if the BatChmod part is necessary or not but I did it anyway.
* Copy the VST and Component files back to their folders and click “Replace” to overwrite the old VST and Component files.
* Launch the ”R2R KeygenSpectrasonics_2048_KeyGen.exe” file which comes with the Omnisphere v2.3.2f update. I use KeyGen APP to run the keygen. Then click the “Patch” button in the keygen app and browse to “Volumes\Macintosh HD\Library\Audio\Plug-Ins\VST\Omnisphere.vst\Contents\MacOS\Omnisphere” (the R2R keygen browses into the VST file). The keygen should say “Patched Successfully”. Then click “Patch” again and navigate to the AU file (Components\Omnisphere.component\Contents\MacO\Omnisphere)
* Open your DAW and launch Omnisphere

 

@nstell79


Ok... I saw your post on the other thread.

Could you do me a huge favor and see if your AU works in ABleton?

Want to see if my issue is unique

 

@GreatJobChamp I launched the Omnisphere AU in Ableton and it loaded with no problem. It didn't pop up with any license issue/etc either.

 

WHAT?!!!


I gotta mess with it.

Are you a legit owner of Ableton?..

You can PM me that answer. I am curious.

 

Ok so it was not working for me in Ableton! but I went to the Components Folder, and I put the Omnisphere Component in BatchMod and clicked on "Apply to enclosed folder", and now it is working fine! Give it a try.

 

How did you get the 2.0.3d install to work first of all? I downloaded it and the iso files had no install. Was just an internet link and a steam folder.

 

Completely agree. Especially with something as big as Omnisphere, I always read the change log because if it contains nothing you consider essential, leave it. I've been through the whole "cannot locate Steam folder" after updating and have had to rebuild from V1.

 

I have Omnisphere 2.6.2 installed and working but its only the DEMO mode on Mac?

So after 15 mins it stops working.

I have a folder in the download called !Patch with two files only : Omnisphere.component, and Omnisphere.vst

I have copied these over (as these must be the cracks) to Mac HD > Library > Audio > Plug Ins > Components and the same but folder VST
And overwritten them.

Omnisphere still launches in Demo mode?

Any ideas? when I got this full 2.6.2 download, I was told I wouldn't need a PC for any keygen and it can all be done on the Mac (as I only have Mac) - Is there a simple solution that I'm not doing correctly?

Thank you

 

Last version working fine ( Mojave and Catalina )... open your au and vst copy the omnisphere binary on desktop patch with the keygen R2R and replace in your plugin ... generate your challenge response close and reopen and you are fine....

 

THANK you however I am on High Sierra and it works fine apart from this demo issue.

When you say Keygen R2R, can I do this within MacOS as I don’t have access to a pc