Whenever I put in the response code the authorization page just comes back up over and over again. I ran the keygen and FL in admin mode. Also, I can't authorize my dll file even though it isn't write protected, so that may be the reason. Any help?

 

I had the same problem when I switched from OSX to WIN few days ago ..
I moved the dll's to the Desktop, patched them, then back into the VST folder ..

It crashed like 50 times when i pasted the responce code into Omnisphere, but after the 347589x try it finally worked.

I can feel ur pain, I had the same problem .. and someone on reddit said, just to try it over and over again ..

Try authorizing with another DAW, I use Ableton, but it crashed always there .. so I used Studio One to register to plugin.

 

Sometimes the authorization doesn't crash, it just pulls up the same thing again. I'll try to patch it like that, thanks

EDIT: Tried to patch like you said and it still didn't work. Any other suggestions?

 

Have we had that kind of problem yet?

 

What's that supposed to mean

 

Sometimes it takes more than one attempt to get the keygen run correctly.
You always need to run keygen and the app as admin and make sure the dll you are about to patch is writable.
When your DLL is inside the c:\program files\ structure, Windows protects it and it is a good idea to set the rights to "all" for the current user.
Also you should remember that the plugin and the "native" app of Omnisphere use two DLL that are sitting in two different locations.

I found it to be the easiest way to patch the "native" DLL and copy it to the VST directory overwritig the DLL that's already there.
Also you should patch the x64 DLL on a x64 system, not the x32 one.

 

It means, we discuss problems with patching Omnisphere on a weekly basis.
Really A LOT and I mean A LOT of threads are here about that issue.
Search and you will find.

The good thing is: Eyveryone managed to patch it at the end

 

best way is to run the standalone as admin and paste the code in, usually works first time, make sure no DAW is open just the standalone.exe, it can take a few attempts if you try and auth it within your DAW.

 

Alright, so my dll that I'm trying to patch is in C:\programdata\spectrasonics\plugins\64 bit. It is writable and I have been running the keygen on admin, yet is always says failed to patch. I have no folder named structure in program files. Are you saying that I should copy the dll to vstplugins folder and patch it from there?

 

There's no option to open my standalone as admin. It just says open when I right click

 

are you on pc or mac, because mac is different

 

PC