Concrete Limiter vs. Ozone 7: Why I Use Both in My Mastering Workflow

Concrete Limiter and Ozone 7 Maximizer in a teal studio comparison cover

When it comes to music production, I’ve learned that every plugin doesn’t have to do everything. That’s why my Concrete Limiter vs Ozone 7 mastering workflow gives each tool a specific job. Sometimes the best results come from understanding what a plugin does well rather than asking it to do everything.

That’s exactly how I feel about the Sonar ProChannel Concrete Limiter and iZotope Ozone 7. I’ve used both for years, and recently I found myself returning to Ozone 7 for mastering—not because Concrete Limiter stopped working, but because I wanted each processor to handle a different responsibility.

The Concrete Limiter helps control peaks on my master bus. Ozone 7 helps me get the finished record loud. Here’s why that distinction matters to me.

Why I Still Use the Concrete Limiter

If you’ve read my previous Sonar articles, you know how much I use ProChannel. It’s part of my production workflow, from individual tracks to the master bus. One plugin I’ve come to appreciate is the Concrete Limiter.

Concrete Limiter is capable of mastering-level limiting. But in my experience, the way it handles sudden peaks is what makes it especially valuable.

A kick can hit harder than the surrounding instruments. A snare can jump out unexpectedly. Even when the overall mix sounds balanced, a short transient can push the level higher than I want. I use Concrete Limiter to help keep those moments under control without simply turning the whole mix down.

The important part is not overdoing it. I want to tighten the edges of the mix, not flatten the drums or take away the energy.

Controlling Peaks Isn’t the Same as Making Music Loud

Peak control and perceived loudness are related, but they’re not identical. A mix can have tall transient peaks without sounding especially loud. Another mix can sound consistently loud because more of its average level is elevated.

That’s why I don’t need one limiter to handle every responsibility. I want Concrete Limiter to help catch the occasional peaks, then I can think about the final loudness separately.

Why I’m Returning to iZotope Ozone 7

Here’s the funny part: I’ve had Ozone 7 installed for years. Even as newer versions appeared, there was something about version 7 that made me keep it around. I know how it responds to my music, and that familiarity matters.

I’ve been using Ozone 7’s Maximizer again because I want it to handle the final loudness. I’m not asking it to repair a poorly balanced mix or fix problems I should have handled in production. I want to bring an already good mix up to the level I’m looking for while listening carefully to what happens to the music.

Concrete Limiter vs Ozone 7: How I Give Each a Different Job

1. Build the mix in Sonar

I start with the actual mix: instrument levels, EQ, compression, stereo placement and the overall balance. My Neve console emulation and Softube Saturation Knob may be part of that process when they suit the record. The mix needs to sound good before I chase loudness.

2. Let Concrete Limiter manage peaks

On the master bus, Concrete Limiter helps control transient spikes, especially from drums. I watch how much gain reduction is happening. If it’s working too hard, I need to reconsider the settings—or even go back into the mix. I still want my kick and snare to hit.

3. Let Ozone 7 handle final loudness

At the mastering stage, Ozone 7’s Maximizer becomes my loudness tool. I’m listening for the kick’s impact, bass clarity, snare attack, instrument separation and the overall feel. A louder master isn’t automatically a better one.

The Danger of Using Two Limiters

Two limiters do not automatically make a better master. If Concrete Limiter is already reducing too much of the signal, Ozone receives a mix that may have lost punch. Push Ozone too hard after that, and I can lose even more dynamics.

My goal is to let each processor do only the work it needs to do. I compare processed and bypassed versions at matched playback levels, because louder can seem better simply because it’s louder. If a limiter isn’t helping, I don’t need it engaged just because it’s in my usual chain.

Why I Don’t Chase One Loudness Number

LUFS and true-peak measurements are useful, especially when preparing music for distribution. But I don’t think every song should be forced to the same loudness. A hard-hitting trap instrumental and a smooth R&B track may need different treatment.

I use the meters to inform my decisions, not replace my ears. The final record should be loud enough for its purpose without sacrificing the qualities that made the mix work.

There’s Nothing Wrong With Older Plugins

Ozone 7 isn’t the newest Ozone, and Concrete Limiter isn’t a new discovery. But both still earn a place in my workflow. Years of learning how my tools respond count for something.

I’m always willing to try newer technology, but I’m not abandoning a plugin that’s helping me make good music just because another version exists. If it sounds good and does the job, I’ll keep using it.

Final Thoughts

The lesson isn’t that every producer needs both Concrete Limiter and Ozone 7. It’s that you should know what job you’re giving each processor. For me, Concrete Limiter helps control the peaks and Ozone 7 helps me reach the final loudness.

I don’t need every limiter to make my music louder. Sometimes I need one to control the peaks so another can handle the loudness.

Try using a limiter just to catch peaks, then compare that with using one to raise overall loudness. Pay attention to the drums, bass and energy. You might discover that a tool you’ve used for one purpose is even more valuable for another.

If you want more practical music production discussions, read my Sonar ProChannel vocal mixing guide and how to record vocals over a beat. You can also explore original instrumentals in the NJMP Beats Beatstore.