I just installed omni 2 r2r and everything is fine until I go to use it....I open the keygen and receive a response code I go to paste it and I close out my daw them it brings the same screen up about entering a response code.


I seen some stuff about patching and Im new to this stuff I have no idea what patching is. Can anyone let me know what it is and how to do it in detail.

 

Are you on Mac Or PC?

 

Im on pc

 

Sometimes the DAW can be an issue. I had trouble registering the code when using FL Studio. There is a program you can download call VSTHost. This is what I use when registering Omnisphere, works every time.

http://www.hermannseib.com/english/vsthost.htm

Once you've registered it in VSTHost, the same .dll will work in any DAW ime.

 

so asson soon as I register with this i can go straight to using it in fl 12?

 

It's been a long while but a silly question: did you run the keygen as administrator and PATCH the install (without the DAW and plug being loaded) before attempting to generate a key? Can't think of anything else offhand.

 

WHat is PATCHING give me directions to follow. also i had the daw running when i generated the key. ill try it with thought runnung but I REALLY NEED TO KNOW WTF PATCHING IS ASAP

 

you have to patch it or its not going to work

 

CAPS and bold

 

bro whats patching idk what it is. ive never done any of this before

 

caps and bold?

 

had this problem , i started fl studio with admin

 

You mentioned that you've never done any of this before. Do you know how to read a .nfo file? If not, go to the readme.nfo file, right click and open with notepad. That's basic stuff, but can get a lot of people who've never cracked software before.

With Omnisphere 2 there are also 6-8 different disks to install (I forget the exact number as it's been a couple years). Have you installed each disk successfully? I like to install everything to my D: drive, including the vst. That way I know exactly where everything is, nothing is hidden in folders and finding the VST is a breeze.

This also makes it so that there aren't duplicate .dll files sitting in different folder locations. I've had this happen before and though I was successfully registering one .dll in my primary folder my DAW was picking up on one that wasn't registered! Was quite frustrating because it was like I hit a brick wall and had no idea why it wasn't working.

Once the vst and steam folder are successfully installed in sequence, go into the first disk and find the folder with the patch in it. It will want you to route it to where you set up your VST. It will patch the VST file. Open the VST in VSTHost (open VSTHost as Admin by right clicking > Run as Admin) and get your code. Run it through the keygen, register and then close the program completely when you get your confirmation code. Re-open it to make sure it's registered successfully and then you can open it in other DAWs no problem.

 

what is patching bro

 

In this case I would say patching Omnisphere is kinda like changing the security. That means you have to patch it to make it work. Or otherwise Omnisphere won't accept it. I got this issue one time in the past aswell, but I found out it was not patched yet. Open the keygen. Click on patch. Search for the location where you have Omnisphere installed. You should find an Omnisphere dll file right there. Use that to patch. Omnisphere should now accept the response code after it have been patched succesfully. Make sure your daw is closed too before you start patching it.

 

Last edited: Sep 9, 2017

my bad but what nick said

 

You have to Patch the Omnisphere.dll, if your DAW is Crashing, try it in another DAW! in my case it works with Reaper...

Ps: Next Time, Read the Readme, TXT or NFO-File!

 

Last edited: Sep 11, 2017

every 3 days there's here a new topic on how to authorize omnisphere...

Hey guys,you really have eyes to read infos ?

There are alreadyl tons of informations on how to do that on the web, I don't understand the need to create a new topic for that.

 

OK, so you've installed Omnisphere, and you wanna know how to patch it. But before you try to authorize O2, you must open the keygen first and patch it, otherwise it will not authorize no matter how hard you try.
Nonetheless, I'ma tell you how to patch it... it's ok it was difficult for me at first too. Sad part is, when I reached out and asked how to do it, I was ridiculed so I taught myself.
So open the keygen.
Where you see "patch" button, click it, and it will ask you to locate a file. So assuming you installed omnisphere plugin folder in the default location, you must locate your vst plugins folder. I don't know the exact path for this folder but I'm sure you can find it with a little trial and error. Just keep looking until you find the "VST2" folder. It should be under "C:/programfiles/VST2" if I remember correctly. Or it could be in C:/CommonFiles. Not sure though. Just look for Omnisphere.dll in those folders.
When you click the "patch" button in the keygen, it will bring up a file browser, locate that Omnisphere.dll file in the browser, and double click on it. If the keygen says "Successfully patched!" then it is now safe to authorize omnisphere, so don't close the keygen just yet until you have done all the challenge/response code shit.

If you have any other issues, feel free to ask.

 

DAAAAAMN i had the issue where i put in the response code close fl open it and it asked me for the response code again and again all i did was ensure that the dll file that i was patching was the same dll file in the plugin shortcut that fl studio was using.