Yes I can confirm this when I launch Cubase while it opens the window says it from 2008.

 

Okay so here is an update, I reverted back a snapshot of the virtual machine to a state where only Cubase is installed and I'm reinstalling Omnisphere right now strange thing happens tho look at the Screenshot bellow this is what I'm looking for, but Omnisphere is only half way through the install so it isn't installed yet but as soon as it does I'm going to launch Omnisphere without crack or update installed if that's good, then I'm going to make a snapshot install the update make a snapshot and then crack it just so I can revert back to previous state to see where it fails.

Screenshot: https://postimg.cc/LnLB07V5

 

for clone's benifit the MROS and Microsoft Wavetable are not vst's there the mros is eqiverlent to macosx internal midi routing(a precorser to rewire) and the Microsoft Wavetable is windows own internal general midi synth.

default vsts with cubase whould be lm4, lm9 and neon are ones i can remember.
i dont rember that cs40 but looked it up and its also a vst of the time.

 

have you been installing the plugins with cubase open.
and then testing them without closing cubase and restarting it

after making yor snapshoot id try running the air keygen on the base install so that it is usable.

 

Last edited: Jul 30, 2024

You had to reboot with nearly every .dll plugin you installed back then. But I think there is too much going on still. I knew the GM was not really applicable, and the other some stock thing or whatever. That's why I mentioned to check with a simple 3rd party plugin. If you load both channels the same way and you get sound from the easy simple instrument plugin, you know it is Omnisphere. If not, it is within Cubase settings.

If Omnisphere is not installed correctly, you could chase your tail with it because you can't even assume the plugin is working normally.

 

No, I firstly install everything and then open Cubase after everything is installed and cracked.

 

Actually there WAS a VST32 5.2 release, it was a beta that was never finished. Cant remember if it was Zone or AiR that put it out, Radium was about gone by that point.. I wouldn't use it, it was a Steinberg beta heh, and it shouldn't have anything to do with a plugin not working or not considering everyone else that owned it was running 5.1.

 

So Omnisphere is installing right now, when it's done I can check if it works in a different program, what program should I test it in ?

 

maybe try savi host (VST2, including keyboard)

https://www.hermannseib.com/english/savihost.htm

 

the update that i was refering to not working was Cubase v5.12 AIR-UPDATE with cubase VST32 5.1R1

 

Cubase again first, then if still no sound...

You could do it with REAPER. Make one channel in a project and add Omnisphere to that channel. It should do the same thing as it does in Cubase. If it works correctly, we know the plugin is installed correctly and working. All that is left are Cubase settings, versions, etc.

The whole thing from download to finished will probably be in about 10 minutes.

 

Last edited: Jul 30, 2024

UPDATE: Still no fix, I tested the plugin and it works. But in Cubase a weird thing happend after the install I had the option to select Omnisphere in the Output (look at the screenshot 1 bellow) as basically any other VSTi plugin, even after the update it still showed but as soon as I replaced the Omnisphere.dll file with the cracked one it dissapeard. Now I'm assuming it's the Omnisphere.dll file that is the problem.

Screenshot 1: https://postimg.cc/gallery/dk43MNz

There are two pictures in there one is of the activator and the second one is me showing you that Omnisphere is recognised by Cubase perfectly fine before I replaced the Omnisphere.dll file, but the thing is if I can't replace Omnisphere.dll file with the cracked version how am I gonna activate it ?

 

Thank you for the reply, please take a look at my update. I believe it's the activation when I copy and replace the new generated Omnisphere.dll from the crack it doesn't work but if I leave it as it is then it works without a problem except Omnisphere then asks for activation and the keygen can't generate the correct key probably because of the wrong Omnisphere.dll

 

Wait I'm confused right now is there another keygen for this ? I tried opening the keygen and just pasting the code with the original Omnisphere.dll file but it just won't activate see the screenshot bellow.

Screenshot: https://postimg.cc/Q9w9sQ3S

 

FINAL UPDATE: Thanks to User @audioplg he managed to figure out what the problem was, the whole time activation was the problem, we ended up installing v1.0 of Omnisphere and then using v1.1.4 TeamAir release we managed to finally fix the issue, everything works !

Once again huge THANK YOU to audioplg and everyone here who replied to the post.

 

Lol
Cubase 5.1 ?????

 

just for future people

the issue of with the midi ports of the vst no showing up was that as of version 1.2 of omnisphere they moved to vstsdk 2.4 with this move it caused the problem to appear on vesions of cubase upto sx 3.

Thanks Steinberg