Chapter 27 Exercises

Automation is a hands skill wearing a concepts coat, so this set is weighted toward the DAW Lab — and the DAW Lab is weighted toward your own mix, because rides only mean anything against a balance you built. You'll need: your stabilized mix from the Chapter 26 checkpoint (balance, EQ, compression, space, width, and color all settled — if it isn't settled, finish that first; riding a moving target is this chapter's cardinal sin), your three reference tracks from Chapter 4, a lyric sheet for your lead vocal (the Chapter 11 markup if you have it), headphones or your treated-room monitors, and your listening journal.

Two ground rules. First: the hierarchy before the ride — any exercise that asks for vocal rides assumes clip gain (Chapter 21) and the leveler (Chapter 23) already did their jobs; if your rides want more than ±2 dB, stop the exercise and fix the layer below. Second: read mode is home — every DAW Lab exercise ends with all tracks returned to read and the session saved. Selected answers and worked examples appear in the back-of-book Answers appendix. Exercises marked 🎧 are focused listening; 🎛️ exercises need your DAW open. Spread the set across several short sessions — ride judgment is a fresh-ears skill, and the blind tests in C2 and C5 are explicitly invalid on fatigued ears (Chapter 4's hygiene rules govern).

Part A — Conceptual Understanding

A1. The thesis, defended. "Static mixes are corpses" is a strong claim, and a skeptic might answer: "My balance is correct everywhere — why would I change correct?" Write the chapter's response in one paragraph, using all three of these ideas: perceptual adaptation (why a constant stops being information), intention rendered as change (what movement actually communicates), and the static mix's real status in the workflow (what Chapter 20's name for it was disclosing). Then add the boundary clause: name one genre context where near-stasis is the correct choice, and what makes it correct there.

A2. Two workflows, one lane. Define performance automation (riding) and programmed automation (drawing) in one sentence each, then assign the right method to each of these five jobs with a one-line reason: a +0.5 dB chorus lift; a vocal ride across verse two; a de-ess on one ess; a four-bar filter open into the drop; "make the bridge feel like it's holding its breath."

A3. The hierarchy, diagrammed from memory. Without looking back: draw the three-layer vocal level hierarchy, label each layer's tool, chapter of origin, typical working range, and one-word job. Then write the diagnostic rule that the hierarchy enforces: what does a ±6 dB ride mean, and where do you look first?

A4. The lift family tree. List five members of the section-lift family with typical sizes, and explain why the dim — lowering parts before a boundary — is described as the family's strongest member. Your explanation must invoke both T2 (less is more) and the Chapter 21 headroom contract.

A5. The border, operationalized. Chapter 17's border sentence — architecture there, balance here — became a decision tree in this chapter. Apply it: for each scenario, rule arrangement, processor policy, or automation, and name the owning chapter. (a) The hats need +1 dB in every chorus. (b) The vocal's 300 Hz mud bothers you all song. (c) The last word of the bridge should ring out into the final chorus. (d) The vocal disappears on quiet syllables in every phrase. (e) This one verse line should sit back so the guitar answer speaks.

A6. Master-section caution, argued. Your bandmate wants to automate the 2-bus fader +1 dB for the final chorus: "It's one move, it's easy." Write the three-part case against it (the headroom contract, the processors that read level, the confession a whole-mix lift makes), then give the two legitimate alternatives — and name the one traditional exception to the master-fader taboo and the tradeoff that comes with deferring it.

A7. The JND, applied. Using the Advanced Sidebar's logic: explain why +0.5 dB is called "the professional unit of feel," what happens perceptually when a lift grows to +2 dB, and why a fader pulled down to -30 is a worse riding surface than a trim plugin at unity. Hedge your numbers the way the chapter does — anchors, not constants.

Part B — 🎧 Listening Lab

B1. The movement pass (the new sixth pass). Take your three Chapter 4 reference tracks and run one full playthrough of each, tracking only what changes: lead vocal level phrase to phrase, section-to-section lifts, space swelling or drying, width opening or folding, FX events. Log every move you can catch with a timestamp and a size guess (subtle / clear / dramatic). This is the chapter's core listening skill: hearing the invisible layer. Expect to catch more on the second playthrough — that's the layer working as designed.

B2. The vocal ride hunt. Pick one modern pop or R&B record you know well — something with an exposed, polished lead vocal. Listen twice at moderate level, attention locked on the vocal's level against the track (not its tone). Log: three moments where the vocal leans forward, two where it sits back, and one where you suspect a syllable-level rescue (a word that's quieter or louder than its phrase had any right to deliver). You cannot verify the engineer's lane — you're training the detector, not auditing the session — so log confidence levels, not certainties.

B3. Find the chorus lift. On two of your references: loop the last four bars of a verse, then the first four bars of the following chorus, several times each, at matched playback level. Question: does the lead vocal's prominence change across the boundary by more than the arrangement explains? Describe what you hear in level terms ("vocal feels +0.5 to +1 dB more present") and list which lift-family cousins you suspect (vocal lift, hat lift, width bloom, verb change, a dim before the boundary). Journal which cousin was hardest to separate from arrangement changes — that difficulty is the trick working.

B4. Throw safari. Across any five songs in your genre playlist, hunt phrase-tail throws: words that bloom into delay or reverb at section boundaries. Log each find: timestamp, the word thrown, delay or reverb (or both), bright or dark tail, how many repeats you can count, and whether the tail collides with or carpets the next section's entrance. If you find fewer than three across five songs, switch genres for the back half — pop and hip-hop are throw country.

B5. Static versus ridden, A/B. Build a two-song comparison: one deliberately static-aesthetic track (lo-fi beats, ambient, minimal house) and one maximal pop production. Listen to ninety seconds of each, twice. Journal: where did your attention go in each, when did it drift, and — the real question — did the static track's stillness read as intentional (trance, weather by design) or as missing (a mix nobody finished)? Write one sentence on what makes designed stasis feel different from omitted movement.

B6. The fade and the close-down. Find two songs that end by fading or closing down (filters shutting, width folding, elements leaving) rather than on a hard stop. Map the exit: how long is it, what moves, in what order, and does it feel performed or drawn? Connect to the chapter: which parts of the exit are architecture (Chapter 17's close-down) and which are mix-balance moves (this chapter's)?

B7. Density audit, by genre. Pick one song each from three different rows of the chapter's genre-density table. For each, estimate the density in plain words (near-static / preservation rides / moderate / maximal) and name the one most-moved element. Then check your estimates against the table's predictions and journal any surprises — a folk record with a maximal vocal lane, a pop record with a frozen bridge. Surprises are where genre conventions are being deliberately broken (Chapter 18's contracts, breached knowingly).

Part C — 🎛️ DAW Lab

C1. The twenty-ride vocal pass. On your own mix: hierarchy audit first (ten minutes — clip gain even? leveler at 2–4 dB on loud phrases?). Then print or open your lyric sheet, mark the lines that matter most and least, and perform a ride pass on the lead vocal — fader, controller knob, or mouse, recorded into the lane — targeting at least twenty distinct moves, all inside ±2 dB, riding toward the lyric's meaning. Do up to three takes; keep the best. Then thin the lane until your intention is readable at arrangement zoom. Deliverable: a journal entry listing your five biggest moves and the lyric reason for each. If any move wanted more than 2 dB, write down which lower layer failed and fix it before continuing.

C2. The +0.5 dB lift, blind. Draw a +0.5 dB lift on your lead vocal for the final chorus only (two breakpoints, snapped to the boundary). Now the test: bounce two versions — lifted and not — name them neutrally, close your eyes (or have a friend drive), and A/B at matched start points several times. Can you reliably pick the lifted one? Does the lifted chorus feel louder, or does it feel like arrival? Repeat the experiment at +2 dB and journal the difference in how the move reads. This is the JND sidebar as a lab: the half-decibel should be feelable-but-not-nameable; the 2 dB version should announce itself.

C3. The manual de-ess drill. Find the three worst esses in your lead vocal (zoom in — they're visible as high-frequency hash). On each, draw the four-point move: ramp down, hold at -2 to -4 dB for just the ess, ramp back. A/B each fix against bypass at matched loudness. Then write the comparison sentence: what did the manual move do that a single static EQ cut at the sibilance frequency could not? (Answer in terms of when each is active.)

C4. One throw, placed and tamed. Build a dedicated throw return: tempo-synced delay (dotted-eighth is the default), EQ'd dark (high-passed and low-passed harder than feels right in solo), send from the lead vocal sitting at -∞. Choose the one word in your song that most deserves to ring — a section boundary's last word — and draw the send leap for that word only. Then tame the tail: if the repeats fight the next downbeat, automate the feedback or return level down across the boundary. Deliverable: the before/after bounce, and one journal line on why that word.

C5. The dim experiment. Instead of lifting your chorus, dim before it: pull two supporting parts (pads, rhythm guitar, keys) down 0.5 dB through the final two to four bars of the preceding section, returning to unity on the chorus downbeat. Blind-A/B against the unedited version. Journal: does the chorus feel bigger, and did anything get louder to achieve it? Check 2-bus peaks before and after to confirm the move's headroom cost (it should be zero or negative — that's the point).

C6. Mode tour. Take one eight-bar vocal phrase that your C1 ride pass got slightly wrong. Fix it three ways, undoing between attempts: (a) in touch mode — grab, correct, release, and confirm the lane returns to your original pass after release; (b) in latch mode — grab, correct, and observe what happens after release until you stop transport; (c) by drawing breakpoints over the offending phrase. Journal which method felt right for this job and write the one-line rule for when each mode earns the work. End in read mode. Save.

C7. The offset problem, solved twice. Your C1 ride is done — and now pretend the verdict comes back: "whole vocal +1 dB." Solve it without redrawing a single breakpoint, two ways: (a) trim/relative automation if your DAW has it (Appendix E), offsetting the lane wholesale; (b) a separate gain stage layered after the ridden one — trim plugin, VCA-style group, or bus fader. Verify with your ears and the meter that the ride's shape survived both solutions. Journal which layering you'll adopt as your standard and why.

C8. The audit ritual. Full-mix playback in read mode, top to tail, no touching: confirm every lane plays as intended, confirm 2-bus peaks still honor the -6 dB contract (Chapter 21), confirm no orphaned moves (if you edited audio after automating, listen specifically at those edits). Then the next-morning listen before declaring the pass done. Deliverable: your written verdict in the journal — beautiful and boring, or beautiful and breathing?

Part D — Synthesis & Critical Thinking

D1. The automation philosophy paragraph. Write the automation section of your production manifesto (Chapter 5's document, still alive): your genre, your density budget (cite the table row you're nearest), the three moves you'll make on every song, and the one move you'll deliberately not make. Defend the abstention with either T2 or your references (T4).

D2. The live-mixer thought experiment. A front-of-house engineer mixes your song live, hands never leaving the faders — then mixes it again the next night, and the rides differ slightly both nights. Your DAW automation plays identically forever. Write two paragraphs: what the captured-forever version gains (precision, repeatability, the sub-JND lift craft) and what it risks losing (response to the room, the night, the moment) — and how performing your rides rather than drawing them is an attempt to keep the second thing inside the first.

D3. Design the full map. For a song you know intimately but didn't make: design its complete automation pass on paper. A lift map in the chapter's diagram format (sections across the top, moved elements down the side), the five most important vocal rides with lyric reasons, one throw placement with the word named, and one thing you'd leave deliberately static. You can't verify against the real session — the deliverable is the reasoning, and the exercise is how working mixers internalize the layer.

D4. The diminishing-returns argument. Case study 1 describes a professional vocal lane carrying hundreds of breakpoints and argues the first forty do most of the audible work. Take a position in two paragraphs: at what density does your own work stop paying for the evening it costs — and what, specifically, about a release context (major-label single vs your Friday upload) changes where that line sits? Use T3 honestly: name what the extra four hundred points buy, and what they cost.

Part M — Mixed Practice

M1. (Chapter 21) Your automation pass added six lifts averaging +0.5 dB and two dims averaging -0.5 dB. The 2-bus previously peaked at -6.2 dB. Explain why you can't arithmetic your way to the new peak value and must re-measure — and name the two places you check after any lift pass.

M2. (Chapter 16) A producer friend's chorus "doesn't lift" no matter how many automation moves they add. Applying Chapter 16's contrast engine and this chapter's decision tree: what's the first non-automation question to ask about their verse, and which sixty-second test answers it?

M3. (Chapter 24) Your throw return uses the shared plate instead of a dedicated delay, and now the throw event drags a wash across the whole next section. Using Chapter 24's send architecture logic, explain what went wrong and the two-part fix.

M4. (Chapter 10) You can't hear your own +0.5 dB lifts on your monitors, but you can on headphones. Before blaming your ears: which Chapter 10 problems could erase a half-decibel at your listening position, and what's the no-gear test that checks?

M5. (Chapter 2) You bounced "lifted" and "unlifted" versions for the C2 blind test as MP3s and the difference seems smaller than it did in the session. A friend claims lossy encoding "compresses the dynamics." Correct them using Chapter 2's vocabulary: what does lossy encoding actually discard, what doesn't it touch, and what's the right export format for a fair A/B?

M6. (Chapter 23) A collaborator's lead vocal is uneven two ways at once: verse two was recorded noticeably hotter than verse one (the singer crept toward the mic between takes), and within every phrase the loud syllables jump while the quiet ones bury. Their plan: "one careful ride pass fixes everything." Using Chapter 23's purposes taxonomy and this chapter's three-layer hierarchy, assign each of the two problems to its correct layer and tool, explain why a ride is the wrong fix for both — and then name what the ride pass is for once those layers have done their jobs: what can a ride do that no compressor ever can? Finally, the reverse case: in the bridge, the singer deliberately leans into one line for dramatic effect, and the leveler keeps pressing it flat. Which layer wins that argument, what's the concrete move, and what does this pair of failures — a ride doing a compressor's job, a compressor undoing a ride's — tell you about the difference between control and intention?

Selected answers and worked examples: see the Answers appendix. The exercises that matter most this chapter are C1, C2, and C5 — the ride, the lift, and the dim. If you only have one evening, spend it there, then take the quiz.