i’ve been mastering using Wavelab 10 for a few months and all has been solid. Today I find that any time I load one of the izotope ozone package plug ins Wavelab quits. What is the procedure for clearing prefs for Wavelab? Or any other time greatly appreciated. I just updated to the latest 10.04 but that did not solve the problem
It would be good to specify which operating system you use, and make sure you’re using the latest WaveLab 10.0.40 update that came out just today.
In addition, it would be good to specify which version of Ozone you are using, and make sure it’s up to date.
Lastly, it would be good to say where you are inserting Ozone. The master section? Clip FX? Montage Output FX?
On MacOS Mojave and the latest Ozone 9 Advanced, I am not having any troubles with the handful of Ozone module plugin I use. I never load the full version because it’s a CPU hog.
I can’t speak for all but it seems that Ozone 8 was problematic in WaveLab, and Ozone 9 is better. That is my current experience.
Also, iZotope doesn’t seem to support WaveLab 10 officially for Ozone 9, and I can’t find if and what they supported for Ozone 8 because it’s old:
Supported Hosts for Ozone 9:
Logic Pro X, Ableton Live 9–10, Pro Tools 12.8-2019, FL Studio 20, Cubase 9–10, Nuendo 10, Wavelab 9, Sound Forge Pro 13, Sound Forge Mac 3, Studio One 4, REAPER 5, Reason 10, Audition CC 2019, Premiere Pro CC 2019, MASCHINE 2, Komplete Kontrol, Bitwig Studio 3, Final Cut Pro X.
After extensive trials in new montages or applying to different files via the master section I have established that the Ozone plugs can be applied to the master section, but never to the initial problematic file. I now see that file is 32 bit float, and when you select the plug in it has 64F written next to it. I wonder if that is causing it? Another observation, if I copy a plug in strip from one clip to another, I can do that even if there’s an ozone plug used in the strip. The crash mainly seems to happen when I try to load a single instance of an ozone plug in on a clip.
I now see that file is 32 bit float, and when you select the plug in it has 64F written next to it
File format is isolated from plugin sample format.
However, you may try the following option, to reduce the memory consumption of Ozone.
Be aware that Ozone is a very memory hungry plugin. Each time you load one Ozone plugin, it consumes more memory than the whole WaveLab application itself!
Dam, always interesting. PG, you are full of all kinds of information! I’m not having any problems - and I have no reason to load two versions of Ozone 9 into WL - but I will change this to 32bit float. Thanks!
I just noticed that, while all my plugins have been reset to 32 bit, the built in Silence plugin is set at 64 bit without an option to change it. Is this going to be a problem?
I opened the Plugins folder and scrolled to the bottom of the list. There I found Silence, and it is listed as 64 bit while all my other plugins are listed at 32 bit as I selected on June 4.