Chapter 39 Quiz
This is the capstone quiz, so it spans the entire pipeline — every question reaches back into the book the way release week will. Closed book first pass: answer everything before opening any <details> block. Misses here aren't failures; they're the most precise re-reading list you'll ever get, one chapter number per miss. Scoring guidance is at the end.
Section 1 — Multiple Choice (15 questions, 1 point each)
1. In this chapter's gate list, "release QA" specifically judges:
- A) whether the mix translates across playback systems
- B) whether the deliverable files are correct, complete, and verified
- C) whether the master is loud enough for the genre
- D) whether the arrangement supports the song
Answer
**B.** Release QA judges the *files*, not the music — musical judgment closed at Gates 1–4 (Chapters 30–33). It catches wrong uploads, corrupted bounces, mislabeled alts, and metadata that doesn't match the split sheet.2. The correct print spec for a mix headed to mastering (Chapter 31) is:
- A) 16-bit WAV, peaks at -0.1 dBFS, limiter engaged
- B) MP3 at 320 kbps, normalized
- C) 24-bit WAV, peaks around -6 dB, no limiter on the 2-bus
- D) 32-bit WAV, peaks at exactly -18 dBFS
Answer
**C.** 24-bit preserves the noise floor advantage, ~-6 dB of headroom is mastering's working room (reserved back in [Chapter 21](../../part-05-mixing-foundations/chapter-21-gain-staging/index.md)), and the limiter's job — loudness — belongs to the mastering stage, not the mix print.3. "Static Bloom" has no second full chorus before the double chorus at 2:30. The walkthrough presents this as the record's boldest example of:
- A) genre compliance
- B) arrangement by subtraction — withholding the payoff so its final statement owns the record
- C) a mixing decision made with automation
- D) a limitation of the session's track count
Answer
**B.** [Chapter 16](../../part-04-arrangement-production/chapter-16-arrangement/index.md)'s deepest move: contrast is the engine, and the rarest payoff is the biggest. It's theme T2 (the professional subtracts) operating at the structural level.4. Why does the gate list check metadata against the split sheet rather than against memory?
- A) memory is acceptable if the release is a solo project
- B) the split sheet is the signed source of truth that royalties will follow, and documents check documents
- C) distributors require a photo of the split sheet
- D) the split sheet contains the loudness targets
Answer
**B.** [Chapter 36](../../part-08-music-business/chapter-36-copyright-licensing-royalties/index.md)'s doctrine completed: the signed split document is what the money follows, and the metadata must mirror it exactly — name by name, percentage by percentage.5. A master at -8 LUFS integrated and a master at -11 LUFS integrated are both streamed on a platform normalizing to roughly -14 LUFS. At playback, the listener hears:
- A) the -8 master noticeably louder
- B) both at approximately the same loudness, with the -8 master keeping less of its dynamics
- C) the -11 master distorting
- D) no difference of any kind
Answer
**B.** Normalization levels the playback field ([Chapter 33](../../part-07-mastering/chapter-33-loudness-wars-streaming/index.md)'s threshold concept) — absolute loudness differences vanish, but the dynamic cost paid to reach -8 stays in the waveform forever.6. The "one decision" the walkthrough assigns to the recording stage (Chapters 11–12) is:
- A) buying the most neutral microphone available
- B) recording every part at least ten times
- C) performance over perfection — full takes, never clip a keeper, let the unguarded take win
- D) recording everything in stereo for safety
Answer
**C.** The gravy take — take six, loose and a little reckless — won half of Demi's comp. Technique exists to serve the performance, and the capture disciplines (locked position, untouched gain) are what made the loose take usable.7. In the Whole Signal Chain diagram, the two stages the producer cannot control are:
- A) the DAW and the master
- B) the listener's playback system and the listener's room
- C) the microphone and the preamp
- D) the distributor and the split sheet
Answer
**B.** Everything from source to platform is yours; the playback hardware and the room it fires into are theirs. Chapters 30 (translation testing) and 33 (normalization) exist to make your work survive those two uncontrolled stages.8. The version-2 list exists primarily to:
- A) document bugs for the mastering engineer
- B) give post-release "I should have" observations a destination other than the finished master
- C) track which plugins were used
- D) plan the deluxe edition
Answer
**B.** Growth observations are scheduled onto the *next* track instead of reopening a record that passes its gates — [Chapter 31](../../part-07-mastering/chapter-31-what-is-mastering/index.md)'s revision discipline extended across a career. It's how "done beats perfect" stays honest.9. Which sequence states the four mix passes (Chapters 22–25) in the order the book runs them?
- A) compression → EQ → width → space
- B) EQ → compression → space → width
- C) space → width → EQ → compression
- D) width → space → compression → EQ
Answer
**B.** Carve the frequency real estate first (EQ), control behavior second (compression), then place sounds front-to-back (space) and left-to-right (width) — each pass standing on the one before, all of it on the [Chapter 2](../../part-01-sound-fundamentals/chapter-02-digital-audio/index.md)0–21 foundation.10. The chapter's reasoning for the four-week release lead time is:
- A) distributors legally require it
- B) editorial-pitch windows and pre-save mechanics need runway, and day-of uploads forfeit both
- C) masters need four weeks to "settle"
- D) it's an arbitrary tradition
Answer
**B.** [Chapter 35](../../part-08-music-business/chapter-35-distribution/index.md)'s doctrine: playlist pitching happens before release in editorial windows, and a campaign ([Chapter 37](../../part-08-music-business/chapter-37-building-an-audience/index.md)) needs a runway to run on. The lead time is plumbing reality, not superstition.11. The kick on "Static Bloom" shipped with no compressor because:
- A) kicks should never be compressed
- B) the bypass comparison won at matched loudness — the absence beat the presence
- C) the CPU budget ran out
- D) compression is only for vocals
Answer
**B.** [Chapter 23](../../part-05-mixing-foundations/chapter-23-compression/index.md)'s quiet lesson: a processor must beat its own bypass at matched loudness or the bypass wins by default. Deleting is a decision; "no rules, only consequences" cuts both ways.12. Why does the walkthrough credit the $80 room treatment (Chapter 10) as a prerequisite for nearly every later stage?
- A) treatment makes the room look professional on camera
- B) the room is part of the monitoring chain — untreated, it lies to every decision made through it
- C) rockwool improves microphone frequency response
- D) treatment is required by streaming platforms
Answer
**B.** [Chapter 10](../../part-02-tools-of-production/chapter-10-room-acoustics/index.md)'s threshold concept: you mix what your room lets you hear. Jaylen's chair sat in a null that hid his own 808s — every downstream decision inherits the room's honesty or its lies.13. The post-release week's "analytics without obsession" discipline prescribes:
- A) hourly checks for the first 48 hours
- B) two checks in week one (around day three and day seven), watching saves/completion/source rather than raw plays
- C) ignoring all data forever
- D) checking only the raw play count
Answer
**B.** [Chapter 37](../../part-08-music-business/chapter-37-building-an-audience/index.md)'s metrics literacy applied with a calendar: meaningful signals over vanity counts, on a schedule that protects the only resource that matters post-release — momentum toward the next track.14. The split sheet for "Static Bloom" was signed when the song was worth zero dollars because:
- A) lawyers were cheaper that month
- B) splits are easiest to agree before money exists and hardest after it arrives
- C) the distributor demanded it
- D) Demi and Theo were in the same room anyway
Answer
**B.** [Chapter 36](../../part-08-music-business/chapter-36-copyright-licensing-royalties/index.md)'s friendship-insurance doctrine: ten slightly awkward minutes before release prevents the relationship-ending dispute after the royalties flow. Splits before money — in that order, always.15. The AI audit (Chapter 38) concluded that this book's knowledge matters in an AI-tool era because:
- A) AI tools are all marketing hype with no real capability
- B) evaluating any tool's output requires the diagnostic vocabulary and trained ears the tools don't supply
- C) AI tools are prohibited by distributors
- D) AI masters always sound worse
Answer
**B.** The clear-eyed position: some tools are genuinely good (the blind A/B was uncomfortable for a reason), and the differentiator is the evaluation function — ears, vocabulary, and intent. Tools democratize; knowledge differentiates.Section 2 — True/False + Justify (5 questions, 2 points each: 1 for the verdict, 1 for the mechanism)
16. True or false: Once the master passes Gate 4, finding three things you'd change during release week means the release should be delayed.
Answer
**False.** Growth observations are permanent — your ears improve faster than any single track can chase, so the gap never closes. The gate question decides: if the track still passes every gate with the flaw in it, the observation goes on the version-2 list and the release proceeds. Delay is only correct for an actual gate failure.17. True or false: Release QA should include playing every deliverable file top to tail, even though you've heard the song hundreds of times.
Answer
**True.** You've heard the *song*; you haven't verified these *files* — and the most expensive release errors (corrupted bounce, wrong revision, instrumental with a stray ad-lib at 2:51, truncated tail) live precisely in the gap between those two. Familiarity is why file errors survive: you hear your memory, not the audio ([Chapter 31](../../part-07-mastering/chapter-31-what-is-mastering/index.md)'s proofreader logic).18. True or false: The walkthrough's stage order is also the strict calendar order in which "Static Bloom" was actually built.
Answer
**False.** The book taught capture (Chapters 11–12) before collaboration ([Chapter 19](../../part-04-arrangement-production/chapter-19-collaboration-workflow/index.md)), but in calendar time Demi's vocal and Theo's guitar were recorded *after* the Loopline collaboration began — the techniques were taught in pipeline order, then executed when the story reached them (both chapters flagged this honestly). Case Study 1's logbook restores true chronology; pipelines describe dependency order, not always date order.19. True or false: Normalization means the loudness war's casualties (crushed dynamics) are automatically repaired at playback.
Answer
**False.** Normalization only changes playback *level* — a turn-down. Relative dynamics survive; destroyed ones stay destroyed. The platform levels the field, which removes the *reward* for slamming, but it cannot give a flattened master its transients back ([Chapter 33](../../part-07-mastering/chapter-33-loudness-wars-streaming/index.md)). That's why the three-master experiment's slammed build lost.20. True or false: For the podcaster reading this book, the release gates mostly don't apply.
Answer
**False.** The gates compress but don't disappear: no mastering hire or DSP waterfall, but release QA (files verified, episode art, metadata), the loudness gate (-16 LUFS stereo convention, measured, as of this writing), and the next-one rule (the published schedule) are identical in kind. Aisha's whole arc is the gate list, applied twice weekly.Section 3 — Short Answer (4 questions, 3 points each)
21. Define the deliverables package and list at least six of its contents. Then explain, in one sentence, why its position in the signal chain (the boundary between your studio and the business rails) dictates its completeness standard.
Answer
The deliverables package is the complete, self-contained folder that leaves your studio: final master WAV(s); alternate versions (instrumental, clean, acapella if promised); the metadata document (ISRC/UPC, writer/producer credits matching the split sheet); artwork at spec; lyrics; archived stems and session backup. Position dictates standard because it's the last artifact you fully control — every downstream party (distributor, sync supervisor, remixer, future-you) draws from it, so nothing after it can be assumed or reconstructed cheaply.22. State the next-song rule precisely (the action, the deadline, and what counts as compliance), and give the chapter's reasoning for why it protects you in both the good-numbers and the quiet-numbers post-release scenarios.
Answer
Start the next track within fourteen days of release — "start" meaning a new session created and at least one real decision made (not a finished demo). Good numbers tempt dashboard-watching; quiet numbers tempt identity renegotiation; both are cured by being mid-project, because momentum is the one tool that can't be bought and depreciates fastest. The catalog ([Chapter 37](../../part-08-music-business/chapter-37-building-an-audience/index.md): career = catalog × audience × time) only grows one way.23. A friend wants to skip Gate 0 ("the song's been done for months — why re-check the concept?"). Give the two-part answer: what Gate 0 actually verifies, and the most common release regret it exists to prevent.
Answer
Gate 0 verifies that the finished record still honors the manifesto ([Chapter 5](../../part-01-sound-fundamentals/chapter-05-history-of-recording/index.md)) and that every arrangement element survived a real defense ([Chapter 16](../../part-04-arrangement-production/chapter-16-arrangement/index.md)'s mute-test logic) — that the track is the *song* you meant, not just a well-engineered file. It prevents the most common non-technical regret: shipping a track whose parts were never individually justified, discovering after release that the second verse everyone skips was the one you never defended.24. Explain why the chapter places the measured loudness numbers (integrated LUFS, true peak) in the project notes at Gate 4, rather than trusting that the master "sounded right." Name the two failure modes the written numbers catch.
Answer
Because "sounded right" is unfalsifiable and unportable — a number is evidence, comparable across versions and time. The written numbers catch: (1) true-peak overs that sample-peak meters miss (inter-sample peaks that turn spitty after lossy encoding — [Chapter 32](../../part-07-mastering/chapter-32-mastering-tools-techniques/index.md)'s -1.0 dBTP ceiling); and (2) accidental re-render drift — a later bounce from a changed session quietly shipping at a different loudness than the approved master. Numbers also let you verify the platform encode later against a known baseline.Section 4 — Applied Scenario (6 points)
25. The full-pipeline triage. A producer friend sends you a panicked message one week before their planned release date. The symptoms, verbatim: "(a) The mix sounds amazing at my desk but the chorus turns to mush in my car. (b) I mastered it last night to -7.5 LUFS because a YouTube video said competitive. (c) My collaborator just noticed she isn't in the writer credits I submitted. (d) I haven't posted anything about the release yet — I was waiting until it's out. (e) Also, honestly, I keep finding little things I want to fix and I'm wondering if I should push the date."
Triage all five. For each: name the gate it fails (or the discipline it violates), the chapter that treats it, the concrete fix, and — this is the test — the correct order in which to handle them, with one sentence justifying your sequence. Finish with the honest call: does this release date survive, and under what condition?
Answer
**Order: (c) → (a) → (b) → (e) → (d).** **(c) Credits — Gate 6, [Chapter 36](../../part-08-music-business/chapter-36-copyright-licensing-royalties/index.md)/35.** First, because it's a rights-and-relationship failure that gets harder to fix the closer money and publication get: correct the metadata against a signed split agreement *now*, before anything goes live. Documents check documents. **(a) Car mush — Gate 1, [Chapter 30](../../part-06-advanced-mixing/chapter-30-mix-troubleshooting/index.md) (and 22/20 underneath).** Second, because everything downstream (the master) is built on the mix: run the symptom table — chorus mush is classically a 200–400 Hz committee and/or arrangement density; diagnose on the car, fix at the desk one change at a time, re-verify across the fleet. The mastering must be redone afterward anyway, which makes (b) free to fix. **(b) The -7.5 master — Gates 3/4, Chapters 32–33.** Re-master from the corrected mix print: matched-loudness referencing, limiting in stages, "better or just louder?" at each step, ceiling -1.0 dBTP, measure and write the numbers. Normalization will erase the -7.5's loudness advantage and keep its damage — the YouTube number is chasing a war that's over. **(e) The little things — this chapter's quality bar.** Apply the gate question to each: gate failures get fixed in the passes above; everything else goes on the version-2 list, in writing. "Push the date" is only legitimate if gates fail — and some just did, so see below. **(d) No campaign — Gate 8, [Chapter 37](../../part-08-music-business/chapter-37-building-an-audience/index.md) (and 35's lead time).** Last in fix-order but it decides the date: with one week and no runway, the editorial-pitch window is already gone. Build the short version: pre-save now, personal sends list, a week of content from production artifacts. **The honest call:** the date survives *only if* the mix fix and re-master complete with a real next-day listen inside the week — rushed gates are failed gates. The professional move, given (a)+(b)+(d) together: slide the release two to four weeks (the distributor makes this easy pre-release), run the gates properly, and use the recovered lead time to run an actual campaign. Done beats perfect — but done means the gates passed, and a week of triage is how releases ship broken.Scoring
| Section | Points available |
|---|---|
| Multiple choice (1–15) | 15 |
| True/False + justify (16–20) | 10 |
| Short answer (21–24) | 12 |
| Applied scenario (25) | 6 |
| Total | 43 |
36–43: Release-ready — your understanding spans the pipeline; ship, and trust your gates. 28–35: Solid — re-read the chapters behind your specific misses before upload week; the gate list will cover the rest. 18–27: The walkthrough table is your friend: re-walk the stages where you dropped points, with your own project open. Below 18: Good news — this is the one chapter that's an index to every other chapter, so your misses just wrote your personalized re-reading plan. The gates will still be here when you're back.