I will need to spend some additional time with this information, and I will try and obtain this specific version of Wavelab for further testing. That being said, I am unaware of any updates or patches to Ozone 5 planned in the immediate future. I will forward this to our developers for their consideration and further investigation. I was able to recreate this issue on our side here, and noted that the recorded playback and the rendered file with the same settings may provide different results within Wavelab 8.0.3. Please let me know if you have any further questions in the mean-time.Īny news on this issues? What developers say? Current status makes Ozone unusable within Wavelab. While I have not heard of any updates on this, I will check with our developers directly and get back to you as soon as possible with further information. IZotope develops award-winning audio software and plug-ins for mixing, mastering, restoration, and more. iZotope iZotope | Plugins for Audio Restoration, Mixing, Mastering and More Please let me know if you have any further questions. In that case, you may want to contact Steinberg Support for further information. Please go throughout it:Īfter further investigation, it appears that this issue may occur with other plug-ins as well in this audio host application.Ĭan you try using an alternate manufacturer’s reverb plug-in to see if this issue continues to occur? If it does on your side, then this may indicate a difference in playback and rendering by Wavelab directly. I also send pictures of spectrum and Ozone preset I’m talking about in correspondence.Įverything is explained below. Since there is Wavelab 8.5 coming out and they suggest that the reason for mis-compatibility may be on WL side - I’m pointing this out. Here is my mail correspondence with them on the subject. Here is a serious incompatibility between Ozone 5 Adv and Wavelab 8 discovered by me few month ago.

Izotope ozone 5 vst