Production guides · Meme Plugins · 27 October 2026 · Updated 1 November 2026
Build a static mix by balancing the existing tracks with level and panning before adding new corrective effects. Establish the song’s focal point, bring supporting parts into a useful relationship, then listen through section changes. Keep notes on the problems that balance alone cannot solve so the next processor has a specific job.
You do not need to strip away essential sound design to prove a point. A synth patch, committed guitar sound or deliberate delay may be part of the arrangement rather than an optional mixing correction.
1. Start from an organized, reversible session
Save a new version. Name the tracks, check their outputs and identify shared returns or groups. Know which processing is already printed into the audio and which is still active in the session.
iZotope describes a static mix as a preliminary balance built with level, panning and little else. Definitions vary; the useful purpose is to hear what the parts already do together before accumulating more treatment.
If you temporarily bypass a processor, check the level difference. Use the plugin level-matching workflow instead of mistaking a louder rough mix for a better one.
2. Choose an anchor and add parts deliberately
Pick the lead event for the passage: perhaps the vocal, a melody or a drum-led groove. Set a comfortable listening volume and a useful initial level for that anchor. Add the other parts one at a time, adjusting each while the important material plays.
Do not make every track equally prominent. Ask which part supplies rhythm, harmonic support, movement or a response to the lead. If two parts demand attention in the same gap, muting one briefly can reveal an arrangement decision that another EQ would not resolve.
3. Use panning for purposeful placement
After the basic levels make sense, compare a few clear positions for supporting parts. Keep an earlier centered version available. Listen for a useful balance between sides and check whether a stereo source’s pan control is a balance control or a different panning mode in your software.
Panning can separate positions, but it does not guarantee that overlapping sounds will remain clear when combined into mono. Use a temporary mono check before deciding that width has solved the whole problem.
Example: an eight-track chorus, faders first
Imagine a chorus with kick, snare, hats, bass, keys, guitar, lead vocal and backing vocals. This is a hypothetical exercise, not an auditioned session.
- Keep the lead vocal as the initial anchor, then balance kick, snare and bass for the chorus’s intended drive.
- Add hats, keys and guitar with the lead still audible. Try a quieter supporting part before lifting the vocal again.
- Add backing vocals as support rather than matching their level to the lead by habit.
- Save that fader-only balance. Then compare a panning pass for keys, guitar and backing parts.
A fictional first-pass note might read: “Lowering the keys helped the words; the last quiet word still disappears; the long bass note covers the next kick; one guitar entrance remains sharp.” These are illustrative observations, not promised results. They define separate next tasks instead of one instruction to make the whole mix brighter or louder.
4. Check more than the loudest chorus
Play the verse, chorus and transition without continually touching controls. One fixed balance may reveal a section that needs a later ride, an edit, or a different arrangement. Do not force the chorus setting onto every passage just to keep the mix static forever.
Keep enough output margin for the combined mix and your next steps. There is no universal fader position that proves correct gain staging. If unwanted overload appears, follow the clipping signal path.
5. Turn the remaining issues into a short plan
Write the source, passage and desired change. “Guitar entrance is sharp in bar nine” gives an EQ or automation experiment a purpose. “Everything needs compression” does not.
Save a rough export and compare against an appropriate reference at matched loudness using the reference-track workflow. Keep the static version as the baseline for judging later processing.
Static-mix questions
Should I remove every effect?
No. Preserve the musical intention and document what remains. The exercise is to avoid unnecessary new correction, not erase the production.
Must one balance work for the whole song?
No. It establishes relationships and exposes where intentional movement is still needed.
Once the level relationships work, use the panning workflow to compare supporting positions and a clear musical centre. Check entrances and gaps as well as the full chorus.