Chapter 33 Quiz

Closed book, honest effort. Every confusion you catch here is one that won't end up in a forum post with your name on it. Score yourself with the table at the end. Platform specifics in this quiz are "as of this writing" by definition — grade the reasoning, not the weather.

Multiple Choice

1. LUFS differs from dBFS because LUFS measures: A) the same thing, with a gate added B) the highest reconstructed peak rather than the highest sample C) perceived loudness of a program — ear-weighted, averaged over time, gated — rather than a sample's distance from digital full scale D) acoustic pressure in the listening room

Answer **C.** dBFS is a peak/headroom fact about samples in a file; LUFS describes how loud a whole program reads to ears — K-weighted, energy-averaged, gated. A describes neither correctly; B describes dBTP; D describes dB SPL ([Chapter 1](../../part-01-sound-fundamentals/chapter-01-what-is-sound/index.md)). The four-unit table exists because these get conflated constantly — Appendix B keeps the map.

2. The integrated (I) reading on your meter is valid: A) any time the meter has been running for at least 3 seconds B) only after the entire program has played through the meter (or been analyzed whole-file offline) C) only when the song is playing its loudest section D) once momentary and short-term agree

Answer **B.** Integrated is a whole-program measurement with gating; mid-song it's a number still under construction. Short-term needs 3 seconds (A confuses the windows); C and D describe nothing in the standard.

3. The relative gate in the integrated measurement exists primarily to: A) remove inter-sample overs from the average B) prevent passages far quieter than the program's body — long fades, ambient intros — from diluting the number (and to close the pad-it-with-silence loophole) C) make quiet songs measure louder so they get turned up D) filter out frequencies the ear can't hear

Answer **B.** After the absolute gate (-70 LUFS) removes silence, the relative gate re-averages without anything more than 10 LU below the provisional average — so integrated describes the body of the program, and silence-padding can't game it. A is true-peak territory; D is K-weighting's job, loosely; C inverts the purpose.

4. Your sample-peak meter shows -0.3 dBFS, but the file crackles after lossy encoding. The likely culprit and fix: A) the file's bit depth is too low; dither it B) inter-sample overs — reconstructed/encoded peaks exceeding the sample peaks; re-limit with a -1.0 dBTP ceiling, true-peak detection on C) the platform re-compressed the file; nothing can be done D) the meter is broken; trust your converters

Answer **B.** The reconstructed wave bulges between samples ([Chapter 2](../../part-01-sound-fundamentals/chapter-02-digital-audio/index.md)'s not-stairsteps fact), and lossy encoders overshoot further on hot material — clipping a sample-peak meter never saw. The decibel of true-peak margin is the standing fix. A is unrelated; C blames the robot for the file's own ceiling.

5. With normalization on, a platform plays your -9.0 LUFS master. What does it do, mechanically? A) re-limits the file to its reference loudness B) applies one static gain offset (here, roughly -5 dB against a ≈ -14 reference) to the whole track at playback C) compresses the loudest sections until the average hits the reference D) re-encodes the file at a lower bitrate

Answer **B.** Normalization is a per-track volume offset computed from the measured integrated loudness — the robot reaching for the volume knob. It is not dynamics processing (A, C) and has nothing to do with bitrate (D). The one hedged exception: some platforms apply protective limiting *when boosting quiet tracks*, never as part of an ordinary turn-down.

6. Which of these survives normalization completely unchanged? A) the track's absolute playback level B) the track's competitive loudness advantage over its playlist neighbors C) everything inside the file — PLR, transients, sectional dynamics, tone, and any limiting damage D) nothing; normalization alters the audio data

Answer **C.** The offset changes the level the file plays at; the file itself is delivered as printed — punch intact if you kept it, damage intact if you printed it. A is the one thing that changes; B is the war's confiscated prize; D is the forum myth this chapter exists to kill.

7. The loudness war's core engine was: A) record executives' poor hearing B) the equal-loudness effect making louder sound better on every unmatched comparison — and nobody being able to afford losing first listens C) vinyl's physical limitations D) a shortage of skilled mastering engineers

Answer **B.** Louder delivers more perceived bass and treble for free ([Chapter 4](../../part-01-sound-fundamentals/chapter-04-listening/index.md)), every career-deciding comparison was unmatched, and a quieter record sounded broken next to loud neighbors — so escalation was individually rational and collectively ruinous. C is backwards (vinyl's vetoes *restrained* the war; the CD removed them).

8. The Death Magnetic episode mattered because: A) it was the first loud album B) fans preferred the louder version, proving the war's point C) the same songs shipped in two public versions differing only in loudness treatment — and ordinary listeners could hear, and measure, the cost D) it triggered an immediate official remaster

Answer **C.** The Guitar Hero stems skipped the final loudness treatment, giving the world a controlled A/B with every variable held except the slam — and the fan response (the petition, the engineer's own published distancing) proved civilians hear the damage. B inverts the verdict; D never happened (no remaster was issued, as of this writing).

9. EBU R128's broadcast reference is -23 LUFS integrated. Streaming references cluster around -14 to -16. The reason broadcast runs quieter is: A) broadcast equipment can't handle higher levels B) broadcast carries whisper-to-explosion program with dialogue intelligibility paramount, and standardized generous headroom for it C) regulators picked the number at random D) older listeners prefer quieter audio

Answer **B.** The number suits the medium's dynamics needs. The architecture — measure like an ear, pick one reference, normalize — matters more than any specific value, which is exactly why streaming could borrow the measurement and choose different references.

10. A master measures -1.0 dBTP true peak and -13.5 LUFS integrated. Its PLR is: A) 14.5 dB B) 12.5 dB C) -14.5 dB D) impossible to compute without the LRA

Answer **B.** PLR = true peak − integrated = -1.0 − (-13.5) = 12.5 dB — a healthy, dynamic master, in the neighborhood this chapter mapped for dynamic rock/indie/folk. A subtracts in the wrong direction conceptually (and gets lucky-looking); D confuses the two dynamics statistics.

11. "Master to exactly -14 LUFS because that's Spotify's number" is wrong primarily because: A) Spotify's reference is actually -23 LUFS B) the reference is a playback level, not a delivery spec — and deliberately under-shooting your genre's density culture has real costs while "not being touched" by a volume offset buys nothing C) -14 is too loud for any genre D) LUFS can't be measured accurately enough to hit a target

Answer **B.** Nothing requires -14; the offset changes nothing inside the file, so avoiding it has no sonic benefit; and chasing the number can cost density that is part of a genre's sound — plus level in contexts that never turn quiet tracks up. The number is an outcome you sanity-check, not a target you chase.

12. The podcast delivery convention this chapter gives Aisha, as of this writing: A) ≈ -23 LUFS integrated, -3 dBTP B) ≈ -8 LUFS integrated, 0 dBFS ceiling C) ≈ -16 LUFS integrated stereo (≈ -19 mono), true peak ≤ -1 dBTP, segments within about 1 LU short-term D) whatever each episode's music bed measures

Answer **C.** The mid-teens convention with the standard ceiling, plus the rule that outranks the integers: consistency — episode to episode and voice to voice. A is European broadcast; B is a war crime against spoken word.

13. A listener plays Glass Hours as an album on a service with album normalization (as of this writing). What happens to Jaylen's Chapter 32 level map ("Glovebox" deliberately 1.5 dB inside the anchor)? A) every track is normalized to the reference individually, flattening the map B) one offset is applied to the whole album, so the track-to-track relationships survive exactly as sequenced C) the quietest track is turned up to match the loudest D) the level map is re-created by the platform's algorithm

Answer **B.** Album-mode normalization computes a single offset for the record, preserving sequencing craft. In playlists/shuffle it's track-by-track (A describes that mode), where each track stands alone at the reference — and the dynamic quiet track gives up nothing there either.

14. The turn-up asymmetry: platforms turn loud masters down reliably but treat quiet masters inconsistently because: A) turning down is computationally free and safe, while turning up risks clipping the ceiling — so platforms either decline or boost behind a protective limiter B) quiet masters are rare C) copyright law prohibits amplification D) loud masters are flagged as errors

Answer **A.** Attenuation can't clip; gain can — so the conservative behavior (YouTube-style, as of this writing) is to leave quiet tracks quiet, and the aggressive behavior boosts through a limiter the artist never approved. This asymmetry is why "master very quiet, the platform will fix it" fails in both directions.

15. K-weighting, in one honest sentence, is: A) a compression curve applied before limiting B) an ear-shaped filter applied before energy averaging — de-emphasizing deep lows, leaning into upper mids — so the measurement weighs the spectrum roughly the way hearing does C) the gate that removes silence D) a loudness penalty applied to bass-heavy genres

Answer **B.** It's step one of the LUFS recipe: filter like an ear, then average, then gate. C is a different stage of the same recipe; D is a conspiracy theory version of B.

True/False — with Justification

16. T/F: Normalization re-compresses your master to make it fit the platform's reference.

Answer **False.** Normalization is a static gain offset — one volume move for the whole track, computed from measured integrated loudness. No dynamics processing occurs on a turn-down. The single hedged exception: some platforms apply protective limiting when *boosting* quiet tracks on certain settings — which is an argument for not relying on being turned up, not evidence that normalization compresses.

17. T/F: A 40-second near-silent ambient intro will drag your song's integrated loudness down and cause the platform to mis-level the loud body of the track.

Answer **False.** The gate exists for exactly this: the absolute gate discards silence, and the relative gate discards passages far below the program's provisional average — so the body of the song sets the integrated number and the dramatic intro costs you nothing. Arrange freely; the meter has heard a fade before.

18. T/F: Two masters with identical sample-peak readings can differ enormously in loudness.

Answer **True.** Peak and loudness are nearly strangers ([Chapter 21](../../part-05-mixing-foundations/chapter-21-gain-staging/index.md)'s lesson, formalized here): loudness lives in the average energy of the body, and the gap between peak and loudness — PLR — is precisely the dynamics this chapter taught you to measure. Identical ceilings, wildly different floors.

19. T/F: When a platform turns a slammed master down, the turn-down itself is what makes it sound worse than a dynamic master at the same playback loudness.

Answer **False — and the distinction is the chapter.** The turn-down is harmless; it's a volume offset. What makes the slam lose at matched loudness is the damage printed *into the file* — spent transients, hardened tails, fatigue — which the offset faithfully delivers. The platform removed the slam's advantage; the slam's own limiter removed its punch. Blame the right robot.

20. T/F: One LU is the same size step as one dB.

Answer **True.** A track at -11 LUFS integrated is 3 LU above a -14 reference and gets a -3 dB offset; the units exchange one-for-one. (Same family resemblance as LKFS, which is the identical unit under a US broadcast badge.)

Short Answer

21. Explain the two-stage gate in the integrated measurement — what each stage discards and the loophole the second stage closes — in three or four sentences.

Answer The absolute gate discards everything below -70 LUFS — silence and near-silence (count-ins, gaps, dead air) — before any averaging. The meter then computes a provisional average and the relative gate re-averages after also discarding every block more than 10 LU below that average, excluding radically quiet passages like ambient intros and long fades. Result: integrated loudness describes the body of the program. The relative gate closes the padding loophole: without it, a slammed track wearing a minute of hush would measure moderate, get turned down less, and play louder than its competitors — the war restarted by silence.

22. A -8 LUFS club track and a -14 LUFS ballad are both correct masters. Defend that sentence, then state the one rule that survives every genre.

Answer Correctness is contextual: the club track lives in un-normalized rooms — DJ chains, sound systems, sets where it plays beside other -8 records — and its density is its genre's texture; at -14 it would be wrong *there*. The ballad's power is dynamic reach, which normalization delivers intact to every streaming listener; at -8 it would be destroyed *everywhere*. The universal rule: don't destroy dynamics chasing a number that normalization cancels — master for the music at matched loudness against references, and let the number be an outcome you sanity-check.

23. Describe Aisha's three-read QA ritual for a podcast episode: which meter reading does each job, and what's the goal of the whole practice in one sentence?

Answer Integrated, per episode: the finished bounce measures ≈ -16 LUFS stereo (±1) so the show plays at one loudness across the catalog. Short-term, per segment: while editing, every voice — host, guest, clips — stays within about 1 LU of the others so nobody reaches for the knob mid-episode. True peak, at the gate: ≤ -1 dBTP on the publish bounce, every time. The goal: be un-noticeable — levels nobody ever thinks about.

24. Why does this chapter tell you to measure your three reference tracks' integrated loudness and PLR — and what does that replace?

Answer Because your references are your genre's loudness and dynamics culture, measured empirically (T4): their integrated numbers map the neighborhood your master should land near, and their PLRs show how much dynamics the genre actually keeps. It replaces every forum argument and every printed table — including this book's — with data from the records you already chose as your compass, and it converts the QA neighborhood check from someone else's opinion into your own evidence.

Applied Scenario

25. The band you're mixing for sends two demands before release: "Master the single to -7.5 LUFS so we're the loudest thing on every playlist," and "master the acoustic B-side to exactly -14 because that's Spotify's number." Write the full correction: the normalization arithmetic on the -7.5, what the slam still costs, what's wrong with the B-side's reasoning, where density genuinely would still pay, and the deliverables you'd actually propose — with the QA gates each must pass.

Answer **The single's arithmetic.** On every major platform with normalization on (defaults, as of this writing), a -7.5 master meets a ≈ -14 reference and plays roughly 6.5 dB down. The loudness advantage doesn't reach a single playlist listener — it's confiscated at the door. What does reach them is everything the push printed into the file: shaved transients, hardened bass tails, a PLR around 6–7, and a fatigue curve — delivered at matched loudness next to competitors who kept their punch. The slam pays full wartime taxes and collects no wartime prize. **The B-side's reasoning.** -14 is a playback reference, not a delivery spec — "so Spotify doesn't touch it" buys nothing, because the offset changes nothing inside the file anyway. The acoustic track should be mastered for *its* music: by ear, at matched loudness, against acoustic-genre references (commonly landing -14 to -12 with generous PLR — measure the band's actual refs rather than trusting the integer). If it lands near -14, fine; that's an outcome, not obedience. **Where density still pays.** Un-normalized contexts: DJ/club chains, raw file swaps, some social/sync paths, listeners who toggle normalization off. If — and only if — the single genuinely lives in those rooms, propose a second, hotter club print as a separate deliverable. **The proposal.** Master the single by the [Chapter 32](../chapter-32-mastering-tools-techniques/index.md) ladder to its last honest *better*, sanity-checked against the genre's measured reference family; master the B-side the same way against its own refs; optionally one club print of the single. Every deliverable passes two gates: true peak ≤ -1.0 dBTP (non-negotiable), and integrated within shouting distance of its measured reference neighborhood — with any deliberate outlier documented as a decision. Then send the band the three-masters experiment (exercise C2) with their own track and let the blind jury tell them what you just did: at the loudness everyone will actually hear, the slam finishes last on its own scorecard.

Scoring

Count one point per fully correct answer — justifications required on 16–20, with generous partial credit for sound reasoning. The scenario is worth a high bar: full credit needs the arithmetic, the cost analysis, the B-side correction, the un-normalized caveat, and concrete deliverables with gates. 25 points possible.

Score Verdict Prescription
Below 50% (<13) The units haven't separated yet Re-read "LUFS in Plain Words" and the four-unit table, redo exercises A1–A5, then retake. Everything in this chapter hangs off knowing which number answers which question.
50–70% (13–17) Mechanics present, consequences fuzzy Review your misses (most people: the gate, the turn-up asymmetry, and question 19's blame-the-right-robot distinction), run Listening Lab B3 and B6, retake in a day or two.
70–85% (18–21) Solid working grasp Skim weak spots, make sure C1's passport actually exists in your journal, and move on to Chapter 34 with confidence.
Above 85% (22–25) Fluent — you've crossed the threshold Go straight to Chapter 34. You're also now the designated person in your circle who corrects loudness forum posts; use the power kindly.