iZotope UI feels laggy?

[drdriller]

I'm running Ozone and Neutron on a pretty old CPU and video card, in the worst performing DAW (currently) out there, and my displays play back absolutely fine.

on my old computer (i5 / 6440pts), the UI of Neutron advanced took nearly 500 ms to open, and then it was a mess with automation (a litteraly named "dirty flag" control triggered an event each time i automated another control..)

but what was really unusable du to cpu hog was the dynamic eq, finally i sold it and now use Melda DynamiqEq which work like a charms.

[Nimrod7]

2018 15" MBP, i9, 32GB RAM...
I mean.. should work fine.

I have the same MBP.
The UI of Izotope plugins is fine. The framerate is very high. I have it connected to an external monitor, which forces the dGPU to be used.

Have you tried to force the use of the discreet GPU instead of the integrated?
That utility can do it: https://gfx.io/

[EnochLight]

Always issues with Macs these days. I just don't get it - seems like testing on this platform should be fairly easy to achieve. It's not like there's 1000's of different hardware builds available like there are on PC's. So weird.

@drdriller: did you ever reach out to iZotope tech support and try to get your issue resolved? I mean, not like you can now since you sold it.

[layzer]

sounds like a keylogger to me, check for trojan virus, someone is recording your screen.

[Ploki]

sounds like a keylogger to me, check for trojan virus, someone is recording your screen.

highly doubt it.

The frame rate drop is especially noticable when i open Voxengo Span... oddly.

Other frequency analysers are fine.

I love it and would jump on the new music production suite2 ... but these gui lags worry me.
also the dirty flag - noticed it too lol.

[2NDMOUSE]

Anyone ever get to the bottom of this ?
I have hundreds of vsts, and none give me visual lag except Izotope plugins.
Iris 2 and Vocalsynth 2 are particularly bad. Even just clicking next preset has a 2 second delay, and it also slows down the DAW responsiveness as well.
I have a 2,8gh cpu , quad-core, with 32gb ram. This shouldn't be happening.

I don't have a dedicated graphics card, and I'm thinking it may be something to do with graphics drivers, openGL, direct draw....all that stuff that i've never had the time to investigate because I'm doing busy making music. Maybe I need to update my drivers, but every other plugin is 110% fine, so I dunno.......

[pixel85]

Anyone ever get to the bottom of this ?
I have hundreds of vsts, and none give me visual lag except Izotope plugins.
Iris 2 and Vocalsynth 2 are particularly bad. Even just clicking next preset has a 2 second delay, and it also slows down the DAW responsiveness as well.
I have a 2,8gh cpu , quad-core, with 32gb ram. This shouldn't be happening.

I don't have a dedicated graphics card, and I'm thinking it may be something to do with graphics drivers, openGL, direct draw....all that stuff that i've never had the time to investigate because I'm doing busy making music. Maybe I need to update my drivers, but every other plugin is 110% fine, so I dunno.......

It looks like they didn't find the way to optimalize their GUIs. It's a bit strange by looking how great DSP programmers they have.
Their GUIs eat resources no matter what. Of course the more powerful PC is the less is the impact but it's still noticeable. I have "low-medium" graphic card GTX1060 and I can still see that opened GUI of iZotope plugin have more impact than any other plugin.
Although it's not an issue on modern CPUs within normal usage/projects, while doing stress-test to see the limits of my PC, when DAWs performance meter reached 100%, operating any plugin was still fine but not iZotope. Especially Neutron 3 was making operations unbearable.
I doubt that drivers can change anything (except if the current one are very badly written).
Who knows, maybe $2k graphic card is required for smooth operation?

[DJ Warmonger]

Well, I noticed FPS drop in Izotope plugins, but only when combined with multiple plugins with real-time display. Maybe they all use a common thread or library for rendering. Hard to guess without peeking into source code, and for same reason impossible to fix.

[2NDMOUSE]

sounds like a keylogger to me, check for trojan virus, someone is recording your screen.

Absolute nonsense.

[street spirit]

Yup agree, they dont play with with older GPU and processors. You need something more modern in my experiences

[guerraldo]

The answer is slow, but I'm going to give it to you, after investigating the problem of Izotope Ozone 10.0.4 in FL Studio 21.1 I thought it was the DAW but it's not the case, the problem is a conflict in the programming of the main module em the opengl routines, this causes a crash in the driver mainly the AMD one causing it to enter a lag cascade throughout the system, it can be solved without having to restart or exit FL studio or windows, simply press shift+ctrl+ winkey+B, this will reset the graphic driver, also the Riva Tuner can cause other graphic problems set application detection level to none and turn off freesync and enhanced sync in the driver creating a profile for FL studio, don't open the asio driver menu in FL Studio since it will trigger the video Lag error, mainly in Behringer asio drivers and Focusrite, I wanted to post this earlier but the image line forum won't let me

[2NDMOUSE]

I've basically just abandoned izotope. The lag in Iris 2 was horrible to the point where it was unusable. I chalked it up to experience, but I was availing myself of every sale Izotope had and managed to get myself up to the full bundle where I had Neutron 3 advanced and Ozone 10 advanced, but then Izotope just decided to abandon Trash 2, Breaktweaker 2, and Iris 2 ( all of which I also own ). I had basically written those plugins off due to the lag issues, but I still had Ozone 10 to kinda offset my anger.
I used it in standalone mode to master. Then izotope had the nerve to end the standalone mode ( based on customer usage statistics.......( which most users probably turned off because we need our cpu to process music, not usage statistics ) , so all that was left was to use the ozone modules within the DAW..........that would be ok, except for the fact that they suffer from the same horrendous lag which dogged Iris 2 etc......so every module is unusable. Useless.

I now boycott izotope. I had bought everything ( RX10 as well ) but they've now lost me as a customer. Given their "race to the bottom" pricing strategy, it wouldn't surprise me if they went out of business. I don't care anymore. They'll never get another penny from me.

I bought Wavelab. I'll continue to master with something more professional now.

[guerraldo]

After a lot of research, changing video drivers, uninstalling stardock-type applications, changing things in the flstudio 21.1 profile in the amd driver, surprise, the problem is incompatibility with freesync, but it is not corrected just by turning it off in the AMD driver, you have to turn it off on the monitor, that's how the OZONE 10 worked with FL 21.1