# Ableton Live for Electronic Music Composition: instructor pacing guide

## Delivery model

This is a 24-28 hours college-level intensive for students beginning with no application-specific experience. Students complete the 75-minute Professional Media Workflow Foundation first. Module checkpoints are formative; the completed portfolio is assessed with the 100-point rubric.

## Lab readiness

- Current Ableton Live 12 Standard or Suite in the institution lab.
- Headphones or lab monitors; a MIDI controller is helpful but not required.
- At least 15 GB of working storage and no unauthorized sample libraries.
- No previous Ableton, synthesis, or music-production experience is required.
- Create one clean student account and complete every guided build before release.
- Publish the exact tested application version, workspace/keymap assumptions, storage location, and support escalation route.
- Provide captions and transcripts for demonstrations, text alternatives for diagrams, and additional time or alternate input methods where required.

## Module 1: Think in clips, scenes, tracks, and devices

**Student workload:** 3 hours

**Before class or release:** Verify the module diagram, application version, required source media, storage path, and checkpoint folder. Reproduce the guided build on a clean lab account.

**Suggested pacing:** 20 minutes retrieval and orientation; 30 minutes principle instruction; 30 minutes annotated demonstration; 90-120 minutes guided build; 45-60 minutes independent challenge; 15 minutes checkpoint packaging and reflection.

**Outcomes:**
- Explain how Session and Arrangement Views share tracks but hold different clip timelines.
- Configure audio, MIDI, folders, and recording behavior.
- Build a role-based Session View sketch with a defined project intention.

**Checkpoint:** Submit the collected Live Project, signal-chain trace, Session/Arrangement explanation, and scene-map screenshot.

**Common diagnostic prompts:**
- A clip is visible but not heard: Trace clip launch state, track activator, monitoring, device chain, mixer, routing, crossfader assignment, and Main output.
- Arrangement is greyed out during playback: Session clips have taken control; use Back to Arrangement deliberately after deciding which timeline should play.
- Samples are missing on another computer: Use Manage Files and Collect All and Save, then test the project from a different path.

## Module 2: Program rhythm and build groove

**Student workload:** 3.5 hours

**Before class or release:** Verify the module diagram, application version, required source media, storage path, and checkpoint folder. Reproduce the guided build on a clean lab account.

**Suggested pacing:** 20 minutes retrieval and orientation; 30 minutes principle instruction; 30 minutes annotated demonstration; 90-120 minutes guided build; 45-60 minutes independent challenge; 15 minutes checkpoint packaging and reflection.

**Outcomes:**
- Build and route a Drum Rack pattern.
- Use timing and velocity to create a controlled groove.
- Develop pattern identity across multiple scenes.

**Checkpoint:** Submit the Drum Rack, five derived clips, pre/post groove comparison, resampled texture, and annotated rhythm role map.

**Common diagnostic prompts:**
- The beat feels unstable: Keep core anchors deterministic and reduce probability, microtiming, or competing syncopation on structural events.
- Groove changes the wrong notes: Adjust groove timing/velocity amounts, use separate clips, or commit and edit only selected events.
- Drum Rack clips overload the Main: Balance pad chains, review choke behavior, remove duplicate layers, and preserve headroom before bus processing.

## Module 3: Shape synthesis, samples, and warped audio

**Student workload:** 4 hours

**Before class or release:** Verify the module diagram, application version, required source media, storage path, and checkpoint folder. Reproduce the guided build on a clean lab account.

**Suggested pacing:** 20 minutes retrieval and orientation; 30 minutes principle instruction; 30 minutes annotated demonstration; 90-120 minutes guided build; 45-60 minutes independent challenge; 15 minutes checkpoint packaging and reflection.

**Outcomes:**
- Explain source, filter, amplifier, envelope, and modulation stages.
- Choose an appropriate warp mode and correct timing without unnecessary damage.
- Build a playable Instrument Rack with meaningful macros.

**Checkpoint:** Submit the rack, macro map, warp-mode comparison, three designed sounds, and source/transformation rights note.

**Common diagnostic prompts:**
- Warped transients smear: Use fewer markers, align true transients, select a suitable mode, and avoid extreme local stretching.
- Bass changes level across notes: Review filter resonance, key tracking, oscillator phase behavior, envelope, velocity mapping, and monitoring room modes.
- Macros produce unusable extremes: Reduce mapped ranges, invert or scale relationships deliberately, and test every combination at controller limits.

## Module 4: Improvise scenes into an arrangement

**Student workload:** 3.5 hours

**Before class or release:** Verify the module diagram, application version, required source media, storage path, and checkpoint folder. Reproduce the guided build on a clean lab account.

**Suggested pacing:** 20 minutes retrieval and orientation; 30 minutes principle instruction; 30 minutes annotated demonstration; 90-120 minutes guided build; 45-60 minutes independent challenge; 15 minutes checkpoint packaging and reflection.

**Outcomes:**
- Design scenes with compatible and contrasting clip combinations.
- Perform and capture a Session sequence.
- Convert performance evidence into a readable Arrangement.

**Checkpoint:** Submit the Session map, three performance captures, selected Arrangement, transition notes, and decision log.

**Common diagnostic prompts:**
- Arrangement keeps returning to Session clips: Stop or deactivate Session clips and use Back to Arrangement only when the linear timeline should regain control.
- Transitions happen late: Review global and clip quantization, launch timing, scene preparation, and whether the performance gesture anticipates the boundary.
- Follow actions create incoherent combinations: Limit the source group, probabilities, and allowed transitions; keep formal anchors outside the generative system.

## Module 5: Develop transitions, automation, and mix hierarchy

**Student workload:** 3.5 hours

**Before class or release:** Verify the module diagram, application version, required source media, storage path, and checkpoint folder. Reproduce the guided build on a clean lab account.

**Suggested pacing:** 20 minutes retrieval and orientation; 30 minutes principle instruction; 30 minutes annotated demonstration; 90-120 minutes guided build; 45-60 minutes independent challenge; 15 minutes checkpoint packaging and reflection.

**Outcomes:**
- Use automation to create phrase and section direction.
- Build transitions from existing material.
- Establish a controlled mix with useful groups and returns.

**Checkpoint:** Submit energy map, grouped and routed set, two transition constructions, automation audit, and three-system listening notes.

**Common diagnostic prompts:**
- Automation appears but does not play: Check automation mode, Re-Enable Automation, clip versus track envelopes, device state, and Arrangement Override.
- The drop lacks impact despite being louder: Create contrast before the arrival through subtraction, register, tension, and spectral space rather than only gain.
- CPU overload causes clicks: Freeze tracks, increase buffer for mixing, remove redundant devices, inspect oversampling, and avoid printing glitches into resamples.

## Module 6: Finish, collect, export, and perform the track

**Student workload:** 3 hours plus capstone work

**Before class or release:** Verify the module diagram, application version, required source media, storage path, and checkpoint folder. Reproduce the guided build on a clean lab account.

**Suggested pacing:** 20 minutes retrieval and orientation; 30 minutes principle instruction; 30 minutes annotated demonstration; 90-120 minutes guided build; 45-60 minutes independent challenge; 15 minutes checkpoint packaging and reflection.

**Outcomes:**
- Complete a translation-aware final mix.
- Collect a portable Live Project and export aligned deliverables.
- Demonstrate the track's compositional system in a short performance.

**Checkpoint:** The capstone package is the checkpoint: collected Project, master, stems, performance capture, rights manifest, QC report, and walkthrough.

**Common diagnostic prompts:**
- Collected project still misses plugins: Differentiate samples from devices; freeze or bounce approved compatibility tracks and document required third-party versions.
- Stem sum differs from the master: Review Main processing, return routing, sidechains, group processing, normalization, and stem export method.
- Export contains silence or wrong range: Set Arrangement start/end explicitly and check locator, loop, selection, and render settings before every version.

## Assessment calibration

Before marking, score two sample portfolios independently. Discuss any criterion differing by more than five points, revise the local examples, and retain the common rubric language. Do not reward expensive equipment, preset choice, or speed where the stated outcome is judgment, organization, delivery, or evidence.

## Completion gate

A portfolio is not complete until the native project opens on a second lab system, required outputs meet the specification, the final master has been inspected outside the timeline, known limitations are documented, and the student can explain the workflow in five minutes.