Omnisphere 2 slow interface

[exmatproton]

I've always had lag with any envelope that used curve1 or 2? I think it was called. Any envelope with an adjustable curve causes huge frame drops, on both my PCs which have powerful gaming graphics cards.

Spectrasonics actually spent a long time working with me trying to fix it and the support was really good. Still broken tho ☺

+1. Most of the elements work pretty good. But those darn envelope curves are aweful to work with...

[pluton]

bought a legit copy, everything works fine now

[noiseboyuk]

Thread revival, as this keeps bugging me. The problem seems better every time there's an update, but it's pretty quick to go back to being sluggish.

I have a case open now with support to try and nail this down. I've been doing more thorough tests in standalone, in an empty Cubase project and a busy Cubase project, keeping Windows Resource Manager open (Win10). It's clear that the single core CPU use maxes out when Omni is freezing. I get this when I move the scroll bars - typically the first time it's a hang of a few seconds for the GUI to respond. It seems logical that the more the background CPU activity, the worse the hang.

Thus far I haven't replicated a really bad scenario - at its worst it can hang for up to 15s and every click in the browser produces a long delay. But I hope the videos I'm sending them are a start.

On my M2 MacBook, Omni is like lightning, super responsive. My PC is 5 years old, a 7820X with 64gb of RAM. I suspect memory management is quite different between Macs and PCs, but given than Omni (and Stylus incidentally) is noticeably worse than other plugins, I wonder if there's something specific to Spectrasonics UIs in Windows - should the call on CPU usage really be this high to move a scroll bar?

I'm also wondering if updating my CPU / MOBO and swapping for DDR5 RAM will improve things - I have my eye on a Ryzen 9 7900 whose single core score is about 75% higher than the 7820X. More headroom would hopefully ease the maxed out CPU situation.

[enCiphered]

I'm pretty sure the problem is Cubase, not Windows, and certainly not your computer. Cubase has the worst CPU management among all major DAWs and causes the most drop-outs, GUI lags.. you name it.
Try to download a trial of Bitwig or Reaper and you will see that Omnisphere will behave a lot better.

[noiseboyuk]

I'm pretty sure the problem is Cubase, not Windows, and certainly not your computer. Cubase has the worst CPU management among all major DAWs and causes the most drop-outs, GUI lags.. you name it.
Try to download a trial of Bitwig or Reaper and you will see that Omnisphere will behave a lot better.

IMO it's the usual thing of a bunch of factors. Cubase is about the least efficient DAW out there I agree, but ultimately other plugins don't have this issue in Cubase, and Cubase / Omni is behaving fine on the Mac.

[T-CM11]

I'm pretty sure the problem is Cubase blablabla

Unless it's not.
Did you read the whole topic? About the same behaviour in other DAWs and even standalone?

other plugins don't have this issue in Cubase

+ Omnisphere works fine in Cubase for a lot of people.

If Cubase is the (sole) culprit, everybody would have this same issue - which is not the case.

[enCiphered]

I'm pretty sure the problem is Cubase blablabla

Unless it's not.
Did you read the whole topic? About the same behaviour in other DAWs and even standalone?

other plugins don't have this issue in Cubase

+ Omnisphere works fine in Cubase for a lot of people.

If Cubase is the (sole) culprit, everybody would have this same issue - which is not the case.

Please forgive me for not having read the whole topic from the beginning, what a fool I am. What the heck was I thinking when I expressed my opinion to help someone..

[legendCNCD]

I had no problems with my old i7-4960X + SataSSD and there are no problems with new R7950X + nvme with the GUI. It is now much faster in doing any loading though

[MegaPixel]

Thread revival, as this keeps bugging me. The problem seems better every time there's an update, but it's pretty quick to go back to being sluggish.

I have a case open now with support to try and nail this down. I've been doing more thorough tests in standalone, in an empty Cubase project and a busy Cubase project, keeping Windows Resource Manager open (Win10). It's clear that the single core CPU use maxes out when Omni is freezing. I get this when I move the scroll bars - typically the first time it's a hang of a few seconds for the GUI to respond. It seems logical that the more the background CPU activity, the worse the hang.

Thus far I haven't replicated a really bad scenario - at its worst it can hang for up to 15s and every click in the browser produces a long delay. But I hope the videos I'm sending them are a start.

On my M2 MacBook, Omni is like lightning, super responsive. My PC is 5 years old, a 7820X with 64gb of RAM. I suspect memory management is quite different between Macs and PCs, but given than Omni (and Stylus incidentally) is noticeably worse than other plugins, I wonder if there's something specific to Spectrasonics UIs in Windows - should the call on CPU usage really be this high to move a scroll bar?

I'm also wondering if updating my CPU / MOBO and swapping for DDR5 RAM will improve things - I have my eye on a Ryzen 9 7900 whose single core score is about 75% higher than the 7820X. More headroom would hopefully ease the maxed out CPU situation.

Omni is complete random, it works well for some and like shait for others (mac and pc), my guess is it's some common software/driver combination....

I'm one of the unlucky ones... It runs like shait for me on win10 in Bitwig, StudioOne, FL and standalone.

They have known about this issue for many years.

Since going through tech support, twice, a long time back, I've re-installed win10 Pro with newer and newer versions as time passed, I even have more ram, a new nvme drive, a new gfx card and new audio interface now, and it still runs like complete shait. I've not used omni in a single project.

i9 9900K OC'd to 4.85ghz on all cores, 64gb ram, scarlet 8i6, rtx 4090

My advice would be to sell it, it ain't that good anyway.


PS. I just remembered I did manage to speed it up a bit., I shaved off an hour or 2 from the delay in dragging the preset slider by having an older version of visual studio attach itself to it's process to debug it. It crashed, but after the crash it ran a bit better (for that install)...

Support have no idea why, I have all the issues you have, they confirmed the issue remoteing into my machine, and various YT videos I made, and in the end after many hours of the usual, nothing was done. There was mention that I could install a debug version or put it in debug mode but they never did that, that would have been very helpful, I could have gone through the logs at least, but nope...

[Echoes in the Attic]

I used to have problems sometimes but currently am totally fine. It's quite snappy. Last few years have been fine. No idea why it's so different on different systems. I'm on Windows with Bitwig and smooth sailing for now.

[noiseboyuk]

Thanks all - if anyone has the inclination, I'd be interested to know if a CPU core maxes out when doing UI stuff. If you DON'T get freezes but DO get a CPU core maxed out - or if you DO get freezes and DON'T get a CPU core maxed out, then that would be very useful data.

MegaPixel - never selling for any money, even though this issue is frustrating. It absolutely IS that good

[noiseboyuk]

I took a look on the MacBook Air, and there's no obvious CPU spiking at all when I click anything in the UI.

It sounds / looks like there is something in the setup / config of some peoples' Windows rigs that is causing a huge drain on CPU, most likely related to the UI. It's clearly not consistent, it's not meant to happen and I genuinely think Spectrasonics have never managed to track down why it afflicts some systems and not others. It would be very good if they could.

[legendCNCD]

I launched Live 10 and dragged Omni to track, in two seconds it was open. There was a spike on 4 cores of 16 when loading, then nothing when operating UI. Win11Pro. Both Live and Omni are latest updates. GTX1070 with Studio Drivers.

[noiseboyuk]

I launched Live 10 and dragged Omni to track, in two seconds it was open. There was a spike on 4 cores of 16 when loading, then nothing when operating UI. Win11Pro. Both Live and Omni are latest updates. GTX1070 with Studio Drivers.

Thanks for the info.

Support had me turn off real time protection in the virus settings - has anyone here with issues played with this? That does seem to have made the scroll bars snappier, even though they still cause CPU spikes. Stuff like changing part in the browser from the drop down menu still causes huge CPU overs. I'll need to road test it for a few days to get a better idea if this is a real difference or not.

[legendCNCD]

I launched Live 10 and dragged Omni to track, in two seconds it was open. There was a spike on 4 cores of 16 when loading, then nothing when operating UI. Win11Pro. Both Live and Omni are latest updates. GTX1070 with Studio Drivers.

Thanks for the info.

Support had me turn off real time protection in the virus settings - has anyone here with issues played with this? That does seem to have made the scroll bars snappier, even though they still cause CPU spikes. Stuff like changing part in the browser from the drop down menu still causes huge CPU overs. I'll need to road test it for a few days to get a better idea if this is a real difference or not.

That sounds really, really strange but, its software - it will have bugs. (I'm in QA )
I dont have defender installed, so my system is already different from most of peoples, also WUpdate is in "win7" mode of having no anything done automatically. Hm, neither did my Win7 box have defender, or any other antivirus running.