By the end of this module
- Mix for musical hierarchy and translation.
- Export a master and aligned role-based stems.
- Package a clean Logic project with composition and QC notes.
Core knowledge
Principles before controls
Mixing reveals the composition
Balance, register, panorama, dynamics, and space should clarify roles and form rather than disguise unresolved arrangement.
Reference by function
Compare tonal balance, focal level, depth, and dynamics at matched loudness without copying another work.
Stems must reconstruct the approved result
Shared effects, bus processing, automation, and tails require deliberate stem design.
Reflection should name evidence
Explain how musical materials change, where the brief is met, what was revised, and what remains limited.
Guided build / approximately 90-120 minutes
Build it in the application
- 1
Finish arrangement edits before opening a dedicated mix milestone and remove muted experiments only from the copied final project.
- 2
Set static balance from focal role outward, then check mono and low-level playback before detailed processing.
- 3
Use EQ to resolve specific masking or resonance and dynamics to shape behavior, level-matching every comparison.
- 4
Build coherent depth with sends and shared spaces while retaining enough direct sound for definition.
- 5
Automate final section balances and transition tails, then listen through without touching controls.
- 6
Bounce a 24-bit WAV master and an approved listening copy from the exact project range.
- 7
Export aligned rhythm, bass, harmony, lead, texture, and effects stems including necessary tails and shared returns.
- 8
Import the master and stems into a blank verification project, reconstruct the balance, and inspect start, end, peaks, silence, and metadata.
- 9
Package the Logic project with assets, brief, rights note, composition map, QC report, and five-minute walkthrough.
Independent challenge / 45-60 minutes
Prove the principle
Ask a blind listener to describe the piece's form, focal material, strongest contrast, and ending. Revise one mismatch between intent and heard evidence.
Portfolio checkpoint
Evidence to retain
The capstone package is the checkpoint: Logic project, master, stems, composition map, decision log, QC report, and walkthrough.
Store this evidence in 01_ADMIN/checkpoints/module-6 and include it in the final decision log.
Failure modes
Diagnose before retrying
Stems sound different from the full mix
Check bus processing, sidechains, shared effects, master processing, automation, and whether returns were included consistently.
The master clips after bounce
Inspect overs, true peak, inter-sample behavior, normalization settings, and sample-rate conversion. Preserve headroom.
The mix is clear but emotionally flat
Return to dynamics, orchestration, phrase, and sectional contrast before adding broad mastering processing.
Working vocabulary
Terms you must be able to explain
- mix bus
- The principal path combining the project into its final channel format.
- stem
- A synchronized submix representing a defined musical role.
- masking
- Reduced audibility caused by competing energy in related times or frequencies.
- reference track
- A comparison recording used to evaluate defined characteristics at matched level.
Primary sources
Verify current behavior
Lesson reviewed 2026-07-13. Verify menus and shortcuts against the lab release.