OMNISPHERE 2.5 Slow GUI after update?

[martinjuenke]

Every software has issues.....
Not all of us have these issues, I am pretty sure the majority don't.
I think between here and gearslutz I have read about four of them, one already solved.
rsp

To be fair, he's only been here for three years. That's clearly not long enough to have worked out that new releases, updates etc can have bugs that slipped through the beta process

Thanks for calling me a young guy. You made my day!

[Tarekith]

I've been having a lot of issues with this myself since the update, both in standalone mode and when hosted in a DAW. The whole GUI lags seconds behind a mouse click, no matter what my audio buffer is set to or any of the other performance suggestions on the Spectrasonics page. Running a 2017 MBP using Mojave.

[Echoes in the Attic]

I’ve found that it takes much longer than it used to just to load patches using the oscillators and no samples. They had a while where loading samples patches took an absurdly long time but they fixed that. However I do find that it takes a couple seconds to change oscillator patches, which used to be pretty much instant. I don’t recall when this started, maybe 2.5. Don’t recall if patch changing in v2 before 2.5 was as fast as v1. It is annoying though still usable.

[noiseboyuk]

Pretty much instant here on Win 10, but it prompted me to check and I'm still on 2.5.0d - are you folks on the latesst 2.5.1d?

[Tarekith]

Yep, latest version of Omni and Mojave here. I have a support email in to Spectrasonics, hopefully they have some ideas.

[Armadillo]

I'm on PC, Cubase 9.5 and it's also sluggish for me. Particularly changing categories in the browser takes 5+ sec. which is rather infuriating. Hopefully 2.6 will solve this issue.

[noiseboyuk]

I just checked on my MacBookPro on 10.13.6 and this is on the latest 2.5.1d. The switching here on waveform patches is a little slower, but nothing drastic, between 0.5 and 1s. Category switching is instant however, whereas that's slower on Windows.

[Tarekith]

I just heard back from Spectrasonics support (only a couple hours after sending a request too btw), and they said it's a known issue with certain graphics cards on Mojave. They sent me a test build of Omni to try, and it instantly fixed everything. Very responsive GUI now, huge improvement.

Definitely contact Spectrasonics if you're having this issue.

[noiseboyuk]

Good news, thanks for posting Tarekith.

[Armadillo]

Yeah, thanks for the heads up Tarekith. I've now contacted them.

[Echoes in the Attic]

I just heard back from Spectrasonics support (only a couple hours after sending a request too btw), and they said it's a known issue with certain graphics cards on Mojave. They sent me a test build of Omni to try, and it instantly fixed everything. Very responsive GUI now, huge improvement.

Definitely contact Spectrasonics if you're having this issue.

So this is only related to Mojave? I guess I won't hope for improved speed of preset switching on windows 10 then. Like I said it's not terrible, maybe 2 seconds per switch, but still could be better.

[noiseboyuk]

Maybe it is a graphics card thing in Windows as well, Echoes - no delay here on Win 10 for those synth-only patches.

[Echoes in the Attic]

Maybe it is a graphics card thing in Windows as well, Echoes - no delay here on Win 10 for those synth-only patches.

My issue definitely was nowhere near as was described above though, which makes me think it’s a separate issue. I have delays with the interface in general. But we’ll see when it’s updated I guess.

[Biome_Digital]

Slow on PC too. Any news on this?

[Brittlestem]

People used to complain about the now-abandoned RMX and then Omni when it first came out - the official response? "It's got more tabs/pages than most other VST...tough."
But I've gone from a cheesegrater Mac to a i9-9900k PC and Omnisphere/RMX are still like molasses to open and browse.