Music Production Guide

05 - Locked vs Taste Commit Gate

Purpose

The guide exists to reduce fiddling, but nothing in it tells you a part is done. This page does. It is the behavioral stop rule: which chains are locked and must not be reopened, which knobs are the only legal things to adjust, and the trigger that says "commit and move on."

This is not the pre-bounce checklist in 04 - Make It Sound Expensive — that is whole-mix QA before a bounce. This is per-element: "stop touching this sound." Read it when you notice you've reopened a plugin you already dialed.

Main Rule

By default, a part is locked. Only a short, named list of knobs stays "taste." If a change isn't on the legal list, you are fiddling — close the plugin.

A part is finished when its taste knobs are set and its locked chain is committed. "Finished" is a decision, not a feeling.

1. Locked — never reopen once dialed

Set these when you build the part or the session template, then leave them. Reopening one mid-song is the single most common form of fiddling.

  • Send-return settings — the plugin, return EQ, and predelay on every standing send (17 - Default Send Rack). You adjust send amount, never the return.
  • Bus glue / tape — drum-bus and mix-bus compression and tape are set once for the session.
  • Sidechain routing — what ducks what, and how much, is structural; dial once.
  • Low-end ownership — mono-below-120, kick/bass split, who owns each band (18 - Frequency and Depth Map).
  • Corrective EQ / cleanup — HPF, mud dip, de-ess, RX repair. Fixing a fix means the source was wrong; re-record instead.
  • The recipe's printed character move — once you commit the amp, the Trash layer, the saturation, print it and treat it as the source.

If a locked item feels wrong, the real fix is almost always the source or the arrangement, not the locked setting.

On any track, these are the only things you're allowed to keep adjusting:

  • Level / balance — including automation rides for intelligibility.
  • The recipe's 2 marked taste knobs — every recipe names exactly two (e.g. glide time + delay-throw amount). Those, and nothing else on that part.
  • Send amount to the standing returns (and feedback/decay as an automated moment on S2/S3).
  • Automation depth — how far a filter opens, how big a throw blooms, when a layer enters.

That's the whole list. Reverb plugin choice, return EQ, a third character plugin, "let me just re-tune the patch" — none of those are taste. They are either locked or bloat.

3. The Print Trigger — when to commit

Stop and commit when any of these is true:

  • You've A/B'd twice (original vs change) and there's no clear winner → keep the original, commit, move on.
  • You're adjusting a knob that isn't on the taste list → close the plugin; the part is done.
  • You're soloing to make a decision a third time → decide in context or commit.
  • The change is smaller than the noise floor of your attention (you can't reliably hear it) → it doesn't matter; commit.
  • You've muted the part to test it and the song is fine either way → cut it or commit it, don't keep tuning it.

When the trigger fires: print/commit the character moves, freeze the track if useful, and write the part off your to-do list. Re-opening a committed part needs a reason you can name (see the three-question test in 16 - Overlap and Redundancy Map) — not a vague itch.

Quick Self-Check

Before you touch a part you already dialed:

  1. Is the knob I'm reaching for on the taste list? If no → stop.
  2. Can I name what's wrong and why the locked setting can't be left alone? If no → stop.
  3. Have I already A/B'd this twice? If yes → commit.
  4. Would fixing the source or arrangement solve it better than this tweak? If yes → do that instead, then re-lock.

If you can't pass this check, the part was already finished.