Ozone is a powerful mastering suite, but its modules, meters, and low-latency settings can use more processing resources than a typical plug-in. Some Ozone 12 users have reported high CPU readings or audio dropouts with the IRC 5 Maximizer in real-time sessions. The reports vary by computer, DAW, buffer, and settings; they do not mean every Ozone setup has a problem.

If your session stutters when Ozone is active, first identify whether the issue is the mastering chain or the mix. MixDiagnose analyzes an exported audio file and reports mix characteristics to investigate. It does not run inside your DAW, measure your computer's CPU load, or replace Ozone or a mastering engineer.

What users and iZotope report

In a public Native Instruments Community thread, an Ozone 12 user reported 20–35% CPU use with IRC 5 enabled on an M4 Max, including while playback was stopped, and described dropouts during playback in some buffer settings. Other users report different results, so treat this as one real-world configuration report, not a universal benchmark.

In a separate KVR Audio discussion, an Ozone 12 user reported 22% CPU use at idle with IRC 5, Soft Clip, and Transient Emphasis enabled in a Balanced Master Assistant preset. The thread also includes users who did not see the same increase on their systems.

iZotope's own support guidance says Ozone performs more calculations than a typical plug-in. It recommends bypassing unused modules, adjusting the host buffer/latency, disabling meters if needed, and using fewer crossover bands to reduce CPU demand.

Sources: Native Instruments Community: IRC 5 real-time CPU report · KVR Audio: Ozone 12 CPU and upgrade discussion · iZotope Support: Reducing Ozone latency and CPU usage

Troubleshoot the session first

  1. Save a copy of the project, then bypass Ozone and compare playback stability.
  2. If the issue changes, re-enable only the Ozone modules you actually need. Bypass unused modules rather than leaving a full chain active.
  3. Try a different host buffer or latency setting. Very small buffers can increase CPU use for the Digital EQ and Digital Crossover; very large buffers may make meters update slowly.
  4. Test IRC 5 separately from other Maximizer options, and switch off optional processing such as Transient Emphasis or Soft Clip to isolate what matters in your session.
  5. Use fewer crossover bands and disable meters you do not need, following the host- and version-specific guidance from iZotope.
  6. For final rendering, compare the result and export settings separately from real-time playback performance. A session that struggles at a low-latency buffer may behave differently during an offline bounce.

These are diagnostic steps, not a claim that one setting is best for every mix. Preserve the sound you want and verify the final render by listening.

CPU troubleshooting is different from mix diagnosis

Ozone MixDiagnose
Main job Processes audio with mastering modules in a DAW Analyzes an exported mix and reports potential technical issues
Runs in real time in a DAW? Yes No
Changes the audio? Yes No
Can diagnose your computer's CPU use? Your DAW's performance meters and system tools are the right place to check No

MixDiagnose can help you inspect frequency balance, dynamics, stereo, loudness, and other properties of an exported mix. It cannot tell you which Ozone module is consuming CPU or whether an assistant's mastering choices are artistically right.

Check the mix before the mastering pass

If you are troubleshooting a heavy mastering chain, simplify it and monitor your DAW's performance meters. If the session is stable but the mix still needs work, analyze an export and use the report as another set of technical clues before deciding what to change.

Analyze your mix free

Sources

Related reading