Here is a serious incompatibility between Ozone 5 Adv and Wavelab 8 discovered by me few month ago. I wrote to Izotope support about it. Here is my mail correspondence with them on the subject. (start on the bottom and newest on top). 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. I also send pictures of spectrum and Ozone preset I’m talking about in correspondence.
Thanks in advance
Vic
Everything is explained below. Please go throughout it:
“”"
Hello Wiktor,
After further investigation, it appears that this issue may occur with other plug-ins as well in this audio host application.
Can 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. In that case, you may want to contact Steinberg Support for further information.
Please let me know if you have any further questions.
Sincerely,
TJ
iZotope, Inc.
http://www.izotope.com/
On Mon, 10 Mar 2014, support@izotope.com wrote:
Hello Wiktor,
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.
Please let me know if you have any further questions in the mean-time.
Sincerely,
TJiZotope, Inc.
http://www.izotope.com/On Sun, 09 Mar 2014, biliana@zoho.com wrote:
Hello TJ
Any news on this issues? What developers say? Current status makes Ozone unusable within Wavelab. It complicates work a lot.
Sincerely,
Wiktor Korczakowski
http://koras-studio.wix.com/mastering
-----Original Message-----
From: iZotope Support
Sent: Wednesday, January 08, 2014 8:06 PM
To: biliana@zoho.com
Subject: Re: Ozone 5 advanced bugHello Wiktor,
Thanks for your patience.
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.
I will forward this to our developers for their consideration and further investigation. That being said, I am unaware of any updates or patches to Ozone 5 planned in the immediate future.
Please let me know if you have any further questions.
Sincerely,
TJiZotope, Inc.
http://www.izotope.com/On Wed, 04 Dec 2013, biliana@zoho.com wrote:
Thanks - I’ll look forward for it
Wiktor Korczakowski
http://koras-studio.wix.com/mastering
-----Original Message-----
From: iZotope Support
Sent: Tuesday, December 03, 2013 11:57 PM
To: biliana@zoho.com
Subject: Re: Ozone 5 advanced bugHello Wiktor,
Thanks for this information.
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.
I will let you know the results of my continued investigation as soon as possible.
Please let me know if you have any further questions in the mean-time.
Sincerely,
TJiZotope, Inc.
http://www.izotope.com/On Wed, 27 Nov 2013, biliana@zoho.com wrote:
Hello TJ
I’m sending you 6 screenshots taken by schirmfoto utility by Abelsoft:
unprocessed 24bit - original wave
VST2 rec w WL - original wave passed thru Ozone 5 advanced VST2, preset “pno” also included in attachments (same I sent previously) recorded internally in Wavelab 8,0,3 (build 698) 64 bit – what is playing is recorded into separate file VST2 rend w WL - original wave passed thru Ozone 5 advanced VST2, preset “pno” rendered in Wavelab
VST3 rec w WL - original wave passed thru Ozone 5 advanced VST3, preset “pno”, recorded internally in Wavelab
VST3 rend w WL - original wave passed thru Ozone 5 advanced VST3, preset “pno”, rendered in Wavelab
VST2 rend w RX3 - original wave passed thru Ozone 5 advanced VST3,
preset “pno”, rendered in RX3 advancedNo other plugins were used.
Please compare the images presenting spectrograms of all this waves. There is no major difference between VST2 and VST3 versions of Ozone but between “rendered” and “recorded” – there is.
In case of “rendered” versions in Wavelab you can observe much more melted image in 100-700 Hz area and even lack of “dry”, fundamental notes like in 24-26 sec close to 300 Hz compared to “recorded” in Wavelab.(which is our WY-H-IWYG goal)
I’ve also processed original wave by Ozone w/ ”pno” preset on the RX3 platform. This produces sonically (and visually) similar wave to Wavelab “recorded” versions and seems to be OK.
This brings us to the point that there must be some sort of incompatibility between Ozone5 and Wavelab 8. This should not happen in “pro” software.
It is not happening with other plugins used with Wavelab as far as I experienced.
Possibly my experiments will help you do something about it. Ozone is a great software and is worthy of it.
What do you think???
Sincerely
Wiktor Korczakowski
http://koras-studio.wix.com/mastering
-----Original Message-----
From: iZotope Support
Sent: Wednesday, November 27, 2013 12:12 AM
To: biliana@zoho.com
Subject: Re: Ozone 5 advanced bugHello,
My investigation included a few other hosts including Reaper and FL Studio, with the provided settings running during playback. I was unable to notice similar results to the ones you have provided.
Please let me know if the VST 2 version also behaves in this manner on your side. Also, are you running any other plug-ins in the signal path in this scenario?
Please let me know if you have any further questions.
Sincerely,
TJiZotope, Inc.
http://www.izotope.com/On Mon, 25 Nov 2013, biliana@zoho.com wrote:
Hello
What DAW did you use to render file? May the reason lays in DAW soft - in my case Wavelab - the latest rev.
I’ll play with VST2 and let you know about results.
There is also an issue with Inside soft. used in Wavelab. It doesn’t scale up correctly by the right low corner handle dragging, which seems to be placed there for this particular reason.Sincerely,
Wiktor Korczakowski
http://koras-studio.wix.com/mastering
-----Original Message-----
From: iZotope Support
Sent: Tuesday, November 26, 2013 1:09 AM
To: biliana@zoho.com
Subject: Re: Ozone 5 advanced bugHello Wiktor,
In my testing here, the preset appears to sound much different from the resulting files, both the intended and not intended version.
Can you try using the VST 2 version to see if this also recreates this issue? To my knowledge there is not much benefit to the VST 3 version of Ozone 5 over the VST 2 version, and if the VST 3 version has an issue, you may want to try using the VST 2 version to see if this is consistent across both versions, or only in one over the other.
Please let me know if you have any further questions or if the problem persists.
Sincerely,
TJiZotope, Inc.
http://www.izotope.com/On Thu, 21 Nov 2013, biliana@zoho.com wrote:
Hello
I sent you already preset which I observed this phenomenon on. I include it in this mail also.
I’ll check its behavior with VST2 latter on.
Anyhow it should not matter which version of plug I’m using as a end-user, especially - VST3 is newer technology hence suppose to be more advanced. Isn’t it?My best
Wiktor Korczakowski
http://koras-studio.wix.com/mastering
-----Original Message-----
From: iZotope Support
Sent: Thursday, November 21, 2013 1:02 AM
To: biliana@zoho.com
Subject: Re: Ozone 5 advanced bugHello Wiktor,
Thanks for this information!
I can indeed see a slight difference in release/decay characteristics in the examples that you provided. What cutoff settings do you have set for the Reverb module? Would you be willing to provide an Ozone 5 preset for the settings you are using? I can then attempt to recreate this on my side here.
Once we are able to recreate this on our side here, we can then better understand what may be occurring in this type of scenario.
Also, you mentioned that this occurs in VST 3 versions. Does this also occur in the VST 2 version? If not, you may want to simply use the VST 2 version instead.
Please let me know if you have any further questions.
Sincerely,
TJiZotope, Inc.
http://www.izotope.com/On Thu, 14 Nov 2013, biliana@zoho.com wrote:
recorded in line internally in wavelab 16bit
-----Original Message-----
From: iZotope Support
Sent: Thursday, November 14, 2013 12:22 AM
To: biliana@zoho.com
Subject: Re: Ozone 5 advanced bugHello,
Thank you for contacting us.
Would you be willing to provide a demonstration audio file that shows this issue consistently on your setup? Also, if you are able to record the audio playback of what it should sound like in an additional audio file, this can help me better understand the issue that you are experiencing.
Does this issue occur consistently on your setup?
Does this occur with the VST 2 or VST 3 versions in Wavelab?
Can you please also provide a preset of the settings that you are using to process this example?
Please let me know if you have any further questions.
Sincerely,
TJiZotope, Inc.
http://www.izotope.com/On Thu, 07 Nov 2013, biliana@zoho.com wrote:
IP: 89.64.250.76
It’s about Ozone 5 advanced (rev. 5,04).
It should be a WY-H-IWIG program, I believe, but when I render (Wavelab 8,03 64bit) particular setup containing REV module (Theater algorithm) I get different sound from what I hear using it as In-line plugin. It looks as a problem lays somewhere around Cutoff filters.
Is it a bug?
Sincerely
Wiktor Korczakowski
http://koras-studio.wix.com/mastering
Ozone 5 advanced bug
Q) *What do you need help with?
A) Product crash or bugQ) *iZotope product:
A) Ozone 5 AdvancedQ) *Operating System:
A) Windows 7 64-bitQ) *Host Application:
A) Steinberg WavelabQ) Host Version Number:
A) 8,03Q) *Plug-in format:
A) VSTQ) *Processor type:
A) PC IntelWiktor Korczakowski
http://koras-studio.wix.com/mastering
[/color]
pix.zip (1.65 MB)