If anyone tests Ozone 11 with Cubase 12, please leave some feedback. Thanks much
1 Like
Hello,
Today (well, yesterday) has Chris Selim from Mixdown.online published a new video on this. I still haven’t watched it, though, but I will for sure.
I have been using Ozone 11 with Cubase 12 and it is much more stable. With Ozone 10 I had to minimize Cubase when running the Ozone Assistant or it would crash Cubase. With Ozone 11 I no longer need to minimize Cubase and it does not crash. It is interesting that Ozone 11 Assistant now gives a message that it will be using “high CPU” and stalls Cubase, but does not crash. Happy so far, love Izotope products and Cubase.
1 Like
hi,i have the problem with nectar 4.when i use the assistant cubase crash…never had this problem before…but ozone 11 runs well at the moment. (cubase12).everytime a problem with izotope plugins they dont run stable on cubase
What type of computer and OS are you guys testing on?
I just downloaded and installed Ozone 11 on Cubase 12, and gave it a quick spin (using Master Assistant on a track). FWIW, it worked flawlessly.
I just started using the trial version of Ozone 11 Advanced today, just the mothership plugin. So far it has hung on me twice. This is Cubase Pro 12.0.70 on Windows 10. System is Intel i7 5820k with 16 MB RAM, and a MOTU 828x interface (running on Thunderbolt 2).
The first time I’d let the mastering assistant run, and it picked rock as the genre, which seemed decidedly off to me, so I switched it to folk. At that point, both the rock and folk genres were highlighted in the target selection area, and Cubase was hung. It produced a freezedump file in the CrashDumps, which has subsequently been sent to Steinberg on restarting Cubase. The project at this point was just one audio track with a 64-bit/96 kHz mix file on it. Ozone was an insert in the stereo out bus. Unfortunately, I hadn’t saved the project before Cubase crashed, so I was starting again on the second attempt.
The second attempt had the same basic stuff mentioned for the first attempt, albeit saving at points along the way. 
However, I also added a reference track, not going to the stereo out, only to a cue mix. (This was my original master of the song I was trying to remaster from the mix with Ozone 11, just out of curiosity to see if I could easily improve upon it.) I again did the Master Assistant thing, and this time it did pick Folk, and I could play the track and go back and forth between the stereo out and the cue mix in Control Panel. Next, I wanted to try using a specific target file (a classic singer-songwriter track) from a WAV file on my hard disk. I went to the custom targets screen in Ozone 11, added that file to the references, and Ozone got to the point where it says “Searching for enhancements” and “Briefly using high CPU. Prepare for volume increase” and froze, again generationg a freezdump file in Crashdumps (I’ll also send that to Steinberg when I restart Cubase.
Looking at the DMP file in WinDbg Preview suggests the plugin gets stuck in the same place both times (ntdll!NtWaitForSingleObject+0x14), with Exception Code 80000003 (Break instruction exception). There stack entry below that location is KERNELBASE!WaitForSingleObjectEx+0x8e, with 17 Cubase addresses below that, then the top Ozone-specific address is Ozone_11!GetPluginFactory+0x9a77. I think it is likely a user interface issue in Ozone as there are a bunch of stack entries that start with iZOzone11Core!PluginCoreInterfaceVersion starting 2 stack entries below that one.
1 Like
Hi,
Bought ozone 11 standard it runs but the dropout in the Master Assistant is very strange. It gives me a feeling like something is not running well. My PC running I9 with 64 GB.
Strange.