I actually wanted to keep version 2 in case the installation or version 3 didn't work properly; otherwise, I'd have to painstakingly reinstall version 2, which would take hours. When searching for version 3 in the plugin search, only version 2 is displayed, not version 3; you first have to delete version 3 from the VST3 directory.

 

Spectrasonics Bob Moog Tribute Library v2.0c [STEAM] -|||- STEAM | 9TH FEB 2023 | 2.28 GB

Simply copy and overwrite the two files:

Settings Library
Soundsources

Have you Started Omnisphere click rescan waited, then quit it & restart Omnisphere.
Be sure you're doing all this from the Stand Alone app.

The "Moog Tribute Library" is under the "Benefit Libraries" see picture.

 

Last edited: Nov 5, 2025 at 2:56 PM

I would better to not use anything from tracker but only sound libraryes

 

it's going to be revision after revision after revision. Like Serum. Except that where Serum lets you know full well (maybe in front of your entire Youtube audience during a much hyped "unboxing video"), GUI melting while you watch it; That plugin is going to have tons of sneaky stuff that looks like regular old problems with a new synth. But it's probably the same reason as the GUI melt.

 

Even that Bob Moog Tribute library shared version, when installed for use with legit OS2; would cause all sorts of dumb problems.

If you install shared Trilian on a Mac with legit Omnisphere2, it actually detects your Trilian is [k]d and it refuses to work either. Opens a page on their website and tries to rat you out. Or at least appear that way.

They have had years to make a new version and what percentage of that time was spent on this stuff? It's probably way higher than they would like to admit.

 

Hey everyone, in Ableton you can have both Omnisphere 2 & 3 installed at the same time.
The only downside is, more drive space will be needed as you will need both the v2 & v3 libraries.

Do the following -
Use Omnisphere 2 as vst2 & Omnisphere 3 as vst3 or vice versa.
Have your Omnisphere 2 & 3 libraries on the same drive, but name the v2 library Omnisphere2
& the v3 library Omnisphere3. Now say you want to use Omnisphere 3, just move the Omnisphere3 folder
to your STEAM folder & rename it Omnisphere. & if you want to use Omnisphere 2, rename the Omnishphere folder back to
Omnisphere3 & move it out of your STEAM folder, then move the Omnisphere2 folder to your STEAM folder & rename it Omnisphere.

There will be no licensing issues as the AUDIODAT16 is for v2
& AUDIODAT19 is for v3. & using vst2 & vst3 means both versions
can reside on your system.

The reason I done this, is I have 652 3rd party preset banks tagged with Omnitag, & they make the v3 browser very slow, I can't even refresh the browser without v3 crashing. All these 3rd party presets are a tagged mess in v3 as Omnitag is not compatible with v3.. Using v2 & v3 is working great. Omnisphere 3 is now fast when changing categories
& is no longer crashing when doing a browser refresh. So now I can still use all my nicely tagged 3rd party presets in v2,
as well as the new factory library & features in v3. I thought this may be useful for anyone who has had the same experience as me.

NOTE -
You will not be able to use 2 & 3 at the same time in a DAW session. It's either one or the other in each project.
& make sure you don't load Omnisphere 2 with the v3 library in your STEAM folder.
Or load Omnisphere 3 with the v2 library in your STEAM folder. Doing this will mess up your v2 or v3 libraries.
Also don't keep the v2 or v3 libraries in the STEAM folder at the same time. even though the one not in use will be renamed,
It safe practice to only have the one you are currently using in the STEAM folder.

Here are some images that show Omnisphere 2 & 3 can be used on the same system -

 

Last edited: Nov 5, 2025 at 4:41 PM

That's why if you have tons on 3rd party presets in Omnisphere 2 it's best to use Omnitag
& use the presets via the patch browser. This is why I'm using Omnisphere 2 as well,
because if you copy your 3rd party presets across to the v3 library, it makes omnisphere 3 very slow.
This is because Spectrasonics have made changes to their browser & tagging system in v3.
It's best not to use 3rd party presets that have been imported & indexed in v2 in v3.

e.g. Initially I copied all my 3rd party presets across from v2 to v3 & v3 was freezing when changing categories.
It was also crashing when doing a browser refresh, & the 3rd party presets were a mess in the patch browser.
Spectrasonics say "Backward compatibility" which is true in the sense v2 presets will work in v3.
But because the browser & tagging system has changed in v3, it cause issues if you copy all your 3rd party presets across..
I'm not even sure if reinstalling v2 preset banks into Omnisphere 3 will fix this, because of the browser & tagging system changes.
Devs may have to redo their preset banks to v3 standards.

If I didn't have 652 3rd party preset banks, I would just ditch v2 & use v3.
But I'm keeping v2 as well so I can still use my 3rd party presets with no issues

 

Last edited: Nov 5, 2025 at 5:39 PM

Exactly! I I was reluctant to use more space by having the v2 & v3 libraries on my drive.
But I felt it was the only workaround in my case. I think Omnipshere 3 is great, minus the browser & tagging system changes.
I don't think these were needed. They've just made things more complicated for their users now..