Chapter 20 Exercises

This is the gateway exercise set for Parts V and VI, and it's built around one promise: by the end of Part C you will have a real static mix of your own track — the foundation every remaining tool chapter builds on. You'll need: your project (the one this book has grown since Chapter 2), your three reference tracks from Chapter 4 imported as files, your calibrated monitoring setup from Chapter 8, a way to sum your output to mono (DAW mono button or a stock utility plugin — Appendix E names it in every major DAW), and your notebook with two fresh pages headed MIX NOTES and ARRANGEMENT?. No other plugins are permitted anywhere in this set. That's not a suggestion; it's the curriculum.

Selected answers and worked examples appear in the back-of-book Answers appendix. Exercises marked 🎧 need focused listening time; budget about 15 minutes each. Pacing that respects your ears: Part A in one sitting (reading and writing), Part B spread across two or three days, C1 on a fresh-eared evening you protect in advance (it's the big one — 90 minutes plus prep), the rest of Part C in the days after, and Parts D and M as consolidation. The next-day listen built into C1 is part of the exercise, not an optional extra.

Part A — Conceptual

A1. The definition, owned. Define mixing in your own words without using the words "plugin," "EQ," or "compression." Then define balance, static mix, and mono compatibility the same way. Finally, explain why "a mix is pre-decided attention" and your mixing definition are the same claim wearing different clothes.

A2. The four jobs. Name the four jobs of a mix and, for each, write one sentence describing what a mix sounds like when that job — and only that job — has been neglected. (Example format: "Balance neglected: …") Which of the four can faders alone perform, and which must wait for later chapters' tools?

A3. Can/cannot triage. Classify each of the following as something a mix CAN fix, CANNOT fix, or CAN PARTIALLY fix (and say which stage owns the real fix): (a) the lead vocal is inaudible under the guitars in the chorus; (b) the acoustic guitar was recorded in a boxy untreated closet; (c) the second verse feels emotionally flat even though every part is audible; (d) the hi-hats feel buried but turning them up buries the snare; (e) the bass is inconsistent — some notes boom, some vanish; (f) seven good parts all play through the entire song.

A4. The threshold, stated and applied. State this chapter's threshold concept from memory. Then describe the "disguise test" — the cheap experiment that distinguishes a mix problem from an arrangement problem — and explain why faders expose the disguise faster than plugins do.

A5. Hierarchy logic. The mixer's hierarchy says the pad yields to the vocal. Explain the difference between "the pad is quieter than the vocal" and "the pad yields to the vocal" — why is the hierarchy a collision rule rather than a volume chart? Give one genre where the default crown changes, and what changes it.

A6. Mono reasoning. A producer says: "Nobody listens in mono anymore — mono checking is boomer superstition." Write a three-part rebuttal: one practical playback argument, one perceptual argument (name the mechanism), and one workflow argument about what mono does for balance decisions specifically.

A7. Top-down vs. bottom-up. Define both philosophies in one sentence each, name the characteristic failure mode of each, and explain where this book's static-balance-first sequence sits between them — including the discipline that keeps later track-level work honest.

A8. The cost curve. Sketch (words or a quick graph) the cost curve of a deferred decision using a concrete flaw of your choosing — not the sibilance example from the sidebar. Show its price at four stages, and mark the difference between deferral-by-avoidance and deliberate deferral.

Part B — 🎧 Listening Lab

Same playback system for every exercise; calibrated level unless an exercise says otherwise; write everything down. These labs train the specific skill this chapter runs on: hearing balance as a set of decisions someone made.

B1. 🎧 What's loudest? (the balance ranking). Three records, three genres: Adele's "Hello," AC/DC's "Back in Black," and Kendrick Lamar's "HUMBLE." For each, listen to one chorus (or the hook) twice and rank the five most prominent elements, loudest first. Then answer: which element is unmistakably the crown in each? How far below it is element #2 — a hair, or a clear step? Which of the three mixes runs the steepest hierarchy (big gaps between ranks) and which the flattest? Keep these rankings; C1 will ask you to build one.

B2. 🎧 What's tucked? (the deliberate burial). Same method, opposite target: Billie Eilish's "bad guy," Fleetwood Mac's "Dreams," and Daft Punk's "Get Lucky." Hunt for elements that are present but tucked — things you feel before you can point at them (a shaker, a keyboard pad, a background vocal, a percussion loop). Find at least two per song. For each: would the chorus feel thinner without it? (Imagine it gone.) Write one sentence on what "tucked but load-bearing" teaches you about the bottom of the level map — and about why "too quiet beats too loud" still leaves things audible.

B3. 🎧 The mono collapse. Take one of your reference tracks plus your own track (pre-static-balance bounce, if you have one). Listen to each on headphones in stereo, then summed to mono at the same level, then on a phone speaker. Log per track: What vanished or shrank? Did the balance shift — did anything important step backward? Did anything get clearer in mono? (It happens — spatial glamour can hide balance truth in both directions.) Finish with one sentence: what does your reference's mono behavior tell you about how its balance was built?

B4. 🎧 Hierarchy safari (three genres, one question). Chris Stapleton's "Tennessee Whiskey," Daft Punk's "One More Time," and Nirvana's "Smells Like Teen Spirit." For each song, pause at three different timestamps (intro, verse, chorus) and answer the only question that matters: what am I supposed to be hearing right now? Note how confidently you can answer — that confidence is the mix enforcing a hierarchy. Then map each song's crown: who wears it in the intro, and what happens to that element the moment the crown's owner arrives?

B5. 🎧 The whisper test on the pros. Play one reference at your calibrated level, then again at whisper volume — quiet enough that a conversation nearby would cover it. At whisper level, what still reaches you? (Almost always: the vocal and the snare/backbeat.) What disappears first? Connect what you observe to Fletcher–Munson from Chapter 4, and write the implication for your own static balance in one sentence.

B6. 🎧 Balance from memory. Choose the reference you know best. Without playing it, write its level map from memory — top row to bottom row, like the chapter's diagram. Then play it and grade yourself. Most people discover they've remembered the vocal too quiet and the drums too loud relative to reality, or missed the tucked layer entirely. Whatever your error pattern is, write it down: it's a preview of the bias your own static balance will inherit unless the humility loop corrects it.

B7. 🎧 The crown handoff. Pick any one song from B1 or B4 and listen only to the transitions — the two bars either side of each section boundary. Your question at each doorway: who had the crown, who has it now, and how did the mix hand it over? (Common answers: the old crown drops or thins, the new one enters louder than polite, something mutes entirely for a beat.) Log at least three handoffs from one song. Then note which handoffs are balance decisions a static mix could hold, and which are moves — changes over time that will need Chapter 27's automation. This distinction — what the resting state can carry versus what must move — is one you'll be making on your own track within two chapters.

Part C — 🎛️ DAW Lab

C1. THE STATIC BALANCE (the centerpiece — protect an evening for it). Run this chapter's full workflow on your track, by the numbers: complete the mix-prep checklist (version save, bench check, routing audit, names, freeze, references in and level-matched, calibrated level, two-page notepad); write your genre-adjusted hierarchy; faders to silence; loop your busiest section; build in rank order with the fight protocol; mono-check at family milestones; top-to-bottom hands-off pass; translation lap (mono / whisper / hallway); save and stop. Deliverables: (1) the written hierarchy, (2) a level map sketch of your finished balance in the chapter's diagram style, (3) your ARRANGEMENT? page with every confession classified, (4) a bounce labeled static_v1, and (5) — next day, not tonight — three sentences from the fresh-ears listen. Time-box: 90 minutes. If you blow past it, write down why; the reason is diagnostic (secret processing, or a confessing arrangement).

C2. The routing audit. Before or as part of C1: verify every track's output reaches exactly one of your six family buses, and all six reach the 2-bus and nothing else does. Log every stray you catch (Jaylen caught two; most sessions hide at least one). Then prove the architecture works: play the chorus and perform a one-fader family balance — DRUMS bus down 3, up 3, back; VOX bus the same. Write one sentence on what bus-level moves let you hear that 34 individual faders never could.

C3. Reference import + level-match. Import your three references onto a dedicated lane routed around your 2-bus (straight to output). Level-match each by ear at calibrated volume: flip between ref and your session until no loudness jump remains, matching on the vocal and overall body. Document roughly how far down each ref fader ended up — and sit with what that gap is (mastering, Chapters 31–33; not a verdict on your mix). Then run one 30-second humility loop mid-C1 and log what one balance norm it corrected.

C4. The 80%-rule test. Gather three bounces of the same section of your song: (a) your pre-chapter rough (the plugin-era mix, if one exists), (b) your prebalance_instinct bounce from the Productive Struggle block, and (c) static_v1 from C1. Rename the files to A/B/C so the labels don't vote, wait a day, then listen blind at matched volume and rank them on exactly two questions: which sounds most like one song, and which moves you most. Write the verdict memo: what did 90 method-driven minutes buy over instinct, and what did faders-only buy over the plugin rough? (If the plugin rough wins, that's a real result too — figure out what it's doing that your balance isn't, and write it on the MIX NOTES page for the chapter that owns it.)

C5. The mono build. A second, shorter static balance — 25 minutes, a different song or a stripped copy of yours — built entirely in mono: sum the 2-bus before you start and leave it summed for the whole build. Then un-collapse to stereo and document the reveal: what improved for free? What surprised you? Most people report the stereo version feels like a reward they didn't have to earn — write down why that is, in this chapter's vocabulary.

C6. The bracketing drill (calibrating "too loud" and "too quiet"). Loop your chorus with your full static balance playing. Take the lead-vocal fader and find the edges: raise it until it's unambiguously too loud (the band turns into a backing track) and note the level; lower it until it's unambiguously buried and note that level. Now find the width of the window between the edges and set the vocal where the song wants it within that window. Repeat for the kick and for one piece of candy. The discovery worth writing down: how wide (or alarmingly narrow) each element's acceptable window is, and which element's window was narrowest — that one will need Chapter 23's help staying put, and now you know why.

C7. The confession hunt. Take your ARRANGEMENT? page from C1 and process it properly: for each entry, run the disguise test (mute/move experiments), classify the problem — arrangement / source / edit / genuinely mix — and execute every arrangement-class fix now with mute buttons and edits, exactly as Chapter 16 taught. Re-bounce as static_v2. Log what each executed confession changed about the balance ("with the second pad benched, the keys no longer fight the vocal and came up 2 dB"). Items classified "genuinely mix" get written on MIX NOTES with the chapter number that owns them. Nothing gets a plugin.

C8. The hierarchy swap. Rebuild a quick 20-minute static balance of your track with a deliberately different crown — if your real hierarchy is vocal-first, build kick-first as if it were an instrumental club record; if you're beat-first, build it vocal-up like a pop ballad. Bounce it. Compare against static_v1 and write three sentences: what genre does the swapped balance imply? What does that tell you about how much of "genre" (Chapter 18) is enforced at the faders? Which elements barely moved between the two builds — and what does that say about them?

Part D — Synthesis

D1. Pre-decided attention (short essay, ~300 words). Connect three ideas into one argument: the cocktail-party ability from Chapter 4 (your brain mixes live sound by steering attention), the fixed proportions of a stereo file, and this chapter's claim that a mix is pre-decided attention. End with what this implies about the mixer's responsibility during a chorus where four elements are competing — who decides, when, and on whose behalf?

D2. The postmortem. Choose one mix you finished before this book (everyone has one — the beat that died in a car, the song that never sounded right). Apply the diagnostic ladder retroactively: list its three biggest problems as you remember them, and classify each as arrangement / source / edit / mix. For each, name the chapter of this book where the real fix lived, and estimate where on the cost-curve you actually tried to fix it at the time. Close with the sentence you'd send your past self the week before they started that mix.

D3. The wall card. Design your personal static-balance checklist card — maximum twelve lines, meant to be taped where your monitors are. It must include: the silence rule, the hierarchy step, the fight protocol's three legal moves, the mono ritual, the too-quiet doctrine, and the time-box. Wording is yours; brevity is the assignment. (Compare yours against the master checklists in Appendix G after you've drafted it — not before.)

D4. Position memo: top-down or bottom-up? One page, written for a collaborator: which gravity does your genre and your working style pull you toward, what's the failure mode you're personally most at risk of (be honest — your C1 notes know), and what specific ritual from this chapter you'll use to counteract it. Cite one documented professional practice from Case Study 1 in support, with this book's honesty rules intact.

Part M — Mixed Practice

M1. (Chapters 4 + 20) A friend's mix has a problem you can hear immediately: the chorus turns into a wall where words become hard to follow. Using Chapter 4's band vocabulary and this chapter's framework, write the two-sentence diagnosis you'd send them — one sentence naming where (frequency region and likely culprits), one sentence telling them which stage to check first and why.

M2. (Chapters 3 + 20) Map the complete monitoring signal chain you mixed through in C1, gain stage by gain stage, Chapter 3 style: DAW fader → bus → 2-bus → interface D/A → monitor knob → speakers → room → ears. Then answer: why does the monitor knob change none of your balance decisions while the 2-bus fader could change all of them? Which stages in that chain are in the mix and which are around it?

M3. (Chapters 10 + 20) Pull out your room's lies list from Chapter 10 (and your headphone lies list from Chapter 8). For each documented lie, write the specific static-balance decision it could distort and the countermeasure you used (or should have used) in C1 — walk test, mono, whisper, hallway, second system. If you skipped a countermeasure for a lie you know you have, redo that balance decision tonight.

M4. (Chapters 13 + 16 + 20) Test the claim that upstream discipline buys downstream ease: open your session and temporarily un-mute two BENCH-folder parts from your Chapter 16 cut list, then try to find a static balance that accommodates them. Time how long before you hit an unsolvable fight. Re-bench them, and write two sentences connecting what you just experienced to (a) Chapter 16's mute-test doctrine and (b) this chapter's threshold concept.

M5. (Chapters 19 + 20) You've decided to hire an outside mixer for your next single. Based on Chapters 19 and 20 together, list exactly what you'd deliver — files, formats, documentation — and answer the new question this chapter raises: should your included reference mix be your old plugin rough or your static balance, and what does each one communicate to the mixer about your intentions? Which would Mike Senior's method suggest they'd rather receive, and why?