Quote:

Quote:

Ozone in general uses remarkably little CPU% but as it does so many functions, I'm guessing that single effects in general probably use less. This would need to be tested, though.



Plugins are more about RAM than CPU, so if you've got enough RAM to support whatever you are running, should be good to go.


--Mac


I'm sure that statement is true about most plugins, but I don't think it applies well to Ozone. Ozone can be a stand-alone program as well as a plug-in. The Ozone FAQ support section offers many tips about reducing CPU usage, and says nothing at all about RAM. Watching the CPU usage has been very important in my many years of using Ozone, and each of their modules relies heavily on processing power. Here are a few samples from the Ozone FAQ:

For better live playback, there are some adjustments you can make lower Ozone's CPU and latency needs. These settings have been designed for greater fidelity in mastering and mixdowns. Because you may want to hear these high-performance effects during playback, we've made it possible to adjust the latency and CPU they use. If you enter Ozone's Options screen, and examine the "EQ/Reverb/XOver" panel, you will be able to change the buffer sizes used by each of these effects. In general, lowering these buffer sizes will lower the latency required for the effect, but cause a slight jump in CPU needs. Raising buffer sizes will do just the opposite: raise latency needs, but lower CPU cost. It's worth exploring these ranges to find values that work best on your system.
_____________________
If you don't need stereo output when previewing, try enabling "Process as Mono" in your plug-in Options screen, under the General tab. This can cut CPU usage by up to 50%.
­­­­­­­­­­­­­­­­­­­­­­­­­­­­­_____________________
Using fewer bands for multiband effects can save significant CPU. To change the number of bands, right-click (or control-click, on OS X) on the band's mini-spectrum.
_____________________
Problem:
My host application drops out, or experiences "Sync," "Time-out," or "Time-inactive" errors when using my plug-in.

Solution:
When you change a plug-in's settings or presets, this can sometimes change the amount of CPU resources or latency needed by the plug-in. If a host's I/O buffers and latency are set too low, these sudden changes in the plug-in can sometimes cause "sync" problems, playback dropouts, and other timing issues. To help with this problem please try increasing your host's latency allowances and I/O buffer sizes.

BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus 192 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.