This Week in Mixing — Week of July 28, 2026

August 1, 2026 · MixDiagnose Team · 5 min read

This week brought heavy-hitting plugin updates, a renewed debate on AI in mixing, and some of the best community discussions we've seen all month. FabFilter shipped a major EQ update, iZotope pushed Ozone 12, and r/mixingmastering had a viral thread on gain staging that every producer should read. Here's the breakdown.

1. FabFilter Pro-Q 4: Dynamic EQ meets spectral display

FabFilter released Pro-Q 4 this week, and the headline feature is dynamic EQ bands integrated directly into the spectral display. You can now set a threshold on any band and it acts as a dynamic EQ — boosting or cutting only when the signal exceeds the threshold — without leaving Pro-Q or adding a separate dynamic EQ plugin. The update also introduces "Adaptive" mode, which analyzes your track and suggests corrective EQ moves based on spectral imbalances it detects.

Why it matters: Dynamic EQ solves problems that static EQ can't. A vocal that gets harsh only on the "s" and "t" sounds, a bass that resonates only on certain notes — these are dynamic problems. Until now, you needed a separate plugin (Pro-Q 3 + Pro-MB, or a dedicated dynamic EQ like TDR Nova). Pro-Q 4 collapses that into one interface. The Adaptive mode is controversial — some engineers love the starting point, others see it as a crutch — but it's useful for quick fixes on deadline.

MixDiagnose angle: After applying corrective EQ, always verify with a spectrum check. Run your mix through the spectral analyzer and compare before/after. If you cut 3 dB at 300 Hz to fix a boxy vocal, the spectral analyzer should show a visible reduction in that region. If it doesn't, your EQ move isn't doing what you think it is — check your Q width and gain reduction.

2. iZotope Ozone 12 Advanced: Mastering assistant gets smarter

iZotope shipped Ozone 12 Advanced this week. The Master Assistant — which analyzes your mix and suggests a mastering chain — now references genre-specific tonal balance targets. Instead of aiming for a generic "balanced" curve, you can tell it you're mastering hip-hop and it targets the low-end weight and top-end air typical of the genre. The Stabilizer module (introduced in Ozone 11) got an update with improved transient detection, and the Maximizer's IRC IV algorithm now handles low-frequency content without the pumping that plagued earlier versions.

Why it matters: Genre-aware tonal balance targets are a real improvement. A jazz master and a trap master should not look the same on a spectrum analyzer — and now the Assistant acknowledges that. The Maximizer improvement matters more than it sounds: IRC IV's pumping on sub-heavy material was the #1 complaint from Ozone 11 users, and fixing it means you can push louder without audible artifacts.

MixDiagnose angle: Mastering assistants are starting points, not finish lines. After running Ozone 12's Master Assistant, check your integrated LUFS with the LUFS checker. If the Assistant pushed you to -8 LUFS for a streaming target, that's too loud — streaming platforms will turn you down. Aim for -14 LUFS for Spotify, -16 for Apple Music, and verify before you print.

3. r/mixingmastering viral thread: "Gain staging is not about volume"

A post on r/mixingmastering titled "Gain staging is not about volume — it's about headroom" went viral this week, generating 400+ comments and cross-posting to r/audioengineering. The core argument: most producers think gain staging means "keep your faders around unity" or "don't clip your master bus." The thread reframed it as managing the signal-to-noise ratio and plugin operating levels throughout the entire signal chain — from preamp simulation to final bus.

The top comment broke down the three levels of gain staging: (1) input gain — feeding plugins their optimal level (many analog-modeled plugins expect around -18 dBFS RMS), (2) inter-plugin gain — using trim plugins between processors so each plugin sees the level it was designed for, and (3) bus gain — managing headroom on your group buses so your master bus compressor works in its sweet spot.

Why it matters: Plugins are calibrated. An 1176 emulation set to 4:1 ratio with 3 dB of gain reduction responds differently at -18 dBFS input than at -6 dBFS input. If you feed it hot, you're working the compressor harder than you think. This is why mixes that "should work" sound inconsistent — the plugins aren't seeing the levels they were modeled at.

MixDiagnose angle: Poor gain staging shows up in the dynamic range measurement. If your crest factor (difference between peak and average level) is under 6 dB, you've compressed too hard — and the likely cause is plugins being fed too hot and reacting aggressively. Check your dynamics with the LUFS and dynamics checker before you commit to a bounce. A healthy mix sits between 8–12 dB crest factor.

4. Spitfire Audio LABS update: "Drum Productions" library

Spitfire Audio added "Drum Productions" to their free LABS line this week — a collection of professionally recorded drum loops and one-shots captured at AIR Studios. The samples are dry, giving you full control over processing. No reverb, no room sound, just the drums.

Why it matters: Dry drum samples are a mixing gift. When samples come pre-processed with reverb and compression, you're stuck with someone else's decisions. Dry samples let you build your own room, your own compression, your own character — and they sit in a mix more naturally because you're matching them to the track, not fighting a baked-in reverb tail.

MixDiagnose angle: When you add your own reverb to dry drums, check the spectral content of the reverb return. Use the spectral analyzer to verify the reverb isn't building up below 200 Hz — that's where reverb mud lives. High-pass the reverb return at 200 Hz and you'll keep the low end clean while the drums get the space they need.

5. The AI mixing debate: Can algorithms replace mix engineers?

A discussion thread on r/audioengineering about AI-assisted mixing tools — specifically the growing number of "one-click mixing" services — generated heated debate this week. The split: experienced engineers dismissed the tools, citing their inability to make creative decisions (vocal level relative to the beat, drum bus character, reverb choices). Newer producers praised them as learning tools that provide a starting point they can refine.

The nuanced position, which rose to the top: AI mixing tools are useful for analysis, not decisions. They can tell you your mix is -9 LUFS and harsh at 4 kHz, but they can't tell you whether the harshness is a problem or an aesthetic choice. A harsh vocal on a punk track is intentional. The same harshness on a jazz ballad is a mistake. Context matters, and algorithms don't have it.

Why it matters: The tools are improving fast. The question isn't whether AI will replace mix engineers — it won't — but whether producers who use AI analysis tools will make better mixes than those who don't. The answer is yes, if the tools are used as diagnostics rather than autopilots.

MixDiagnose angle: This is exactly what MixDiagnose does. It doesn't mix for you — it tells you where your mix has problems so you can fix them yourself. The mix analyzer flags frequency imbalances, loudness issues, and stereo problems. It doesn't fix them. You do. That's the point. See our full blog for guides on fixing each issue the analyzer surfaces.

6. Free plugin spotlight: TDR Limiter 6 GE update

Tokyo Dawn Labs updated TDR Limiter 6 GE (free edition) this week with improved oversampling and a new "Brimstone" limiting style. The update improves transparency on program material with complex transients — specifically, the limiter no longer produces the low-level distortion artifacts that affected the previous version on acoustic material.

Why it matters: TDR's free plugins consistently outperform paid alternatives. The Limiter 6 GE is the best free limiter available — and with this update, it's closing the gap with FabFilter Pro-L 2 on transparency. If you're on a budget, you don't need to pay for a limiter. Period.

MixDiagnose angle: Limiters are the last thing in your chain, and they're where loudness mistakes happen. After limiting, check your true peak with the LUFS checker — it should stay below -1.0 dBTP. Inter-sample peaks can exceed your sample peaks by up to 1 dB, so if your sample peak meter says -0.3 dB, your ISP could be clipping. Set your limiter ceiling to -1.0 dBTP and you're safe.

7. Community tip: The 30-second mono check

Multiple posts across r/mixingmastering and r/audioengineering this week reinforced a technique that keeps proving its worth: the 30-second mono check. Sum your mix to mono and listen for 30 seconds. If elements disappear, you have phase issues. If the bass gets louder, your low end is wide (it shouldn't be). If the vocal drops in level, your stereo widening is pulling it apart.

Why it matters: Mono compatibility isn't about people listening in mono — almost nobody does that anymore. It's about what happens when your mix is played on a phone speaker, a bluetooth speaker, or any system that partially collapses stereo. If your mix falls apart in mono, it falls apart on the most common playback systems in the world.

MixDiagnose angle: MixDiagnose checks mono compatibility automatically. Upload your mix and look at the stereo width analysis — if the mono sum is more than 3 dB quieter than the stereo version, your mix has phase issues that will cause collapse on small speakers. The fix is usually narrowing your stereo widener or checking for phase cancellation between doubled tracks. Run the spectral analyzer and compare stereo vs. mono to find which frequencies are collapsing.

The takeaway

This week was about tools getting smarter and the community getting wiser. FabFilter and iZotope both shipped updates that use analysis to suggest moves — but the best threads on Reddit this week were about fundamentals: gain staging, mono compatibility, and the limits of AI. The pattern holds: tools accelerate good habits, they don't create them. The producers who win are the ones who understand why their mix has a problem, not just where. Check your work before you bounce, fix what the analysis surfaces, and your mixes will translate everywhere.

← Back to blog