> ## Content Index > Fetch the complete content index at: https://soundforgepro.com/llms.txt > Use this file to discover other available public pages before exploring further. # Ozone 12 Maximizer: IRC Modes, Controls and Best Settings - URL: https://soundforgepro.com/ozone-12-maximizer/ - Published: 2026-10-20T23:45:25.000Z - Updated: 2026-10-22T01:08:38.000Z - Description: The Ozone 12 Maximizer is Ozone's final limiter, in Standard ($219) and Advanced ($499). Pick IRC 4 for a few dB of limiting and IRC 5 for loud masters, set Output Level to -1.0 dB with True Peak on for streaming, and plan for IRC 5's CPU load. - Author: Erick Finn - Tags: Ozone, Mastering **The Ozone 12 Maximizer is the limiter at the end of Ozone's chain: Gain drives the mix into the ceiling you set with Output Level, and the IRC mode decides how that limiting sounds and how much CPU it costs. The full module is in Ozone 12 Standard ($219) and Advanced ($499), and the new IRC 5 mode is in both. Elements ($55) only offers a ±4 dB Maximizer slider inside Master Assistant.** My order of decisions is short. Pick the mode by material and machine: IRC Low Latency while you are still recording or on a weak computer, IRC 4 when the master needs only a few dB of limiting, and IRC 5 when you push for a loud master and your computer can play it back. Then set Output Level with True Peak on, at −1.0 dB for streaming or −2.0 dB if the master is louder than −14 LUFS. Last, measure the bounced file instead of trusting the plugin's estimate. This page stays with the Maximizer module; for the verdict on the whole suite, read the [Ozone 12 review](https://soundforgepro.com/ozone-12-review/). ## Where the Maximizer sits and what it does The Maximizer is a limiter, not a compressor: it holds peaks under a fixed ceiling instead of reshaping the whole dynamic range. If that difference is still fuzzy, the [compressor vs limiter guide](https://soundforgepro.com/compressor-vs-limiter/) sorts it out. [iZotope's Maximizer guide](https://docs.izotope.com/ozone12/en/maximizer.html) describes Gain as the control that pushes the signal into 0 dBFS, where limiting begins, and Output Level as the maximum level that leaves the module. Two older names changed. Gain replaces Threshold, so you now turn it up instead of turning a threshold down, and Output Level is the renamed Ceiling. The limiting idea itself is old: Intelligent Release Control first shipped in Ozone 3 in 2003, according to [iZotope's Inside Ozone 12 article](https://www.izotope.com/community/blog/inside-ozone-12). Soft Clip joined the Maximizer in Ozone 10, Upward Compress in Ozone 11 and IRC 5 in Ozone 12\. The [Ozone 12 vs Ozone 11 comparison](https://soundforgepro.com/ozone-12-vs-ozone-11/) covers everything else that moved between versions. ![Signal flow of the Ozone 12 Maximizer from Input and Gain through a group of Upward Compress, Soft Clip and Transient Emphasis that all act before the limiter, into the IRC limiter with Mode, Character and Stereo Independence, then Output Level with True Peak and Dither last, above a strip listing -1.0 dBTP for streaming, -2.0 dBTP for masters louder than -14 LUFS and -0.1 dB with True Peak off for Full Scale](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/maximizer-signal-order.webp) Everything that adds loudness happens before the IRC limiter; Output Level and True Peak set the final ceiling. Dither comes after all of it. Ozone's Dither lives in the main Ozone plugin and in the Maximizer component plugin, and [iZotope's dither guide](https://docs.izotope.com/ozone12/en/dither.html) says to put Ozone on the last insert slot, post-fader, when it dithers. Whether you need dither at all depends on the output bit depth, which the [bit depth and dither guide](https://soundforgepro.com/sound-forge-bit-depth-dither/) explains. ## Which Ozone 12 editions include the Maximizer The Maximizer module is in Standard and Advanced, and IRC 5 is already in Standard, according to the [edition comparison on iZotope's store](https://www.izotope.com/products/ozone-advanced?tab=compare&country=US). Prices are from the iZotope US store on October 21, 2026, where [Ozone 12 Standard lists at $219](https://www.izotope.com/products/ozone-standard) with no sale price shown. | Edition | US price | What you get of the Maximizer | | -------- | -------- | ----------------------------------------------------------------------------------------------------------------------------- | | Elements | $55 | Master Assistant's Maximizer slider only, ±4 dB of Gain; Module View shows an upgrade screen instead of editable modules | | Standard | $219 | The full Maximizer module inside the Ozone plugin, including IRC 5, Soft Clip, Upward Compress and Delta, plus Ozone's Dither | | Advanced | $499 | Everything in Standard, plus the Maximizer as a separate component plugin | For Maximizer work, the practical difference between the two paid editions is that separate component plugin; the upgrade from Standard to Advanced costs $279\. iZotope offers a free 10-day trial, and Ozone 12 installs as AAX, AU or VST3, 64-bit only, with no VST2\. The wider edition split, including the modules this page leaves out, is in [Ozone 12 Elements vs Standard vs Advanced](https://soundforgepro.com/ozone-12-elements-vs-standard-vs-advanced/), and the [Ozone 12 hub](https://soundforgepro.com/izotope-ozone/) collects prices, upgrades and free tools in one place. ## IRC modes: which one to pick The Maximizer offers six Intelligent Release Control modes. They differ in how they decide when and where to limit, and in how much CPU and latency they cost. Here is the short version from iZotope's guide, with my pick for each. | Mode | How it limits | Named styles | CPU and latency | When I would pick it | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------- | | IRC Low Latency | IRC 1's approach with less delay | None | Lowest latency and least CPU of all modes | Recording through the master bus, or a slow computer | | IRC 1 | Single-band; reacts fast to transients to avoid pumping and slowly to steady bass to avoid distortion | None | Not flagged as heavy in the guide | Gentle, general limiting | | IRC 2 | Like IRC 1, tuned to keep transients sharper under aggressive limiting | None | Not flagged as heavy in the guide | Drum-led material that loses its snap | | IRC 3 | The most aggressive single-band mode; a psychoacoustic model sets how fast it can limit before distortion becomes audible | Clipping, Crisp, Balanced, Pumping (legacy behavior from Ozone 5.01 and earlier) | Very CPU-intensive, high latency; may not run in real time above 48 kHz | Dense, loud material when IRC 5 is too heavy for your machine | | IRC 4 | Limits the frequency bands that contribute most to the peaks, using dozens of psychoacoustically spaced bands; leaves the spectrum alone when no limiting is needed | Classic, Modern, Transient | Very CPU-intensive, high latency | Moderate limiting of a few dB | | IRC 5 | Four frequency bands, each with its own attack and release, to cut pumping and the intermodulation distortion heavy lows cause in higher frequencies | None | The most CPU and the most latency of all modes | Loud masters, if your computer plays it back cleanly | IRC 5 is the headline change. In the same Inside Ozone 12 article, iZotope explains that IRC 1 to 4 were single-band designs, that IRC 4 added a spectral shaper, and that IRC 5 is the first truly multiband one. The guide adds that IRC 5 builds on IRC 3's psychoacoustic model, leaves the spectrum untouched when no limiting is needed, and can cause a subtle tonal shift because it favors the bands that contribute most to the peaks. The article also admits that IRC 5 brought "serious CPU and latency demands", to the point that the team considered dropping Transient Emphasis for it. One wording trap: the guide's overview still says the Maximizer "is not a multiband effect", which clashes with its own IRC 5 entry. Read it as "no user-set bands or crossovers". IRC 5 splits the signal internally, and you never choose the bands yourself. FabFilter's Pro-L 2, by contrast, limits the whole signal as one band; the iZotope vs FabFilter comparison sets the two limiters side by side. ![Ozone 12 IRC modes arranged along an arrow from lower to higher CPU load and latency: IRC Low Latency, then IRC 1 and IRC 2 as single-band modes, then IRC 3 and IRC 4 as very CPU-intensive, then IRC 5 with four bands and the most CPU and latency](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/irc-mode-tradeoffs.webp) Move right only when the material asks for it: each step costs more CPU and latency. ## Gain, Output Level, True Peak and Character Four controls do most of the work, and they are worth setting in a fixed order: mode, ceiling, then Gain. - **Gain** sets how hard the mix hits the limiter. The gain reduction meter and its readout show how much the limiter is taking off at any moment. - **Output Level** is the ceiling. With **True Peak** on, the limiter also accounts for the analog signal after D/A conversion, which can peak more than 3 dB above the digital samples; iZotope notes a small CPU cost for this. The [true peak explainer](https://soundforgepro.com/true-peak-explained/) covers why a sample-peak reading can miss the highest crest. - **Link** ties Gain and Output Level together: raise one and the other drops by the same amount. You hear what the limiter does without the louder-is-better bias. Treat it as an audition tool and switch it off before you set the final ceiling, or Output Level will drift away from your target. - **Character** sets attack and release on a continuous scale from Clipping (0.0) to Very Slow (10.0). The actual times depend on the mode, so the same number behaves differently in IRC 4 and IRC 5. ![Ozone 12 Maximizer module set to IRC 5, with the Delta button and two view icons at the top left, Learn Input Gain with a -14.0 LUFS target at the top right, a Gain knob at +6.0 dB with its link button, Output Level -0.10 with True Peak on, the Character slider at Transparent 5.00, a gain trace over the waveform, and Upward Compress, Soft Clip, Transient Emphasis and Stereo Independence controls along the bottom](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/maximizer-controls.webp) Mode, Gain and ceiling sit on the left, the pre-limiter tools along the bottom. The -0.10 ceiling shown is hotter than Spotify's -1 dB true-peak advice. **Learn Input Gain** listens to five seconds of your track and sets Gain so the output matches the Target LUFS value, then turns itself off. iZotope warns not to use it to meet loudness compliance standards. The [Master Assistant guide](https://docs.izotope.com/ozone12/en/master-assistant.html) says much the same about the Assistant: it sets Maximizer Gain from the analyzed section only, so the final integrated LUFS may differ, and it points to RX Loudness Control for precise compliance. Both are good starting points, and neither is a meter. Check the bounce with a [LUFS meter](https://soundforgepro.com/lufs-meter/). ## Upward Compress, Soft Clip and Transient Emphasis These three controls work before the IRC limiter. They change how much the limiter has to do, so treat them as part of the limiting decision rather than as extra effects. **Upward Compress** lifts quiet passages instead of pulling peaks down. iZotope builds it as level-matched parallel compression: the dB value is the most gain quiet parts can receive, and peaks at 0 dBFS stay at roughly the same level at any setting. In the Gain Trace view its boost shows as the trace rising from the bottom. I would use it when a master sounds loud in the choruses but thin in the verses, a level problem the limiter can only solve by squashing the loud parts harder. **Soft Clip** rounds off peaks before the limiter sees them. Its Amount is a wet/dry mix; at 100% the signal fully clips at 0 dBFS, and the processing runs at 4x oversampling to keep aliasing down. The Light, Moderate and Heavy modes start saturating at −3, −9 and −30 dBFS, so Heavy colors far more of the signal than Light. As a starting point, [Song Mix Master's Ozone 12 review](https://songmixmaster.com/ozone-12-review-mastering-with-stem-eq-bass-control-and-irc-5) suggests Soft Clip at 10 to 30 percent, fine-tuned by ear, with Character near the middle. **Transient Emphasis** shapes transients before limiting, and higher Amount values leave more pronounced transients after the limiter. It is the control to try when drums lose their front edge at the loudness you want. ## Stereo Independence, Delta and the meters **Stereo Independence** replaces the old Stereo Unlink control. It has two sliders, Transient and Sustain, linked and set to 0% by default. Raising them lets the limiter treat the channels more separately. With both at 100% the output can get louder, but the guide warns that the stereo image can narrow. I would leave them linked at 0% unless a wide mix is losing level to one hot channel, and check the result in mono if you move them. **Delta** plays only what the Maximizer changes: the peaks the limiter removes plus the boost from Upward Compress and Soft Clip. It ignores Gain and Output Level, so you hear the processing itself. When the Delta signal starts to sound like recognizable drums or vocals rather than faint clicks, I would back off Gain. The view selector switches between Spectrum Analyzer, Gain Trace and the Gain Reduction meter. Gain Trace is the useful one during setup: the trace from the top shows limiter attenuation, and the trace from the bottom shows the Upward Compress boost. The Gain Reduction meter shows the left and right channels with a readout of the current reduction. ## Starting settings by loudness target Pick the row that matches where the master is going. The platform numbers are Spotify's, from its [loudness normalization guidance](https://support.spotify.com/us/artists/article/loudness-normalization/): it plays tracks at −14 LUFS integrated, suggests targeting that level, and asks for true peaks below −1 dB, or below −2 dB when the master is louder than −14 LUFS. Other platforms publish different references; the [streaming loudness standards guide](https://soundforgepro.com/streaming-loudness-standards/) compares them. | Where the master goes | Output Level | True Peak | Mode | Why | | ------------------------------------------ | ------------ | --------- | ----------------------------------- | ---------------------------------------------------------------------------------------------------- | | Streaming, near −14 LUFS | −1.0 dB | On | IRC 4; IRC 5 if your computer copes | Spotify's true-peak limit for lossy formats | | Loud master, above −14 LUFS | −2.0 dB | On | IRC 5 | Spotify's tighter limit for loud masters; the published IRC 5 comparisons were made at −6 to −8 LUFS | | Master Assistant's Full Scale destination | −0.1 dB | Off | As chosen by the Assistant | iZotope's own full-scale setting; too hot for Spotify's true-peak advice | | Recording with a limiter on the master bus | Your choice | Off | IRC Low Latency | The lowest latency and CPU of all modes | Two caveats. Spotify's Loud setting plays at −11 LUFS and runs soft, dynamic tracks through its own limiter, which engages at −1 dB with a 5 ms attack and 100 ms decay, so a dynamic master can still meet a limiter you did not choose. And the Assistant's streaming destination already uses −1 dB with True Peak on, which lines up with Spotify; its Full Scale destination does not. ## How to set up the Ozone 12 Maximizer 1. Insert Ozone on the last slot of the master, post-fader, and keep the Maximizer as the last module in Ozone's chain, so nothing after it can push peaks back over the ceiling. 2. Choose the mode. Start with IRC 4 for moderate limiting, switch to IRC 5 for a loud master if playback stays clean, or use IRC Low Latency while you are still recording. 3. Set Output Level and turn True Peak on: −1.0 dB for streaming, −2.0 dB if the master will be louder than −14 LUFS. 4. Raise Gain while you watch the gain reduction readout and the Gain Trace, until you reach the loudness you want. 5. To compare modes or Character settings fairly, turn Link on so the louder version cannot win by volume alone. When you are done, switch Link off and reset Output Level to your ceiling. 6. Set Character by ear, then listen to Delta to hear what the limiter is removing. 7. Add Upward Compress, Soft Clip or Transient Emphasis one at a time, and only when the limiter alone does not get you there. Check Delta after each change. 8. Bounce the file and measure its integrated loudness and true peak. Learn Input Gain and Master Assistant estimate; the rendered file is what a platform measures on upload. In Sound Forge Pro, load Ozone 12 as a VST3, since that is the format both sides share; the [Sound Forge Pro plugins guide](https://soundforgepro.com/sound-forge-plugins/) shows where to point Sound Forge at your VST3 folder. Sound Forge is not on iZotope's tested host list for Ozone 12.0.0, so use the trial to confirm it behaves on your system before you buy. Apply Ozone as the last process on the finished master and leave bit-depth reduction for the very end. If you only need a quick limiter without buying anything, Sound Forge Pro's classic [Wave Hammer](https://soundforgepro.com/sound-forge-wave-hammer/) runs a compressor into a Volume Maximizer, and [how to master a track in Sound Forge Pro](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/) walks through the full order of operations. ## Test results: what published reviews report about IRC 5 This composite result counts eleven independent sources published between September 2025 and May 2026: magazine reviews, specialist blogs and user reports. Most of them describe listening comparisons rather than meter readings, so the result is a count of findings, not an average. | Finding about IRC 5 | Sources that report it | | --------------------------------------------------------------------- | ------------------------------- | | Louder or cleaner than earlier modes, with less pumping | 8 of 9 that describe the sound | | Tonal change, odd results when pushed, or another mode sounded better | 4 of 9 that describe the sound | | Heavy CPU load or real-time dropouts | 6 of 7 that discuss performance | | Workaround: raise the buffer, freeze or render offline | 3 of 7 that discuss performance | Eight of the nine sources that describe the sound say IRC 5 limits louder or cleaner. [Sound On Sound](https://www.soundonsound.com/reviews/izotope-ozone-12-advanced) found it let levels go "just a touch further while retaining the signal's coherence". [Sounds of Revolution](https://www.sounds-of-revolution.com/review-izotope-ozone-12/) credited it with "that extra dB or two" of loudness that Ozone 11 rarely reached without distortion or flatness. [Pluginerds](https://pluginerds.com/ozone-12-advanced-review/) compared IRC 5 with IRC 4 on several rock and hip-hop masters at −8 LUFS integrated and heard more open cymbals and cleaner vocal transients. [Gear Gods](https://geargods.net/news/izotope-ozone-12-the-gear-gods-review/) called it the best limiter it had put on a master bus, and [MusicTech's review](https://musictech.com/reviews/plug-ins/izotope-ozone-12-review/) lands on the same side. Four of the nine add a caveat. The same Sound On Sound review preferred other IRC modes in plenty of cases. Pluginerds keeps IRC 4 for lighter limiting where transparency matters most. [dxt3r](https://dxt3r.com/izotope-ozone-12-review/) reached around −6 LUFS on an EDM master with decent punch but found it slightly thinner than Waves L4 and not always as transparent as earlier modes; that site promotes Waves through affiliate links. In a [RealGearOnline upgrade thread](https://realgearonline.com/thread/19922/ozone-12-worth-upgrade), one user found IRC 5 odd-sounding, and a mastering engineer warned that pushing it hard can set off "a bit of a seesaw type thing". iZotope's own guide warns of a subtle tonal shift. Every comparison that named a loudness was made at a loud target: −8 LUFS at Pluginerds, which uses IRC 5 for targets around −8 to −10, and about −6 at dxt3r. None reported results near −14 LUFS, so the case for IRC 5 is a case for loud masters. On performance, six of the seven sources that discuss it report heavy CPU load or real-time trouble; Pluginerds is the exception and says CPU use feels reasonable even with the full module rack. The numbers are in the next section. **My verdict:** if your master only needs a few dB of limiting, I would not chase IRC 5\. IRC 4 costs less CPU, and reviewers such as Pluginerds still keep it for lighter work. When you push for a loud master, IRC 5 is the mode the published reports favor, as long as your machine can play it back. ## CPU and latency: keeping IRC 5 playable IRC 5 is the heaviest mode by iZotope's own description, with the most CPU use and the most latency. The published numbers are single reports from different hosts, meters and builds, so I list them rather than average them: - [Gearnews](https://www.gearnews.com/izotope-ozone-12-studio/), on a pre-release build: a Mac Studio M1 Max played back with many audible dropouts at a CPU load of only about 20%, while rendering worked fine. - A user in a [Native Instruments Community thread](https://community.native-instruments.com/discussion/47629/irc-5-is-unusable-in-realtime-on-mac-os-15-6-1-m4-max-64gb-ram), running Ozone 12 in its launch week on an M4 Max with macOS 15.6.1: 20 to 35% CPU in Ableton Live with Ozone alone on the master in IRC 5 and the transport stopped. In Bitwig the CPU meter read 22% at a 2048-sample buffer with the transport stopped, while at 256 samples the DSP meter sat near 100% with dropouts. - Gear Gods called IRC 5 the most CPU-heavy mastering algorithm it had used, and said the sound was worth the trade. The workarounds in those reports match iZotope's advice. [iZotope's getting-started guide](https://docs.izotope.com/ozone12/en/getting-started.html) suggests removing modules you are not using, raising the host buffer, and using the Stereo channel mode rather than Mid/Side, Left/Right or Transient/Sustain. Gear Gods adds freezing tracks or running IRC 5 only at the bounce stage. On a slow machine I would audition in IRC 4, switch to IRC 5 for the final render, and then listen to the rendered file, because the tone can shift between modes. The latest release in [iZotope's Ozone release notes](https://www.izotope.com/pages/release-notes/ozone-standard) is 12.1.0, from December 1, 2025\. It fixes slow UI loading and instantiation times, but the notes list no IRC 5 or Maximizer CPU change, so check playback on your own system during the trial. Latency matters too: IRC 3, IRC 4 and IRC 5 all add high latency, and IRC 3 may not run in real time above 48 kHz. While you record through the master bus, IRC Low Latency is the safer choice.