Learn
What is cross-track de-masking?
A de-masking plugin removes the frequency clashes that bury instruments in a dense mix. But not all de-maskers work the same way. There are three broad approaches — and the difference between them decides how much manual work you do and how well it scales to a full session.
If you're new to the underlying problem, start with what frequency masking is. This page assumes you already know why dense mixes turn to mud and focuses on the tools that fix it.
Approach 1 — Single-track de-masking
The most common approach. You place a de-masker on one track, and it dynamically tames resonances and harshness on that track only. It's excellent for cleaning up a single source — a sibilant vocal, a resonant guitar, a boxy room.
The limitation: it has no idea what the rest of your session is doing. It can make one track cleaner, but it can't decide which of two competing instruments should yield to the other, because it only ever sees one of them.
Approach 2 — Sidechain "spacing"
Here one track listens to another and ducks the overlapping frequencies only when the other plays — a kick making room for a bass, a pad making room for a vocal. When it's set up well, it's clean and musical.
The limitation: it's manual and pairwise. Every relationship has to be routed and dialled in by hand. For one or two key pairs that's fine. For a forty-track orchestral session, routing every meaningful pair is impractical.
Approach 3 — Cross-track de-masking
The newest approach, and the one Spectral Engine is built around. You put one instance on every track. Instead of each working in isolation, the instances share a picture of the whole project and negotiate with each other: when two instruments collide, the plugin decides what yields based on the roles you assign (lead, support, background) and carves room only at the moments and frequencies where they actually compete.
The result is the behaviour the other two approaches can't offer on their own:
- Project-wide — it sees every track at once, not one in isolation.
- Automatic — no sidechain routing and no pairwise setup; you drop it on and assign roles.
- Scalable — the same workflow that handles four tracks handles sixty-four.
- Clean — minimum-phase carving, so no time-smearing or musical-noise artifacts.
Single-track de-maskers clean one source. Sidechain spacing handles one pair. Cross-track de-masking handles the whole session — automatically.
Which should you use?
- Polishing a single problem source → a single-track de-masker.
- One or two critical relationships (kick/bass, vocal/pad) → sidechain spacing.
- A dense, multitrack arrangement where everything competes — orchestra, choir, layered acoustic or pop productions → cross-track de-masking.
These aren't mutually exclusive. Many engineers still reach for static EQ and arrangement first, then let a cross-track de-masker handle the dozens of smaller collisions that would take hours to chase by hand.
Spectral Engine puts cross-track de-masking on every track in your session. Join the beta for early access.
Join the beta