I keep having a very bad experience with WL12 and iZotope Ozone.
In particular system freezes for short bursts (mouse and graphics freeze momentarly, repeatedly) when I have Maximizer, Imager and Vintage Limiter, loaded in the Master Section.
Even if I deactivate these plugins the situation still remains. I thought that this could be a problem with the plugins themselves, but in Cubase they seem to work fine.
Does anybody else have this problem?
My Setup:
CPU Intel Core i9 13900KF 1700/3.0 GHz
SSD Samsung 980 Pro NVMe M.2 1TB
RAM Desktop Corsair 64GB Kit 6000MHz
M/B Asus Z790 PRIME-P
VGA Gigabyte GeForce RTX 4070 WINDFORCE
O/S Windows 10 (Fully Patched).
Indeed. This is in part why I use Ozone Advanced so I can load just the modules I need instead of the entire CPU hog full Ozone 12.
In general, Ozone 12 and the individual modules are a major CPU and GPU hog so if your computer is older and/or not super fast it’s not surprising to see issues in this area.
Years ago I tried a Mac Mini for my home setup (before the M1 version) and it was Ozone that made it unusable for me.
I guess it would be good to post some screenshots of the WaveLab CPU meter and computer Activity Monitor when using these plugins in WaveLab vs. Cubase.
It’s also worth noting that while the Ozone plugins do seem to work OK in WaveLab, iZotope doesn’t list WaveLab as a supported host so maybe there are some things that could be better optimized for WaveLab if they ever choose to support WaveLab.
I see … So Ozone is not compatible with one of the leading professional wave editors of the market!
There used to be a time when it worked “fine” (meaning it crashed if you switched sample rate, but at least it didn’t cause the computer to hick-up).
Thanks all… Sorry for the trouble! I should have seen this notice myself. The iZotope support is crap BTW. They always say that its something you did wrong - not their software. Then they fix “your wrong” on their next update.
