Omnisphere 2 slow interface

[noiseboyuk]

Some hopeful news from Spectrasonics support. I've been helping them for a few weeks to try and track this down.

What was clear as I did some tests with Task Manager is that patch browsing, changing part, scrolling in the browser all max out the CPU on my system even on standalone, and that correlates with the perceived hang. The more activity there is in a project, the worse the effect of that is - if the CPU is already at 60%, then the CPU overs accordingly last longer, if its otherwise near rest then its relatively short.

We eliminated hard drive performance, anti-virus and database size.

Just received this:

Until now, we've never been able to reproduce these GUI performance issues on any of our Windows development systems, which has made it difficult to implement a fix in the software. After reviewing your videos again this week, we've been able to reproduce the Patch Browser GUI CPU issues on one of our development laptops. Thus, we should finally be able to make some headway on implementing GUI optimizations to resolve this issue.

That's great news. Still don't know why some systems are unaffected and some aren't, but they've tracked it down on an affected system and sound hopeful about a fix. Really happy to receive this update and feel the end might be in sight for all of us who have been frustrated for years over this.

[iPlogger]

Wow! Great to hear. I haven't had this issue myself but have kept my eyes and ears on the topic hoping to hear of a resolution. Glad they can duplicate the problem.

[legendCNCD]

This IS great news, even though I've never had the bug, but I know how awful it is to wait something to appear when it should work instantly. Especially while making music, you want to be quick with sound selection not to lose the inspiration!

[Ben H]

Same. Although I have never experienced this issue in my years of owning Omnisphere, I can understand how it has been a deep source of frustration for many users.

Glad there may finally be a solution in sight.

[syntonica]

Omni grabs a huge chunk of memory on instantiation. Itt may also grab more memory with some patches. The system may be compressing memory or sending it to virtual memory to adjust. This is the only time I've encountered any undue slowness. Otherwise, while not snappy, the GUI runs fine--once the initial call home is completed.

[noiseboyuk]

Omni grabs a huge chunk of memory on instantiation. Itt may also grab more memory with some patches. The system may be compressing memory or sending it to virtual memory to adjust. This is the only time I've encountered any undue slowness. Otherwise, while not snappy, the GUI runs fine--once the initial call home is completed.

It's been clear for years that this issue doesn't affect all systems, so what you experience isn't what others experience. We still don't know what it is that triggers it.

The good news is that Spectrasonics have a system that experiences the same thing, so for those of us affected, the end is indeed in sight.

[syntonica]

Omni grabs a huge chunk of memory on instantiation. Itt may also grab more memory with some patches. The system may be compressing memory or sending it to virtual memory to adjust. This is the only time I've encountered any undue slowness. Otherwise, while not snappy, the GUI runs fine--once the initial call home is completed.

It's been clear for years that this issue doesn't affect all systems, so what you experience isn't what others experience. We still don't know what it is that triggers it.

The good news is that Spectrasonics have a system that experiences the same thing, so for those of us affected, the end is indeed in sight.

I was just adding my two bits as to where the issue may lie. A random issue that can happen to a random number of users is, as you have seen, very, very difficult to track down. Sometimes, I've just had to make an educated guess as to what an issue is while troubleshooting my own code. I should have said that I use Mac and I did not see in this thread if the issue is any computer or one or the other. I've only kept half an eye on this topic.

I'm happy to hear Spectrasonics may have a line on it, though. I'm hoping that if they have a positive result, they are able to modernize the GUI a bit more while in the process of making repairs and give it a little more off the snappy overall.

[noiseboyuk]

I was just adding my two bits as to where the issue may lie. A random issue that can happen to a random number of users is, as you have seen, very, very difficult to track down. Sometimes, I've just had to make an educated guess as to what an issue is while troubleshooting my own code. I should have said that I use Mac and I did not see in this thread if the issue is any computer or one or the other. I've only kept half an eye on this topic.

I'm happy to hear Spectrasonics may have a line on it, though. I'm hoping that if they have a positive result, they are able to modernize the GUI a bit more while in the process of making repairs and give it a little more off the snappy overall.

Basically - our work here is done. There's honestly nothing useful we can add at this point unless they specifically ask for something, the message was clear - "we've repro'd the issue, and we're on it". (It's a Windows-only glitch).

The GUI definitely won't get updated as part of this.

[DizzlerMusic]

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 ☺

i have had the exact same issue for years now. Its still not fixed. How can they not fix such a simple bug. When you download Omnisphere 2.4 the lags are not there, it got introduced shortly after. I would love to use omnisphere again, but waiting 2sec when dragging any envelope point makes it just pointless and a pain in the a** to work with.
Im also wondering if this exists on Mac, because i think this is non-existent on macs, simply because spectrasonics seem to use macs as their primary machines and if it would have occured there, they would have fixed it asap.

[zvenx]

It is hard to fix what they can't reproduce... I have had omnisphere from day 1 on mac and pc and that has never ever once happened to me, and this is over three pcs and two macs over the years.
I am even willing to bet it doesn't happen to the majority of their customers especially those "A-listers" living in California who could have easily taken in their laptop for spectrasonics to witness it first hand or have spectrasonics come to them.

According to Guy's report until recently it has never happened to any of the computers at Spectrasonics either.


rsp

[DizzlerMusic]

It is hard to fix what they can't reproduce... I have had omnisphere from day 1 on mac and pc and that has never ever once happened to me, and this is over three pcs and two macs over the years.
I am even willing to bet it doesn't happen to the majority of their customers especially those "A-listers" living in California who could have easily take in their laptop for spectrasonics to witness it first hand.

According to Guy's report until recently it has never happened to any of the computers at Spectrasonics either.


rsp

thats true, its hard to fix if not reproducable. But I had 2 laptops and 1 pc. The issues happen on all machines. Im probably gonna install omnisphere on my moms laptop aswell, just to make sure im not the unluckiest person on earth then. .Im probably gonna email them again in a few days, maybe i can help them again fixing this. I want this once and for all fixed, i emailed them 2018 about this the first time (yes actually 5 years ago), and its time...But im not sure what will be there first : The bug fix or Omnisphere 3

[TS-12]

As far as I know from my circle of musician friends, none of the legit license owners of Omnisphere experience this issue.
So it might be something to do with that audio##.dat licensing file

[DizzlerMusic]

As far as I know from my circle of musician friends, none of the legit license owners of Omnisphere experience this issue.
So it might be something to do with that audio##.dat licensing file

Has nothing to with that. I have a legit license and i exchanged over 20 emails with their support (i helped them fix some other bugs aswell), and im pretty sure if they knew this existed only to non legit owners, they would have just stopped the email exchange altogether.

Whenever i download 2.4.2c from my account, which is the last version before they redesigned their UI (knobs and stuff), all the Lag issues are completly gone. So it has to do with that specific update, not my license file and also not my gpu or antivirus.

[noiseboyuk]

I've never experienced what you have Dizzler, but so many Windows users don't experience my slow UI issue. So indeed - these things can be mysterious and incredibly hard to track down.

[DizzlerMusic]

I've never experienced what you have Dizzler, but so many Windows users don't experience my slow UI issue. So indeed - these things can be mysterious and incredibly hard to track down.

What exact UI issues do you experience? Slow Browser? I think thats the most common one from what ive read online and i have that aswell. And im obviously not talking about the actual loading process, which can take some time of course, but actual scrolling in the browser often lags/freezes the whole UI and DAW for several seconds,also after a preset is loaded it lags badly. Newest Omnisphere version : just preset scrolling in the browser cuts my fps in half,loading presets the same. Using 2.4.2c : 60fps, snappy as hell, just fun to use.

Could you maybe test if you have the Mseg editing lags aswell (that i have?). Its easy to test: Just go to the mod env and change all points to linear(just use 3-4points), then take 1 point and drag it around from left to right, up and down. It should feel snappy as its intended, the points are at all times where my cursor is. Now when i change all points to either curve1 or 2, and try the same, it lags behind alot, it freezes the whole UI and drops FPS for me down to 5. Even the zoom scrollwheel is laggy then.

It would be also interesting for the issues that you have experienced, if you could just download 2.4.2c from your spectrasonics account(legacy download area) and check if your issues are gone. If thats the case, then its pretty much the UI redesign they did in 2.5 thats causing all those UI lags for (some) people.