Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: VST 2.x/3.x Adapter 0.11.10 with iZotope Ozone 9 and 11 doesn't work properly (Read 883 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

VST 2.x/3.x Adapter 0.11.10 with iZotope Ozone 9 and 11 doesn't work properly

I have a Windows7 2SP x64 based system, running both Foobar2000 v2.0 x64 and v1.6.16 and using the audio suite Ozone from iZotope. I'm using Ozone 9 Advanced x64 and recently discovered that some of the features I hadn't used weren't working properly. I contacted iZotope who had told me Ozone 9 would work on my Windows7 PC prior to purchase, despite official support only being for Windows 10 and later 11. At the time I couldn't test it on my Windows because the VST2.x/3.x x64 adapter didn't exist yet. I was already running Ozone 8 x32 as it worked with the previous VST host plugin and it worked fine.  Ozone 8 x64 works correctly in the new VST 2.x/3.x adapter. Meanwhile Ozone 9 and the recently released Ozone 11, both x64 plugins are not working correctly. I have tried both the VST2 and VST3 versions but it makes no difference.

I believe this is due to changes they made rather than due to Foobar2000 or the VST2.x/3.x adapter. iZotope's reply is it may be due to that their software is tested on Windows 10 and 11, and there's no testing or official support for Windows7 OS, or alternatively that it is somehow due to the way the Foobar2000 with the VST2.x/3.x adapter is structured. They have never claimed that it would work in Foobar2000. They also say they are not aware of the problems I have experienced by any other users in DAWs used in music production settings. Here goes a description of the problem.

Ozone is structured in a series of module plug-ins, where each module processes audio in a specific way.  In the latest version there are 18 modules. Ozone contains a mother of a module, the Mothership, which hosts all the processing modules in a customizable signal chain.  It is this module I place inside of the VST2.x/3.x adapter. This module also contains some, but not all, of the functions that are problematic within the VST2.x/3.x adapter. The Mothership contains among other functionality global toggle switches for bypassing all the modular processing, turning off stereo and instead summing to mono, as well channel swapping, essentially a polarity switch.

A signal chain inside the Mothership can consist of very few or all the modules. The order can be swapped by drag and drop. Each module has a button for turning it on or off without removing it from the chain, and a Solo button where all the other modules are excluded from the signal chain, and you just hear the processing from that module. All modules also contain a Delta switch which then plays back only the changes the module incurs on the sound.

I'm going to exemplify the problem when running Ozone 9 or 11 in the VST 2.x/3.x Adapter in Foobar2000. The actions are identical in v2.0 or v1.6.16 x64.

In Ozone 8 when toggling Sum to mono on in the Mothership it immediately sums to mono. To get stereo back toggle Mono off. Sound turns stereo instantaneously.

Here is a description of how Sum to mono now works.

I first have to turn on Sum to mono, it is immediately shown as mono in the Imager module which displays the sound visually in a vectorscope. However, no change is registered in the sound, out of the speakers/headphones.

To effectuate the change in sound in addition to selecting Sum to mono I have to either turn on or turn off one of the modules in the signal chain (any module). Only then is Sum to mono effectuated in the sound. I can also effectuate it by toggling the bypass button on and off.

This is an additional step compared to previously. It's the same if I want to turn stereo back on. Hence changes are not immediate, and sometimes it complicates the working procedure.

Channel swapping also requires these additional toggles in both Ozone 9 and 11.
 
The same goes for the Delta function. In order to effectuate, I have to select Delta, nothing in the audio changes, then switch on or off ANY module in the signal chain in order to effectuate the Delta function in the sound. Then when I want to switch it off and return to the sound, the same procedure applies.

Alternatively I discovered that I can turn these functions on by clicking on the bypass button twice: Click Delta; Click Bypass TWICE to turn Delta on. To turn it off, toggle Bypass once. Toggle Bypass again to turn Delta on again, but one time is now enough.

Ozone also offers analog iir filters or digital fir filters in the Equalizer module. Swapping between these isn’t effectuated unless  one of the modules is turned off and then on again.

Finally, the functionality of bypassing all processing in other modules, the ”S” for Solo button where you only listen to the processing from one single module, a button available in each module, doesn’t work at all. It has no effect whatsoever.