The Lean On Me Cast Unpacking The Multistar Powerhouse Lineup

How I Finally Made Multiband Processing Actually Work For Me

I spent three years fighting with multiband compressors before I realized most tutorials were backwards. They all start with "buy this plugin and follow these settings." That never works because every mix is different. Here's what actually happened when I stopped treating multiband like a magic fix and started treating it like a surgical tool. I need to be clear about something most people skip. The "Multistar Powerhouse Lineup" is a way of thinking about multiband processing chains as individual dedicated processors rather than one all-in-one plugin doing everything. You split frequencies, process each band with purpose-built tools, then glue them back together. The old way was throwing a single multiband compressor at a problem and hoping it helped. It usually made things worse by creating pumping artifacts that drew attention to themselves instead of solving anything. My workflow starts differently. I identify the actual problem frequency first, before touching any processing. A kick drum that's too boomy around 200Hz doesn't need broadband compression. It needs a narrow EQ cut and maybe a transient shaper if the attack is sloppy. I learned this the hard way during a live recording session where a bassist's amp was ringing at exactly 340Hz on three of five songs. Throwing a multiband compressor at it created audible pumping between sections that ruined the take. I ended up riding a parametric EQ with a narrow Q and automated the gain reduction only on the offending bars. Took twenty minutes instead of an hour of argument.

What Each Band Actually Does In Practice

Below 80Hz on most mixes is your low end management zone. This is where sub-bass lives and where phase problems accumulate fastest. I use a high-pass filter on everything except the kick and bass tracks, but I set the cutoff based on what each instrument actually produces rather than using a default number. The kick might need to go down to 30Hz. A vocal definitely doesn't need anything below 100Hz and probably not below 80Hz either. Between 80Hz and 250Hz is the mud zone and also where fundamental body lives for many instruments. This is the band that destroys mixes when it's out of control. Too much energy here and everything sounds congested. I don't compress this band aggressively. I cut problem frequencies with resonant EQ instead. Compression here tends to make the mix sound hollow because you're reducing the body of instruments along with the flab. The 250Hz to 2kHz range is where most masking happens. Guitars fight vocals. Snare fights cymbals. This is also where human hearing is most sensitive, which means small problems sound huge. A 3dB boost at 800Hz on a snare track that already sits near a vocal is the difference between it cutting through and disappearing completely. I process this band with saturation and gentle compression rather than heavy dynamics control.

Above 2kHz is clarity territory but also sibilance and harshness central. This is where de-essing happens, where I add air with shelving EQ, and where I catch harsh resonances that no amount of low-end work will fix. The mistake people make here is over-compressing. Brightness doesn't need compression. It needs selective EQ. A single resonant peak at 5kHz causing ear fatigue is fixed with a narrow cut, not a compressor trying to tame the whole band.

Phase Alignment Is The Thing Nobody Talks About

When you split signals into multiple bands and process them separately, you introduce phase shifts at the crossover points. These shifts are inaudible in isolation but become obvious when you sum the bands back together. The result sounds thinner or oddly hollow, especially on transients. I use linear phase crossovers when I'm doing serious multiband work and minimum phase when I'm just doing light cleanup. Linear phase preserves timing at the cost of CPU. Minimum phase is lighter but shifts transients slightly. For most mixing situations the shift is negligible, but on drums it can make a snare hit sound less punchy. I also check my multiband processing in mono. What sounds balanced in stereo can collapse completely when summed. Low end phase cancellation is the usual culprit. A kick drum that looks fine split across left and right channels can disappear almost entirely when everything goes mono. This is why I always bake a mono check into my multiband workflow before considering any band processed.

When Multiband Processing Actually Helps

Master bus processing is where I use multiband most often. A well-tuned multiband compressor on the master can tighten low end without affecting transient detail in the mids. I set the low band to compress only when the kick and bass interact badly, the mid band to control vocal presence, and the high band to manage overall brightness without triggering a de-esser. This gives me control that a single broadband compressor never could. Individual track processing works too when you have a specific problem. A vocal with sibilance issues and uneven low-mid presence benefits from splitting those problems into separate bands. One band handles the 5-8kHz sibilance with a de-esser style compressor. Another band tames the 300-500Hz muddiness with gentle compression. The rest of the signal passes through untouched. This is cleaner than trying to fix both problems with broad EQ moves. There's also the case of problematic room acoustics. If your monitoring environment has a resonance at a particular frequency, multiband processing lets you address it surgically without coloring the rest of the spectrum. I've worked in rooms where the low-mid build-up was so bad that broadband compression made everything sound boxed in. Splitting out the problem band and applying treatment only there preserved the natural character of the rest of the mix.

What Multiband Processing Cannot Fix

A bad source recording will stay bad no matter what multiband processing you apply. Compressing a poorly recorded vocal won't make the performance better. EQing a phasey mic placement won't fix the fundamental issue. Multiband tools amplify what's already there. If the original recording has problems, splitting it into bands just lets you apply different types of damage to different frequency ranges, which somehow feels worse rather than better. Also worth noting: multiband processing adds latency. Even minimal setups introduce a few milliseconds of delay. This matters if you're tracking through the processor while recording. I always bypass multiband processing during tracking sessions and only engage it during mixing. The latency is imperceptible in playback but enough to throw off a performer's timing if they're monitoring through it in real time.

My Actual Signal Chain

For master bus work I route through a splitter, send each band to its own channel strip with the appropriate processor, then recombine. I use a high-quality expander on the sub band to clean up rumble that sneaks past my high-pass filters. A gentle compressor on the low-mids only engages when I hear pumping. A de-esser on the high band catches sibilance without affecting the overall brightness. The key is setting thresholds so each processor barely moves the needle. If you're seeing 3dB or more of gain reduction on any band, you've set it too aggressively and you're probably making the problem worse rather than better. I've found that the best multiband processing sounds like no processing at all. If you can hear it working, you've gone too far. The goal is translation across systems, not a particular sound. A mix that sounds good on headphones, in a car, and through studio monitors is the actual target. Multiband is just one way to get there when the broadband tools aren't precise enough.