Exercises — Chapter 6: The DAW

Work these in order if you can: concepts first, then ears, then hands. The DAW Lab is the heart of this set — this is the most hands-on chapter so far, and the template you build in Part C is a deliverable you'll use for the rest of the book (and, if you build it well, for years after). Budget roughly 30 minutes for Part A, 60–75 for Part B, two hours for Part C spread across a few days, and 45 minutes for Parts D and M. Selected answers appear in Answers to Selected Exercises in the back matter; exercises marked ★ are answered there.

Part A — Conceptual

A1. ★ Two costumes, one object. A track has a "double identity" in every DAW. Name both identities, then explain — in terms a non-producer friend would follow — why muting a channel strip in the mixer silences a lane in the arrange view.

A2. The pointer principle. You record a vocal take, then trim 20 seconds off the front of the region, split what's left into five pieces, and delete two of them. Describe exactly what has happened to the audio file on disk, and name the editing philosophy that makes this possible. Then name two operations in a DAW that do create or replace files, and the habit that protects you from them.

A3. ★ Insert or send? For each, say insert or send, and justify in one sentence: (a) an EQ removing rumble from a vocal; (b) a plate reverb shared by lead vocal and harmonies; (c) a distortion that defines a bass sound; (d) a tempo-synced delay that the snare, the lead synth, and one vocal phrase all feed; (e) a compressor controlling a bass performance's dynamics; (f) a reverb used as a one-off sound-design texture on a single riser that you plan to render.

A4. The phantom double. A producer sets up a send reverb but leaves the return's wet/dry mix at 50 percent. Describe what is now arriving at the 2-bus from that return, what it does to the mix's balance, and the one-knob fix.

A5. ★ Bus vs. return. Both are "channels that receive from other tracks," yet they do different jobs. State the functional difference in two sentences, then give one concrete example of each from the six-bus architecture in this chapter.

A6. The case for groups. Your drum kit spans eleven tracks and the whole kit needs to come down 2 dB without changing its internal balance. Explain the bus solution, then explain what the same move costs you without a bus — and why "select all eleven faders and drag" is more fragile than it sounds (hint: think about what happens after you've automated one of them, or when faders hit different parts of their travel).

A7. Template economics. Using this chapter's reasoning, explain why the timing of setup work matters more than the amount of it. Then list the six things this chapter says belong in a starter template — and the one thing that explicitly does not belong on the 2-bus, with the reason.

A8. ★ The buffer gearshift. When do you want a small buffer, when do you want a large one, and what symptom tells you you've chosen wrong in each direction? Connect your answer to the freeze and render-in-place tools: what problem do all three tools share?

Part B — 🎧 Listening Lab

For each exercise, listen on the best playback you have, at a moderate matched level, with eyes closed for at least one pass. Log your observations in the listening journal you started in Chapter 1. These exercises train you to hear session architecture — tracks, families, and shared spaces — inside finished records.

B1. ★ Count the lanes — Lorde, "Royals." This is one of the sparsest hit records of its decade. Across the first chorus, count every distinct element you can hear (treat a stacked harmony group as one element, then try to count the stack separately). Write each element down with a job-description name, the way this chapter names tracks: not "synth" but "SUB — the floor." Most listeners find the total shockingly small. What does each element's job turn out to be?

B2. Count the lanes — Queen, "Bohemian Rhapsody," opera section (around 3:03–4:07). The opposite extreme: an arrangement famously built through punishing tape overdubs (Chapter 5's generation-loss story). Don't try for an exact count — you can't, and that's the lesson. Instead, identify the families: how would you bus this section if it landed in your template? List the buses you'd create and what you'd route to each.

B3. Job-naming drill — Billie Eilish, "bad guy." Verse one and chorus one. Name every element with a track name and a one-phrase job ("BASS SYN — the hook's dance partner"). Then answer: which single element would the song miss most if muted? You're doing the "every track must earn its lane" audit on a record that already passed it.

B4. ★ Hear a shared space — Adele, "Hello," first chorus. Focus on the lead vocal and the backing harmonies. Listen for the room they share: do the harmonies appear to stand in the same large space as the lead, or a different one? That same-space cohesion is what a shared send reverb sounds like on a record. Describe the space in Chapter 4 vocabulary (size, brightness, how long the tail hangs after phrases end).

B5. Hear two different spaces coexist — Phil Collins, "In the Air Tonight." Compare the voice in the first verse (close, dry-ish, intimate) with the drums when they finally erupt (huge, exploding room). Two radically different spaces in one mix — evidence of deliberate space assignment rather than one reverb dumped over everything. Sketch it as a depth map: which elements are near you, which are far away? Where would a single insert-reverb-on-everything approach have failed this arrangement?

B6. ★ Family cohesion — Daft Punk, "Get Lucky." Listen to the drums as one instrument, then try to split them into lanes by ear (kick, snare, hats, percussion). Notice how they move as a unit — level, groove, and space — the audible signature of sounds living on one bus, treated as a family. Then do the same for the layered guitars. How many guitar lanes do you believe are playing, and what makes them read as one section?

B7. Two people, few lanes — The White Stripes, "Seven Nation Army." A duo, famously committed to rawness. Inventory the elements across the whole song and propose the complete session layout map — named lanes, colors, buses — that could contain it. (The "bass" is the trick question: it's a pitched-down guitar. Name the lane for its job.) Compare your map's size to the one you sketched for B2 and write one sentence about what track count did and didn't determine in each record.

Part C — 🎛️ DAW Lab

These are this chapter's real homework. Keep Appendix E open for your DAW's names for each control.

C1. ★ Build the standing template (45–60 min). Follow the Project Checkpoint sequence exactly: new session at 48 kHz / 24-bit → fourteen named lanes in the standing order → six buses (DRUMS, BASS, SYNTHS, GTR, VOX, FX) with every lane routed to its family and every family routed to the 2-bus → returns set 100 percent wet and routed to FX → full color code applied → yellow REF track routed around the 2-bus, muted, loaded with one Chapter 4 reference → two instant-start instruments loaded → save as template (Starter_ plus the date). Verification pass: play a sound on any lane and watch it light up three meters in sequence — lane, family bus, 2-bus. If any meter stays dark, trace the routing until you find the break. That trace is the lesson.

C2. Route a send, prove it's post-fader (15 min). On your template's SNARE lane, send to RETURN: VERB at a moderate level. (a) Confirm the return is 100 percent wet by muting the SNARE lane's output fader-down — wait, you can't mute the dry and keep the send if it's post-fader, which is the experiment: pull the snare's fader slowly to silence and listen to what the reverb does. Post-fader: the reverb dies with the snare. (b) Now switch that send to pre-fader (Appendix E) and repeat: the snare disappears but its ghost keeps singing in the reverb. Write one sentence on when each behavior is what you want. Switch it back to post-fader before saving.

C3. ★ The phantom-double demo (10 min). Deliberately set RETURN: VERB's mix to 50 percent wet, send a drum loop to it, and listen at matched level against the 100-percent-wet version. Describe what the 50-percent version does to the loop's punch and stereo image (you've created a quieter, slightly-later copy of the dry signal stacked underneath everything). This is an inoculation exercise: hear the mistake once on purpose so you recognize it forever.

C4. Rescue an old crime scene (30–45 min). Open the messiest old project you own — your own final_v3_REAL. Time yourself on this task first: "find the lane carrying the main melodic hook and solo it." Write down the seconds. Now apply the doctrine: name every lane for its job, apply your family colors, drag lanes into the standing order, delete (yes, delete — export a safety copy of the whole project folder first) every muted experiment you haven't touched since creating it, and add section markers. Re-run the timed task on the cleaned session. Report both times in your journal. This before/after number is the most persuasive argument this chapter can make, and only you can run it.

C5. ★ The eleven-verbs shortcut drill (10 min/day for a week). Look up your DAW's keys for: play/stop, record, loop toggle, split, duplicate, mute, solo, undo, save, zoom in/out, and new track. Write them on a sticky note on your monitor. Each day this week, produce for at least twenty minutes with one rule: the mouse may not touch the transport or the edit menu. Day one will be infuriating. Day seven won't. Log the moment a shortcut fires without conscious thought — that's the instrument forming.

C6. Freeze and render experiments (20 min). Load your most CPU-hungry synth on a lane, play a pad, and open your DAW's performance meter. (a) Note the CPU reading. (b) Freeze the track; note the reading and what you can still edit. (c) Unfreeze, then render/bounce in place instead; note what your DAW did with the original (muted? moved? gone? — this is your destructive-verbs audit from the chapter, performed live). (d) Chop and reverse a slice of the rendered audio — notice that committing created material. Write two sentences: one on when you'd freeze, one on when you'd render.

C7. One fader, eleven decisions (15 min). In your template, drop a full drum loop spread across the four drum lanes (or program a quick pattern). Balance the four lanes against each other, then ride only the DRUMS bus fader against the 808 lane. Notice what stays constant (the kit's internal blend) and what changes (the kit's place in the song). Then try the same overall move without the bus by dragging all four lane faders — and observe the drift. Document which workflow you trust.

C8. ★ The 90-minute sprint (90 min, after C1–C7). Start a brand-new session from your template and build a rough loop or song section — drums, bass, one harmonic element, one extra — inside ninety minutes, ending with a correctly named, versioned save (SongName_v1). The goal isn't a masterpiece; it's experiencing what the template was for: zero setup friction between idea and sound. In your journal, note every moment friction appeared anyway — those are your template's v2 punch list.

Part D — Synthesis

D1. Design for a different life. A podcaster records one host and up to two remote guests, adds intro/outro music and occasional sound effects, and publishes twice weekly. Design their template on paper: lanes, names, colors, buses, and what loads by default. Justify every departure from this chapter's six-bus music architecture. (You've just discovered that the doctrine generalizes even when the layout doesn't.)

D2. ★ The advisor's letter. Three friends ask you "which DAW should I get?": a rapper with a Windows laptop who makes beats nightly; a folk trio recording themselves in a living room on a tight budget; a Mac-owning singer who produces her own demos and wants maximal stock sounds. Using the honest survey (and refusing tribalism), write a three-paragraph recommendation — one per friend — each ending with the condition under which they should ignore your advice.

D3. The two-costs essay. In 200–300 words, connect non-destructive editing to the "less is more" theme: how can a technology that makes keeping everything free end up making music worse, and what specific practices from this chapter (rendering, deleting losing experiments, template pruning, the job-naming test) act as the antidote? Use Jaylen's 411-file folder as your case evidence.

D4. Translate yourself. Pick the DAW you know least from the survey table. Using Appendix E, write a one-page "phrasebook" for moving a song from your DAW to that one: what each of your five most-used concepts (track, region, send, bus, render) is called there, and the one workflow difference you'd expect to slow you down most. (If you've truly never touched another DAW, do this exercise with its free demo or its manufacturer's online manual.)

Part M — Mixed Practice

Interleaving review — these reach back across Part I on purpose.

M1. ★ (Ch 1 + Ch 6) Your template's lanes will eventually fight for spectrum. Using Chapter 1's frequency vocabulary, predict which pairs of lanes in the standing layout are most likely to collide, and in which band: name at least three pairs (e.g., which two lanes will contest the sub region?). One sentence each.

M2. (Ch 2 + Ch 6) Your template locks in 48 kHz / 24-bit. Defend both numbers in two sentences each — what does 24-bit buy you while tracking that 16-bit doesn't, and why isn't 96 kHz the obvious upgrade? Then state where in the template's signal flow clipping is still possible even though your DAW's internal mixing is 32-bit float.

M3. ★ (Ch 3 + Ch 6) Draw (boxes and arrows, paper is fine) the complete signal chain from a USB microphone to your ears, and mark exactly which stretch of that chain lives inside the DAW. Label at least four gain stages, and circle the two where this chapter gave you new controls (channel fader, bus fader).

M4. (Ch 4 + Ch 6) Your REF track is only honest at matched loudness. Using Chapter 4's equal-loudness reasoning, explain what happens to your judgment when the reference plays 3 dB louder than your mix — which bands seem to bloom, and why "louder sounds better" even when it isn't. Then describe the two-step level-matching habit that fixes it.

M5. ★ (Ch 5 + Ch 6) Map five artifacts of the console era to their descendants in your template: the console channel strip, the multitrack tape machine, the razor blade and splice block, the patch bay, and the tape library. One sentence per mapping — and one final sentence on what the DAW added that the 1975 studio simply did not have.

Self-Check Before You Move On

Chapter 7 assumes the workshop exists. Before you turn the page, audit yourself against this list — honestly, the way you'd audit a collaborator's session:

• [ ] The template exists and loads. Not "I know what I'd put in it" — it opens, today, in under ten seconds, with fourteen named lanes, six routed buses, and an empty 2-bus.
• [ ] The routing is verified. You played a sound and watched it light three meters in a row: lane → family bus → 2-bus. You found and fixed at least one dead route doing it (almost everyone does).
• [ ] Both returns are 100 percent wet. You checked, because you did C3 and heard what 50 percent does.
• [ ] The REF lane works. One click flips you between your session and a professional reference, level-matched by ear, with nothing on the 2-bus coloring the comparison.
• [ ] StaticBloom_v1 (or your own song's v1) exists, built from the template, at 96 BPM — or your tempo — with section markers placed and a real versioned name. The word "final" appears nowhere on your hard drive's new files.
• [ ] You can state the insert/send rule from memory — one sentence, no notes — and answer A3 cold.
• [ ] At least five of the eleven verbs fire from your keyboard without looking at the sticky note.

If any box is empty, the fix is specific and short; do it now rather than carrying the debt into Part III, where recording sessions will spend whatever attention your workflow doesn't.

One last journal prompt (5 minutes): Re-read the hook. Jaylen lost a placement to his own folder. Write down the single workflow failure of yours that has cost you the most — the lost session, the un-findable beat, the idea that died during setup — and next to it, the specific practice from this chapter that would have prevented it. Date the entry. When your template feels like overhead some night, that entry is the receipt for why it isn't.