Mix Revisions: Turning Notes into Session Changes
Turn each note into a time, an action and an acceptance line before touching the session.
Related
Turn words into session language
"Warmer vocal" is not an instruction. Ask for three things: a time, a reference and an acceptable boundary. Warm can mean more 200 Hz, less sibilance, a shorter reverb or added distortion, and those are very different moves. Repeat the note back until the client confirms you mean the same thing; if that fails, make two versions instead of guessing inside one.
The revision sheet
| Note | Lands on | Check first | Acceptance |
|---|---|---|---|
| Vocal too dry | send level and pre-delay | wet/dry, line endings | tails enter the backing naturally |
| Drums not hard enough | bus attack and saturation | transients, polarity | impact remains at low volume |
| Too much low end | bass and kick at 60–120 Hz | masking, mono | no boom on a phone, no mud in a car |
| Overall too full | arrangement layers and mids | 2–5 kHz build-up | hierarchy still reads |
Every row must land on a track, a parameter, an amount and one acceptance sentence. If a note cannot be written that way, do not start.
Run one round
Freeze the current version and duplicate the session before touching it. Work through the timecodes and change only what is on this round's list; log anything else for the next round. Export at the same loudness and match levels for A/B, or the louder version will always win. Send a change log: what changed, what did not, and why. Start the next round only after approval.
Versions and delivery
Put version and date in the file name, and use snapshots or Save As inside the session rather than overwriting. Keep notes, references and exports in one folder. After approval, export stems and an instrumental, with sample rate, bit depth and bus processing written down. Keep rejected versions until the project closes so a changed mind can be answered.
When not to comply
If a note hurts intelligibility, breaks the delivery spec or comes only from a phone speaker, explain the cost and offer an alternative. A matched-loudness comparison settles arguments faster than adjectives. If the client insists, do it and document it, but do not put blame in the file name. State the number of revision rounds in the contract and price the rest.
Listen in the library
All tracks from midicn-lib — inline badge is the license tier (C1 commercial / C2 non-commercial / C3 study only).
Along the same line
Sources
- Bobby Owsinski, The Mixing Engineer's Handbook（Cengage）修订与客户沟通章节
- Avid, Pro Tools Reference Guide 中 playlists、markers 与 comments 章节
- Apple, Logic Pro User Guide 中 alternatives 与 project versions 章节