Chapter 19 Quiz

Closed book on the first pass — workflow doctrine only protects you when it fires from memory, usually at 1 a.m., usually with someone waiting on the file. Multiple choice, then true/false with justification (the justification carries the points), then short answer, then one applied scenario that is somebody's real week. Answers under each Verify fold; scoring guide at the end.

Section 1 — Multiple Choice (2 points each)

1. The difference between stems and multitracks is:

A) Stems are higher quality; multitracks are rough exports B) Multitracks are one file per individual track with minimal processing baked in; stems are one file per bus family, printed through the bus processing C) Stems are for hip-hop; multitracks are for rock D) There is no difference — the words are interchangeable

2. An outside mix engineer is hired to mix your song. They should receive:

A) Your six stems, so your bus processing guides them B) Your project file, so they can see everything C) Your multitracks plus your rough mix as a reference D) Just the rough mix — they'll ask for more if needed

3. Every printed file must start at the project's first sample — even a part that doesn't enter until 2:14 — because:

A) DAWs refuse to import files with different start times B) A bare audio file has no way to store its own timeline position; leading silence encodes the position in the audio itself, the one coordinate system every DAW shares C) The silence improves the sound of the file D) It makes all the files the same size on disk

4. The "same length" rule — every printed file runs from project start to project end — exists primarily so that:

A) The recipient can verify at a glance that nothing was trimmed or shifted, and drop any file at zero with certainty B) Reverb tails sound longer C) File sizes stay uniform for uploading D) The DAW can play them faster

5. The chapter bans "final" from file names because:

A) It's unprofessional slang B) Version numbers are shorter to type C) "Final" is a prophecy, not a description — and when the inevitable change request arrives, the name system collapses into final2 archaeology or silent overwrites D) Distributors reject files named final

6. The 3-2-1 backup rule means:

A) Back up three times a day, two times a week, once a month B) Three copies, on two different kinds of storage, with one offsite C) Three drives, two computers, one cloud account D) Three projects, two backups each, one master list

7. Cloud sync (without version history) is not, by itself, backup because:

A) Cloud storage is too slow for audio B) Sync's job is making every device match — so it propagates deletions and corruptions as faithfully as it propagates songs C) Sync services compress WAV files into MP3s D) Sync only works on project files, not audio

8. The consolidated feedback round — all notes, one deduplicated document, against one named version — exists because the alternative (the drip-feed) causes:

A) Hurt feelings B) Slower uploads C) Work against a moving target, colliding and contradictory notes, and a receiver who must guess when the trickle ends D) Larger file sizes

9. The anatomy of a protocol-grade note is:

A) A compliment, a criticism, and a compliment B) Timestamp — element — observation, with any suggestion clearly labeled as a guess C) A paragraph of context, then the note D) The fix you want, stated as an order

10. The reference mix travels with every send package because:

A) It proves you did the work B) Words like "spacious" and "intimate" mean something different in every head, but a rough mix is unambiguous about every balance and intention — including ones you don't know you have C) Collaborators expect a free song D) It pads the zip to a respectable size

11. Deciding wet versus dry for a multitrack print, the chapter's doctrine is:

A) Print everything dry — processing is the mixer's job B) Print everything wet — it's your sound C) If the processing is part of the instrument's identity, print it; if it's the mix's shared space, print it separately (and nothing from the 2-bus, ever) D) Flip a coin and note the result

12. The baton rule states:

A) The producer always holds the session B) At any moment exactly one person holds the editable project; everyone else works on prints, and the baton is handed explicitly C) Sessions should be co-edited live for speed D) Whoever started the song owns the session forever

13. Which of these does NOT belong in the README of a send package?

A) BPM, key, and sample rate/bit depth B) "All files start from 0:00" C) The file list with one-line notes, and what you want from the recipient D) Your complete plugin list with the serial numbers for each license

14. This book's definition of the producer is:

A) The person who made the beat B) The person who owns the studio C) The person responsible for the record being good — and being finished: vision, decisions, logistics, psychology D) The person who pays for the session

15. Three listeners independently flag 1:12, with three different explanations. The chapter's rule:

A) Ignore all three — they contradict each other B) Implement all three suggested fixes C) Trust the convergence (something is true at 1:12) and hold the diagnoses loosely — go diagnose it yourself D) Trust whichever listener has the best monitors

Section 2 — True/False, with Justification (2 points each — the justification is the point)

16. "Stems" and "multitracks" mean the same thing, and asking which one someone wants is pedantic.

17. Printing your multitracks through the limiter on your master bus is good practice, because the files arrive sounding finished.

18. A considerate collaborator sends each note the moment they think of it, so nothing gets forgotten.

19. If your rough mix is embarrassing, it's better to send a well-written description of your intent instead.

20. Declining a collaborator's note — with a stated reason tied to the song's goal — is a legitimate outcome of a feedback round.

Section 3 — Short Answer (4 points each)

21. You're sending your song to an outside mix engineer. List the complete send package, item by item, with one reason each.

22. Name two independent mechanisms by which a session that opens perfectly today will fail in ten years, and list what goes into the time capsule that makes the failure survivable.

23. State the three rules for giving useful feedback, plus the two delivery moves that make notes land.

24. A producer must repeatedly judge "one more take, or move on?" Describe the signs on each side of that decision, and the cheapest way to ask for the take after "we got it."

Section 4 — Applied Scenario (8 points)

25. You're asked to rescue a stalled long-distance collaboration between a producer and a singer. The wreckage, as reported: the singer received forty-one files in which "every part starts at its own first note," so nothing lines up; the files turned out to be 44.1 kHz against the producer's 48 kHz session, documented nowhere; feedback has arrived as twenty-three texts spread over two weeks, several contradicting each other; there are now two diverging projects — final_MINE on the producer's laptop and FINAL_singer_edit on the singer's — because both kept working; the only "backup" was a sync folder without version history, through which an accidental deletion of the chorus takes propagated to every device; and the singer has stopped sending notes entirely, because the producer answered her last batch with a point-by-point defense of every choice. Both parties still want the song. Write your triage: the order you'd work, what each fix involves, which damage may be unrecoverable, and the one-line prevention rule each failure teaches.

Scoring