Chapter 20 Quiz
Closed book first pass — answer everything before opening any <details> block. This is the gateway chapter to Parts V and VI, so treat misses seriously: every tool chapter ahead assumes these ideas are load-bearing. Scoring guidance is at the end.
Section 1 — Multiple Choice (15 questions, 1 point each)
1. The single word that turns "tracks at whatever levels they ended up at" into a mix is: - A) processed - B) loud - C) deliberate - D) wide
Answer
**C.** A session always has levels, places, and roles — by accident. A mix exists when every audible element is where it is on purpose, and the decisions agree about what the song is.2. The four jobs of a mix, per this chapter, are: - A) EQ, compression, reverb, automation - B) balance, space, clarity, interest - C) tracking, editing, arranging, mastering - D) level, pan, mute, solo
Answer
**B.** Balance (relative levels), space (where elements live, front to back), clarity (everything audible in its moment), interest (movement and color). The tools in option A are means; the jobs in B are the ends.3. A static mix is: - A) a mix with no stereo information - B) a mix where every fader is set to one deliberate level, with no automation - C) a mix printed without mastering - D) a rough mix made before editing
Answer
**B.** One deliberate level per element, no movement yet — the resting state that automation ([Chapter 27](../../part-06-advanced-mixing/chapter-27-automation/index.md)) will later deviate from and return to. A stage, not a style.4. The static balance begins from total silence rather than from the faders' current positions because: - A) silence resets the DAW's pan law - B) it's faster - C) every level then exists because you chose it, instead of inheriting months of accidents - D) plugins only work correctly from zeroed faders
Answer
**C.** Production faders are a recency-and-affection map, not a song. Starting from silence converts every level from an accident into a decision.5. In the most-important-element-first build, the question you ask as each new fader comes up is: - A) "Does this sound good?" - B) "Is this at the same level as in the reference?" - C) "Is the relationship right — can I still hear everything that matters more than this?" - D) "Is this peaking below the top of the meter?"
Answer
**C.** "Sounds good" is unanswerable (everything sounds good loud); the relationship to the already-balanced, higher-ranked elements is the only question a balance decision can actually answer.6. "When in doubt, too quiet beats too loud" is justified by an asymmetry. Which one? - A) Quiet errors save headroom for mastering - B) Holes announce themselves quickly; smears hide behind adaptation while degrading everything underneath - C) Quiet elements use less CPU - D) Loud errors can be fixed by the limiter
Answer
**B.** A too-quiet element leaves an audible hole you'll fix in minutes; a too-loud element masks what's beneath it, your ears adapt within a chorus, and the error stops telling on itself. Err toward the error that confesses.7. Your chorus is cluttered. The "disguise test" from the threshold concept says your first experiment is: - A) a high-pass filter on everything - B) muting suspect parts to see whether the song stops needing them - C) widening the stereo image to create room - D) turning the whole mix down
Answer
**B.** If muting fixes it, it was an arrangement problem wearing a mix costume — the fix is the mute button, not a processor. Only what survives the mute test (and a source/edit check) is genuinely mix work.8. Mono summing is the worst case for clarity because it removes: - A) low frequencies - B) the level differences between tracks - C) the interaural cues that give clashing elements spatial release from masking - D) reverb tails
Answer
**C.** Stereo position lets the brain separate competing elements into streams (spatial release from masking). Mono deletes the positional differences, masking returns at full strength, and any balance war stereo was hiding becomes audible.9. The mixer's hierarchy primarily governs: - A) which element is loudest at all times - B) which element yields when two elements collide - C) the order tracks appear in the session - D) which elements receive processing first in Part VI
Answer
**B.** It's a collision rule, not a volume chart — the bass can be enormous and still yield to the vocal when they fight. Writing the hierarchy in advance pre-decides every fight's loser.10. At mix time, routing 34 tracks into 6 family buses buys you, above all: - A) lower CPU usage - B) automatic gain staging - C) family-level balance moves — six decisions where the big proportions live, instead of thirty-four - D) louder playback
Answer
**C.** Most of mixing is family-level questions ("are the drums as a whole too loud against the vocal?"), and the bus fader is the one control that can answer them. Shared processing and free stems are later bonuses.11. Top-down mixing means: - A) starting with the most important track and working down the hierarchy - B) starting with broad whole-mix and bus-level moves, descending into tracks only where needed - C) mixing the song from the intro to the outro in order - D) setting the master fader first
Answer
**B.** Top-down = whole picture first. (Option A describes the most-important-first *build order* within a static balance — a different axis, commonly confused with it.)12. When level-matching a commercial reference against your unmixed session, you pull the reference down to your mix's level because: - A) the reference is mastered (loudness-maximized), and any loudness mismatch — plus louder-sounds-better bias — rigs the comparison - B) streaming services require it - C) your mix must stay below -18 dBFS at all times - D) references sound worse loud
Answer
**A.** The ref has been through limiting and loudness maximization (Chapters 31–33); raw comparison is dishonest, and [Chapter 4](../../part-01-sound-fundamentals/chapter-04-listening/index.md) taught you that louder wins automatically. Turning your mix up instead would wreck your gain structure to win a rigged contest.13. The "80% rule" — most of a great mix is the balance — is best understood as: - A) a measured statistic from mixing research - B) folklore with a real spine: the number is a sermon, but balance genuinely determines whether the mix works - C) a rule about how much headroom to leave - D) obsolete advice from the console era
Answer
**B.** Nobody has weighed balance against processing on a scale; the wobbling number encodes generations of professionals finding that the static balance decides whether a mix works and processing decides how finished it feels.14. "Fix it in the mix" became a slur because deferred decisions: - A) violate copyright - B) cost more at every later stage, buy progressively worse versions of the fix, and compound with each other - C) are forbidden by streaming platforms - D) only matter on analog consoles
Answer
**B.** The cost curve only bends one way: free at the performance/placement stage, an afternoon at editing, a tradeoff at mixing, a casualty list at mastering — and deferred problems interact, so you end up processing your processing.15. Which of these is something a mix genuinely CANNOT fix? - A) a wandering vocal level - B) a dull-sounding placement that never captured the source's presence - C) hat candy crowding the snare - D) a chorus that needs the pad tucked 3 dB
Answer
**B.** You can't sculpt what isn't in the file — that's a capture-stage failure (Chapters 7, 11–12). The others are level/dynamics work squarely inside the mix's powers.Section 2 — True / False (justify your answer, 2 points each)
16. A static mix contains no automation.
Answer
**True.** "Static" means every element holds one deliberate level — the resting state. Movement is [Chapter 27](../../part-06-advanced-mixing/chapter-27-automation/index.md)'s job, and it only means something relative to this baseline. (Full credit requires saying *why* the baseline matters, not just the definition.)17. If an element can't be heard clearly, the correct first move is EQ.
Answer
**False.** The diagnostic ladder runs arrangement → source → edit → mix, cheapest first: try the fader and the mute test before any processor. Most audibility problems are level relationships or arrangement collisions in disguise; EQ ([Chapter 22](../chapter-22-eq/index.md)) is for what survives those checks.18. Mono compatibility stopped mattering once stereo playback became universal.
Answer
**False.** Phone speakers, single-driver Bluetooth and smart speakers, summed club/PA low end, store systems, and distant in-room listening all collapse stereo toward mono today. And diagnostically, mono is the stress test that exposes masking that stereo placement hides — useful even if every listener owned perfect speakers.19. Building the static balance in the song's busiest section is preferred because a balance that survives maximum density works everywhere.
Answer
**True.** Rush hour is the stress test; sparse sections are easy cases verified afterward in the top-to-bottom pass. The reverse order — building in the sparse intro — produces balances that collapse when traffic arrives.20. In the fight protocol, when a newly added element buries a more important one, reaching for a plugin is one of your three legal moves.
Answer
**False.** The three legal moves are: new element down; buried element up (if the hierarchy agrees); or the collision goes to the ARRANGEMENT? page. Plugins are explicitly illegal at this stage — every fight settled by fader or arrangement now is surgery Chapters 22–25 don't have to perform.Section 3 — Short Answer (4 questions, 3 points each)
21. State the threshold concept, then retell the Chapter 16 banjo situation in its terms: what was asked for, what was actually wrong, what the fix turned out to be, and what the "disguise" consisted of.
Answer
*A mix problem is usually an arrangement problem wearing a disguise.* Demi asked for a mix fix — "make the banjos clearer" — for what was an arrangement wound: seven parts in one register all playing at once. No fader or tone move could fit them; the fix was the mute button (six benched, one counter-melody kept). The disguise: a *when* problem (too many parts at the same time) presenting as a *how-loud* problem.22. Give two setup rules for bringing reference tracks into your mix session, and the reason behind each.
Answer
(1) Route the ref lane *around* the 2-bus, straight to the output — so future mix-bus processing never touches the references. (2) Level-match by pulling the ref *down* to the mix — because the ref is mastered and louder automatically sounds better, so an unmatched comparison is rigged; matching downward keeps your own gain structure intact.23. Why does the chapter route risers, impacts, and textures to an FX bus, and how is that different from the send/return "spaces" arriving in Chapter 24? (Chapter 6's routing vocabulary will help.)
Answer
The FX bus is a family bus: those tracks are *printed sound-design elements* whose entire signal flows through it, like drums through DRUMS — giving them one family fader and meter. [Chapter 24](../chapter-24-reverb-delay/index.md)'s reverbs/delays will live on *returns*: lanes that receive *copies* of other tracks via sends, blending a wet signal alongside the dry originals. Same destination (the 2-bus), different plumbing — full signal versus sent copy.24. Your static balance is finished and it doesn't move you. Per the chapter, what are the two most likely diagnoses, and why is "add processing" not one of them?
Answer
Either the balance is wrong (rebuild — it's ninety minutes, and the hierarchy may have crowned the wrong thing) or the problem is upstream — arrangement confessions not yet executed, or a song that needs another Part III–IV pass. Processing isn't a diagnosis because tools refine a balance's finish; they can't supply the conviction faders couldn't find — the balance is the cheapest, least flattering test of whether the song works.Section 4 — Applied Scenario (1 question, 6 points)
25. A friend sends you this message with their session: "My mix sucks and I don't know why. The verse is fine but the chorus turns to soup — I've EQ'd everything twice. The lead vocal disappears unless I make it weirdly loud. There are two pads, a piano, rhythm guitar, and a synth lead all playing in the chorus. Also the whole thing sounds amazing on my headphones but tiny on my phone. I think I need better plugins." Write your response as: (a) a diagnosis of each named symptom using this chapter's framework, (b) the order of operations you'd prescribe, and (c) one sentence about the plugin theory.
Answer
**(a)** Chorus soup + vocal that only works "weirdly loud" + five sustained mid-register parts at once = the threshold concept in action: an arrangement problem (overbooked stage) wearing a mix costume — no level can fit two pads, piano, guitar, and lead simultaneously, so EQ'ing everything twice was surgery on the wrong patient. "Amazing on headphones, tiny on phone" = a balance/arrangement that leans on stereo separation and low-end the phone can't reproduce — a mono-compatibility failure the phone speaker is reporting honestly. **(b)** Order of operations: (1) run the disguise test — mute pads/piano in the chorus until the vocal sits at a sane level; bench or relocate parts per the [Chapter 16](../../part-04-arrangement-production/chapter-16-arrangement/index.md) mute test (most likely: the parts take turns, not the stage at once); (2) strip the EQ experiments, faders to silence, and build a proper static balance from a written hierarchy, busiest section first; (3) mono-check while building (truth serum — the phone already told you this mix fails it); (4) only what survives all that goes on a MIX NOTES list for the actual tool chapters. **(c)** The plugins aren't the problem and better ones won't help: faders and mute buttons haven't been given their turn yet, and they're the only tools that can fix what's actually wrong. **(Scoring: 2 points for correctly classifying the soup as arrangement-in-disguise; 2 for a sane cheapest-first order of operations; 1 for the mono/phone connection; 1 for the plugin verdict.)**Scoring
| Section | Points available |
|---|---|
| 1 — Multiple choice | 15 |
| 2 — True/false + justification | 10 |
| 3 — Short answer | 12 |
| 4 — Applied scenario | 6 |
| Total | 43 |
| Score | Reading |
|---|---|
| 38–43 | Solid. You know what mixing is — now go prove it with C1's ninety minutes. |
| 30–37 | Good foundation; re-read the threshold block and the static-balance steps behind your misses (the hierarchy-as-collision-rule and the mono mechanism are the usual wobbles). |
| 22–29 | Re-do exercises B1, B3, and C1 with the chapter open — this chapter's ideas stick through faders, not flashcards. |
| below 22 | No verdict on you, only on the route: re-read with your own session open and the faders down, then retake in two days. The static balance will teach you the chapter faster than the chapter will. |
For T/F items, award the second point only if the justification names the mechanism (adaptation asymmetry, spatial release from masking, the diagnostic ladder, the resting-state logic) — not merely the verdict.