OMNISPHERE 2.5 Slow GUI after update?
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 11519 posts since 16 Aug, 2006
When you guys say slow GUI, what specifically are you experiencing? The GUI itself runs fine here, but if I have it open, the Cubase GUI slows to a crawl with very slow frame rates on the meters for example.
-
- KVRAF
- 1588 posts since 24 Feb, 2004
Opening the GUI is soooooo slow. Browsing the sounds, sound match, editing tags, all drag, it's so sluggish, when all you want to do is get on with writing the music.
Worst is adding/deleting sounds using the "Projects", there's a 6 second freeze every fecking time you dare to use it; when your project has like 10 instances and you have to edit the sounds/change them it gets very, very old, very quickly.
Don't get me wrong, my frustration is because I love Spectrasonics stuff but I find myself reaching for other VST where I can get the editing done quickly and get back to writing.
Worst is adding/deleting sounds using the "Projects", there's a 6 second freeze every fecking time you dare to use it; when your project has like 10 instances and you have to edit the sounds/change them it gets very, very old, very quickly.
Don't get me wrong, my frustration is because I love Spectrasonics stuff but I find myself reaching for other VST where I can get the editing done quickly and get back to writing.
"What embecile composed this list :/"
- KVRAF
- 1801 posts since 23 Sep, 2004 from Kocmoc
5 seconds to open Omni on top of Live 10.1 x64 running on Windows 7 SP1 x64.
No delay for opening the plug after closing it, no problem navigating browsing selecting in the GUI.
No delay for opening the plug after closing it, no problem navigating browsing selecting in the GUI.
Soft Knees - Live 12, Diva, Omnisphere, Slate Digital VSX, TDR, Kush Audio, U-He, PA, Valhalla, Fuse, Pulsar, NI, OekSound etc. on Win11Pro R7950X & RME AiO Pro
https://www.youtube.com/@softknees/videos Music & Demoscene
https://www.youtube.com/@softknees/videos Music & Demoscene
-
- KVRian
- 521 posts since 19 Jun, 2016
i had no problems when this topic started but then started having them.
loading and editing was a real pain, mainly editing...
Trying to solve it, while in stand alone, i noticed changing the driver buffer size (strangely enough turning is lower made it better).
Still was hyper slow in cubase.
meanwhile it got much better again so i'm not sure...
my 2 cents...
1 - maybe it could have some deeper issues with not being VST3 if you have cubase 10
2 - maybe updating graphic driver issues made it somewhat better too because that's preety much what i've changed meanwhile
i'll test the suggested bridge tip
loading and editing was a real pain, mainly editing...
Trying to solve it, while in stand alone, i noticed changing the driver buffer size (strangely enough turning is lower made it better).
Still was hyper slow in cubase.
meanwhile it got much better again so i'm not sure...
my 2 cents...
1 - maybe it could have some deeper issues with not being VST3 if you have cubase 10
2 - maybe updating graphic driver issues made it somewhat better too because that's preety much what i've changed meanwhile
i'll test the suggested bridge tip
-
- KVRer
- 5 posts since 30 Sep, 2004
For those that are finding Omnisphere slow on Windows, are you using it alongside iLok protected plugins? If you start your DAW with no iLok plugins in the project and just add Omnisphere on a track is it responsive?
For me it’s fine as long as I don’t have any iLok plugins running, as soon as I do then Omnisphere becomes slow and stays that way even if I remove the iLok plugins from the project.
If I run Omnisphere as a bridged plugin in Jbridge then it is unaffected.
If I run Omnisphere sandboxed in Bitwig then it is unaffected.
The issue for me seems to be solely caused by Omnisphere being in process with an iLok plugin. I suspect some sort of DLL related issue but no real idea how to further diagnose it.
For me it’s fine as long as I don’t have any iLok plugins running, as soon as I do then Omnisphere becomes slow and stays that way even if I remove the iLok plugins from the project.
If I run Omnisphere as a bridged plugin in Jbridge then it is unaffected.
If I run Omnisphere sandboxed in Bitwig then it is unaffected.
The issue for me seems to be solely caused by Omnisphere being in process with an iLok plugin. I suspect some sort of DLL related issue but no real idea how to further diagnose it.
- KVRian
- 1367 posts since 21 Dec, 2013 from USA
Weird. I'll test tomorrow.
-
- KVRAF
- 5450 posts since 25 Jan, 2007
I just tried this, but cannot detect any difference between iLok being plugged in or removed, and a Cubase session with an iLok plugin activated or not. So likely to be system-specific in some way. I'd send your full system specs with reproducible steps to Spectrasonics support.joefrost01 wrote: ↑Wed Oct 02, 2019 2:07 am For those that are finding Omnisphere slow on Windows, are you using it alongside iLok protected plugins? If you start your DAW with no iLok plugins in the project and just add Omnisphere on a track is it responsive?
For me it’s fine as long as I don’t have any iLok plugins running, as soon as I do then Omnisphere becomes slow and stays that way even if I remove the iLok plugins from the project.
If I run Omnisphere as a bridged plugin in Jbridge then it is unaffected.
If I run Omnisphere sandboxed in Bitwig then it is unaffected.
The issue for me seems to be solely caused by Omnisphere being in process with an iLok plugin. I suspect some sort of DLL related issue but no real idea how to further diagnose it.
http://www.guyrowland.co.uk
http://www.sound-on-screen.com
W10, i7 7820X, 64gb RAM, RME Babyface, 1050ti, PT 2023 Ultimate, Cubase Pro 13
Macbook Air M2 OSX 10.15
http://www.sound-on-screen.com
W10, i7 7820X, 64gb RAM, RME Babyface, 1050ti, PT 2023 Ultimate, Cubase Pro 13
Macbook Air M2 OSX 10.15
-
- KVRian
- 791 posts since 24 Apr, 2008 from USA
I posted this in the other Omnisphere thread, here’s a copy of the post:
So, did a clean reinstall of Omnisphere.
- Uninstalled omnisphere and steam folder.
- Installed Omnisphere 2.0 version and original STEAM fIles.
At this point omnisphere browser was working very fast. Selecting patch categories and patches was virtually instant.
- Updated Patches, library and omnisphere to latest versions and browser started behaving much slower. Selecting patch categories and patches takes about a second to 2 seconds to switch.
- Installed 3rd party libraries (That Worship Sound, PluginGuru, PlugHugger and many others) , Trilian and Keyscape and now Omnisphere browser is very slow again. Selecting patch categories and patches takes about 5 seconds
So, did a clean reinstall of Omnisphere.
- Uninstalled omnisphere and steam folder.
- Installed Omnisphere 2.0 version and original STEAM fIles.
At this point omnisphere browser was working very fast. Selecting patch categories and patches was virtually instant.
- Updated Patches, library and omnisphere to latest versions and browser started behaving much slower. Selecting patch categories and patches takes about a second to 2 seconds to switch.
- Installed 3rd party libraries (That Worship Sound, PluginGuru, PlugHugger and many others) , Trilian and Keyscape and now Omnisphere browser is very slow again. Selecting patch categories and patches takes about 5 seconds
Macbook M1 Max 32GB Ram Cubase 12
- KVRian
- 1372 posts since 16 Jan, 2004
Are you using Ableton Live? I have had times when Omnisphere is running fine, and then other times when it's not, and presets take excessively long to load. Interestingly, when things get like this, it seems other synths get slow too, not quite as much, but still enough to say something is wrong. Closing Live and restarting my machine seems to reset things enough to bring things back to normal. Also, it seems like the bad state might be linked to running some Max4Live devices. There may be some correlation, but not sure. And even can be after running some M4L stuff, and then starting a new Live file/project, so not necessarily that the Live current project contains M4L devices. Just that M4L devices were loaded at some point... If that makes sense...
-
- KVRAF
- 5450 posts since 25 Jan, 2007
Thanks for the heads up - massively improved here.
http://www.guyrowland.co.uk
http://www.sound-on-screen.com
W10, i7 7820X, 64gb RAM, RME Babyface, 1050ti, PT 2023 Ultimate, Cubase Pro 13
Macbook Air M2 OSX 10.15
http://www.sound-on-screen.com
W10, i7 7820X, 64gb RAM, RME Babyface, 1050ti, PT 2023 Ultimate, Cubase Pro 13
Macbook Air M2 OSX 10.15
-
Echoes in the Attic Echoes in the Attic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=180417
- KVRAF
- 11054 posts since 12 May, 2008
Oh wow they are all VST3 now too. They mentioned in the release notes that this was important for midi 2.0 stuff that they are currently working on.
No mention of mpe for current version.
No mention of mpe for current version.