By the end of this module
- Navigate Tracks area, Library, Inspector, Mixer, editors, and transport.
- Set project tempo, meter, key context, and file organization.
- Write a composition intention with measurable constraints.
Core knowledge
Principles before controls
A brief defines a function
Composition supports an audience, action, story, performer, or listening context. Mood words alone are not enough. Identify what must change over time.
Constraints generate choices
Duration, instrumentation, tempo range, meter, tonal center, density, and delivery can focus invention instead of limiting it.
Logic separates regions from sources
Regions can be moved, looped, shortened, transposed, and edited while preserving underlying MIDI or audio data.
Project setup is compositional
Tempo map, bar structure, markers, track roles, and sound palette shape what is easy to imagine and revise.
Guided build / approximately 90-120 minutes
Build it in the application
- 1
Read the Signal at Dawn brief and identify audience, dramatic change, exact duration, required deliverables, exclusions, and rights limits.
- 2
Create the standard folders and a new Logic project at the supplied sample rate inside 03_PROJECT.
- 3
Tour Tracks area, control bar, Library, Inspector, editors, Mixer, Smart Controls, browsers, and lists using the interface map.
- 4
Set an initial tempo, meter, key context, cycle range, count-in, and project end that support the brief.
- 5
Create role-based tracks for pulse, bass, harmony, lead, texture, transition, and optional recorded material.
- 6
Add arrangement markers for opening, development, contrast, return, and resolution, assigning provisional bar lengths.
- 7
Audition a limited palette and commit to no more than six principal sound sources for the first draft.
- 8
Write a 120-word intention naming the musical change, focal element, primary contrast, and evidence of completion.
- 9
Save an EMPTY_MAP milestone before recording notes.
Independent challenge / 45-60 minutes
Prove the principle
Create two contrasting project maps for the same brief using different tempo, meter, and palette constraints. Select one without composing a full section.
Portfolio checkpoint
Evidence to retain
Submit the empty mapped project, intention statement, palette list, and a screenshot identifying the main Logic work areas.
Store this evidence in 01_ADMIN/checkpoints/module-1 and include it in the final decision log.
Failure modes
Diagnose before retrying
Playback continues beyond the intended duration
Set and verify the project end marker, cycle region, and any trailing regions or automation.
A region changes when tempo changes
Identify whether it is MIDI, Apple Loop, Flex-enabled audio, or absolute-time material and choose the intended behavior.
The palette becomes unmanageably large
Return to role-based tracks and replace rather than accumulate similar sounds.
Working vocabulary
Terms you must be able to explain
- region
- A movable block in the Tracks area that references MIDI or audio content.
- inspector
- Contextual controls for selected tracks, regions, and channels.
- arrangement marker
- A named formal section that can organize and move groups of regions.
- tempo map
- Tempo events defining musical speed over project time.
Primary sources
Verify current behavior
Lesson reviewed 2026-07-13. Verify menus and shortcuts against the lab release.