Tried putting the plugin on my ssd, didn't made one single difference, don't know about the library though

 

Next try will be putting the whole library on the SSD. but considereing that it runs very fast in cubase off the slow HDD I don't think it will make any difference in S1 3.2

 

I'd say save the trouble, because I have the library on SSD and it's slow.

 

Spectrasonics probably want me to use that old ass Cubase 4 32bit again haha

 

My Omni2.1 in MAC loads in 6 sec. 64bit Ableton Live...

 

New Update 2.2.0e, still the same problem. When loading a patch in Studio one 3 it comsumes a lot of cpu and slows itself down.

 

It takes about 8 seconds for it to fire up on Win8 in FL Studio. The nag for me still is the latency until I initialize a macro, then all is spanking marvelous. I was over at Spectrasonics site for the update but forgot to ask about this. I am going there now.

 

With 2.2 update boot time is still the same at around 5 sec for me in S1 3.2, but navigating the browser is now pretty much fluid

 

64bit or 32bit ?

 

Real 64 bit (NOT previously mentioned Jbridge)

 

Try a different ASIO driver. ASIO4ALL has issues with Omnisphere. I had the same issue and switched to the FLstudio ASIO driver and it loads presets instantly. Hope this helps!

 

After 2.2.0e update loading time is shorter and browsing is easier than the previous version (previous was a memory hog)
Reaper - loading time:
- first opening < 5 sec
- every next opening < 2 sec (this is logical because it exists in RAM)

 

Browser and loading times in version 2.2.0e are much much faster. This is an amazing improvement. Try it yourself.

 

Now this one is interesting. I use my EMU drivers but woould be interesting to use it with other drivers and see the result

 

The Problem is solved!!!

Thanks you complete

 

https://audiosex.pro/threads/omnisphere-software-2-2-0g-update.24323/