• Any tips for reducing CPU?
• Can the full version of Ozone 3.0 and Ozone 2.0 be accessed at the same time from a host application?
• What's the current Ozone version?
• It sounds like Ozone adds noise to my audio?
• Does Ozone offset the audio by some delay time?
• Can I install and run Ozone 3.0 if I have Ozone 2.0 installed?
• I've installed Ozone but I don't see it in my host application's plug-in list.
• What operating systems are supported?
• What CPU models are supported?
• What host applications are supported?
• What restrictions are present in demo mode?
• Will I be able to uninstall the plug-in?

2) Ozone's digital processing modules consume more CPU than their analog counterparts. If you're using Ozone's Digital EQ, Digital Crossover, or Room-modeled Reverb, you should adjust your buffer sizes for optimal performance. See "Buffer Sizes" in Ozone's documentation for details.

3) Try changing the buffer size and/or latency setting in your host application. When buffers are too high (latencies are too large), meters will update very slowly and performance may suffer. As buffers become very small (latencies are very low), the Digital EQ, Digital Crossover, and Room-modeled Reverb will consume more CPU.

4) You can disable meters in their option screens. Right click on any meter to bring up the options screen for that meter.

5) Using less crossover bands can save significant CPU. Try using 1 or 2 band dynamics, for example, instead of all 4 bands. See Using Multiband Modules for instructions on how to change the number of crossover bands.

6) You can force Ozone to process stereo files in mono, requiring roughly half the CPU for half the channels. This is useful while previewing to save CPU in some cases. You can enable this option in the General Options tab.

(applies to Windows versions only) No, Ozone 3.0 will appear to host apps as the "Ozone" plug-in. This is so all of your presets from earlier versions of Ozone will appear and can be migrated to the Ozone 3.0 preset system, and so that all of your projects that used earlier versions of Ozone will automatically load Ozone 3.0 if it is installed.

Ozone 3.0 does not overwrite earlier versions of Ozone, though. By default, Ozone 1.0 was stored in

C:\Program Files\iZotope\OzoneDX

and Ozone 2.0 was stored in

C:\Program Files\iZotope\OzoneDX2

Therefore, if you have ever want to go back to an earlier version of Ozone, you can simply run your Ozone 1.0 or 2.0 installer again, or go to the Windows Start-Run command and run this command:

regsvr32 "C:\Program Files\iZotope\OzoneDX\iZOzone.dll"
or
regsvr32 "C:\Program Files\iZotope\OzoneDX2\iZOzone.dll"

Ozone 1.0 or 2.0 will then appear as the "Ozone" plug-in to host apps, all of the presets that you had created for Ozone 1.0 or 2.0 will still be available, and all of your projects will load Ozone 1.0 or 2.0 as before.

Some presets use "upward expansion" which brings up the level of low signals. In many cases this a powerful tool for adding fullness to a mix. If the source recording has some noise in it, however, the noise will be increased as well with these presets.

To remove noise, simply adjust the ratio of the expanders in the multiband dynamics to be 1.0 or greater as shown below:

You should also make sure that you have not inadvertently enabled Ozone's dithering. You can disable Ozone's dithering by selecting the "Loudness Maximizer" screen and setting the "Dither type" to "None".

Ozone's digital processing modules will insert a delay into Ozone's output. Many host applications will compensate for this delay if you enable "Delay compensation" in Ozone's General Options tab. Ozone's Dynamics and Loudness Maximizer also use lookahead algorithms to intelligently predict and interpolate the waveform. This lookahead time is on the order of a few milliseconds.

You can also compensate for the delay manually after applying Spectron to your audio. To see the total delay Ozone is currently inserting into its output, see the General Options tab.

When mastering with Ozone (or any effect for that matter) a good practice is to leave at least a couple seconds of silence at the end of the file for either offsets from lookahead algorithms or tails/ringing from reverb and filter effects.