Quiz — Chapter 6: The DAW
Closed book, closed DAW. Answer everything, then check yourself against the keys in the drop-downs. Scoring guidance is at the bottom — be honest; the only person you can shortchange here is the one mixing your songs.
Section 1 — Multiple Choice (15 questions, 2 points each)
1. The five universal elements every DAW shares are: a) Tracks, plugins, presets, loops, a master fader b) Tracks, regions, a mixer, a transport, a browser c) A piano roll, a sampler, a mixer, an arranger, a store d) Audio tracks, MIDI tracks, buses, returns, markers
2. A track's "double identity" means it is simultaneously: a) An audio recorder and a MIDI recorder b) A horizontal timeline lane and a vertical mixer channel — two views of one object c) A destructive and a non-destructive editor d) An insert chain and a send chain
3. When you trim and split a region, the audio file on disk: a) Is permanently shortened b) Is copied once per split c) Is untouched — regions are pointers playing slices of it d) Is re-rendered at the session's sample rate
4. An insert effect differs from a send effect because an insert: a) Processes a copy of the signal while the dry continues b) Can only hold one plugin per track c) Passes the entire signal through the processor in series d) Is always 100 percent wet
5. The correct wet/dry setting for a reverb on a return track is: a) 50 percent, to balance wet and dry b) 100 percent wet, because the dry signal already exists on the source tracks c) 100 percent dry, to preserve punch d) Whatever the preset loads with
6. Three tracks all need to stand in the same reverb. The professional routing is: a) One reverb instance inserted on each of the three tracks b) One reverb on a return, fed by a send from each track at its own level c) A reverb on the 2-bus so everything shares it d) A reverb inserted on the loudest of the three tracks
7. A post-fader send means: a) The send level ignores the track fader b) The send is placed after the last insert but before the EQ c) Pulling the track fader down pulls its send contribution down with it d) The send can only feed the 2-bus
8. A bus, as distinct from a send/return, is a channel that: a) Receives copies of signals at adjustable levels b) Carries the summed full output of the tracks routed to it c) Can only contain effects, never level changes d) Exists only on hardware consoles
9. This book's standard six-bus architecture is: a) KICK, SNARE, BASS, LEAD, VOX, MASTER b) DRUMS, BASS, SYNTHS, GTR, VOX, FX c) RHYTHM, MELODY, HARMONY, VOX, FX, REF d) LOW, LOW-MID, MID, HIGH-MID, HIGH, AIR
10. The strongest argument for naming a track PAD — verse instead of Sylenth1 (3) is:
a) Shorter names load faster
b) Plugin names are trademarked
c) The name describes the musical job, which is what mix decisions need to know
d) Mixer strips can't display parentheses
11. Template bloat is a failure mode because: a) Templates over 20 tracks are unstable in most DAWs b) A huge pre-loaded template slows loading, buries ideas, and pre-decides your sound before the song exists c) Templates can't contain buses d) Sample libraries expire
12. The main reason to learn keyboard shortcuts, per this chapter, is: a) Professional certification requires them b) They reduce context switches, preserving listening attention and shortening the gap between intention and result c) Mouse use causes repetitive strain d) Menus differ between DAWs but shortcuts don't
13. Freezing a track: a) Permanently converts it to audio and unloads its plugins b) Temporarily renders it to audio to free CPU, reversible with one click c) Locks it against accidental edits only d) Disables it from playback entirely
14. At matched settings with identical sources and plugins, two different DAWs render mixes that: a) Differ audibly because of each DAW's summing "color" b) Are mathematically equivalent — null tests confirm the engines aren't the difference c) Differ only at sample rates above 96 kHz d) Differ only on Windows
15. The REF track in your template is routed around the 2-bus so that: a) It can play while other tracks are frozen b) It doesn't consume CPU c) Any processing you later place on the 2-bus can't color the professional reference you're comparing against d) It stays out of the mixer view
Answer Key — Section 1
1. **b** — tracks, regions, mixer, transport, browser; everything else is wardrobe. 2. **b** — one object, two camera angles; a mixer move is a lane move. 3. **c** — non-destructive editing: edits are instructions about the file, not surgery on it. 4. **c** — inserts are in-line/series; the processed signal replaces the dry downstream. 5. **b** — dry already exists on the sources; dry signal in the return creates a phantom double. 6. **b** — one shared space, individually metered doorways: cohesion, control, CPU. 7. **c** — post-fader sends preserve the wet/dry relationship as you balance. 8. **b** — a bus is a summing checkpoint the whole signal flows through; a return receives copies. 9. **b** — DRUMS, BASS, SYNTHS, GTR, VOX, FX, all into the 2-bus. 10. **c** — name the job, not the tool. 11. **b** — templates' mistakes are subscribed to by every future song; keep them lean and reviewed. 12. **b** — speed is creativity preserved; every menu hunt is a context switch away from listening. 13. **b** — freeze is non-destructive deferral; render/bounce in place is the committed version. 14. **b** — workflow differs, decisions differ; the math doesn't. The engine was never the gap. 15. **c** — the reference must be heard exactly as released for the comparison to be honest.Section 2 — True/False with Justification (5 questions, 3 points each)
State true or false, then justify in one or two sentences. No justification, no points.
16. Because DAW editing is non-destructive, no operation in a DAW can ever overwrite or commit audio.
17. A track count of 60 indicates a more professional production than a track count of 12.
18. EQ and compression that define a sound generally belong on inserts, while shared spaces like reverb and delay generally belong on sends.
19. The best first response to feeling limited by your DAW is to switch to the DAW your favorite producer uses.
20. Keeping the 2-bus empty in your starter template is a deliberate headroom habit, not an oversight.
Answer Key — Section 2
16. **False.** Regions and edits are non-destructive, but operations like render/bounce in place, "apply"/"flatten" commands, wave-editor processing, and certain record modes create or replace files. Audit your DAW's dangerous verbs once. 17. **False.** Track count measures nothing; sparse records ("Royals," "bad guy") win on intention and audibility. The amateur adds; the professional subtracts. 18. **True.** The rule: if the effect defines the sound, insert it; if it's a space sounds live in, send to it — with deliberate sound-design exceptions allowed. 19. **False.** Fluency beats features; the conceptual machine is identical everywhere. Switch only when your DAW lacks something you need weekly — otherwise you're trading months of muscle memory for wardrobe. 20. **True.** Mixing into 2-bus processing from day one distorts your judgment and eats the headroom later stages need; the empty 2-bus practices the discipline [Chapter 21](../../part-05-mixing-foundations/chapter-21-gain-staging/index.md) formalizes.Section 3 — Short Answer (4 questions, 5 points each)
21. Explain the "phantom double" problem: what causes it, what it sounds like, and the fix.
22. Your CPU meter is pinned and playback crackles mid-session. List, in order, the three escalating tools this chapter gives you, with one sentence on what each costs.
23. Define session as this book uses the term, and name four things it contains beyond "the tracks."
24. A collaborator opens your session cold. Name the three organization rules that should let them navigate it in under a minute, and state why consistency across sessions matters more than the specific choices.
Answer Key — Section 3
21. A return track's effect left partially dry (e.g., 50 percent wet/dry) passes a copy of the unprocessed source back into the mix — a quieter, stacked duplicate under everything. It sounds like smeared balance, softened punch, and "washy" vagueness. Fix: set return effects to 100 percent wet; the dry already exists on the source tracks. 22. (1) The buffer dance — raise the buffer while arranging/mixing; costs latency you don't currently need. (2) Freeze — temporary render that suspends plugins; costs a click and a moment of rendering, fully reversible. (3) Render/bounce in place — commits the sound to audio and unloads the tools; costs editability of the original chain (and rewards you with material and focus). 23. A session is the complete working document: the project file plus the audio files it references, the sample-rate/bit-depth settings, the tempo/time-signature grid, and every track, region, routing, edit, name, color, and marker decision in it. (Any four.) 24. Name everything for its musical job; color by family with one lifelong palette; keep the same track order in every session (plus markers). Consistency matters more because navigation is a *reflex*, and reflexes only form when the map never changes — a brilliant scheme used once is still a scheme that must be read instead of felt.Section 4 — Applied Scenario (15 points)
25. Your friend Maya sends you her session for help. You find: 47 tracks, 19 of them muted experiments; tracks named Audio 3, Audio 3.1, synth??, and USE THIS ONE; a different reverb plugin inserted on the lead vocal, both harmony tracks, the snare, and a pluck (five instances, five different settings); everything routed straight to the 2-bus, which carries a limiter she added "to make it loud"; the project is named MAYA SONG FINAL FINAL 3. Playback crackles on her laptop.
Write her a prioritized rescue plan — five to seven steps, in order, each with a one-sentence rationale tied to this chapter. End with the one habit that prevents the whole situation next time.
Model Answer — Section 4
A strong plan hits these beats (order can vary slightly, but commit-and-clean should precede routing, and routing should precede CPU triage): 1. **Save a safety copy, then rename the project with a real version** (`MayaSong_v4`) — "final" is banned because it's a lie the moment it's saved, and the rescue needs an undo path. 2. **Triage the 19 muted experiments: delete the dead, render and archive the maybes** — non-destructive hoarding is deferred decision-making, and the museum of paths not taken is costing CPU and clarity. 3. **Name every surviving track for its job and apply family colors, then drag into a standing order** — navigation must become reflex; `USE THIS ONE` tells nobody anything in six months, including Maya. 4. **Build the family buses (her version of DRUMS/BASS/SYNTHS/VOX/FX) and route tracks through them** — group-level balance and processing become one-fader decisions, and stems fall out for free later. 5. **Replace the five insert reverbs with one (or two) returns, 100 percent wet, fed by sends at per-track levels** — one shared space restores cohesion, gives one knob of control over the room, and reclaims serious CPU. 6. **Take the limiter off the 2-bus** — loudness is a later stage's job; mixing into a slammed master teaches lies and burns the headroom the mix and master will need. 7. **CPU pass: raise the buffer for mix work and freeze heavy, untouched tracks** — crackles are missed buffer deadlines, and freeze is free. Prevention: **build a template** — names, colors, order, buses, wet returns, empty 2-bus, saved once — so every future song starts clean instead of being cleaned. (Full credit requires the limiter removal and the insert-to-send conversion to appear with correct rationales; those are this chapter's two load-bearing fixes.)Scoring
| Section | Points available |
|---|---|
| 1 — Multiple Choice | 30 |
| 2 — True/False + Justify | 15 |
| 3 — Short Answer | 20 |
| 4 — Applied Scenario | 15 |
| Total | 80 |
| Score | Reading |
|---|---|
| 72–80 | Fluent — your template and your concepts match; move to Chapter 7 |
| 60–71 | Solid — re-skim the sections behind your misses (routing and the survey are the usual suspects) |
| 45–59 | Rebuild the core: re-read "Inserts vs. Sends/Returns" and "Buses and Submixes," redo DAW Lab C2–C3 and C7, retake in two days |
| Below 45 | Re-read the chapter with your DAW open, doing each concept as you read — this material is hands-on, and hands fix what re-reading alone won't |
One pattern worth flagging: missing questions 4–8 (the routing cluster) predicts pain in Parts V and VI more reliably than missing anything else in this quiz. If that cluster cost you points, spend thirty minutes in the DAW Lab before moving on. Routing is cheap to learn now and expensive to learn during a mix.