# Pro Tools for Dolby Atmos Music Production: instructor pacing guide

## Delivery model

This is a 26-30 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

- Pro Tools Studio or Ultimate with the supported internal Dolby Atmos renderer configuration.
- A pre-calibrated institutional 7.1.4 room and approved binaural headphone monitoring path.
- Basic stereo mixing concepts including gain, buses, automation, EQ, dynamics, and stems.
- At least 30 GB of working storage; students must not modify room calibration or monitor routing.
- 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: Understand the immersive production model

**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:**
- Trace audio and metadata from Pro Tools to final render.
- Distinguish beds, objects, groups, and re-renders.
- Describe what binaural monitoring can and cannot predict.

**Checkpoint:** Submit the role map, signal-and-metadata trace, four-format listening notes, and selected spatial concept.

**Common diagnostic prompts:**
- A student equates height with quality: Return to musical hierarchy and compare a focused static placement against constant movement at matched level.
- Binaural and speakers disagree: Treat them as different renders; inspect object positions, binaural modes, decorrelation, phase, and room-dependent cues.
- An object appears to vanish in a downmix: Check level, masking, phase, divergence, routing, and the selected re-render rather than assuming metadata failed.

## Module 2: Configure, route, and prove the Atmos session

**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:**
- Configure the internal renderer and monitor format safely.
- Route beds and objects with unambiguous names.
- Detect missing, duplicated, or incorrectly mapped paths.

**Checkpoint:** Submit the routed session, I/O and renderer record, verification-pulse report, and repaired-fault log.

**Common diagnostic prompts:**
- Object controls are unavailable: Verify the track output, object mapping, renderer mode, supported track width, and object assignment.
- Signal sounds twice: Check simultaneous bed and object feeds, sends, live and printed paths, and monitor returns.
- A monitor format is silent: Trace renderer output selection, monitor path, hardware output, and lab controller state without changing calibration.

## Module 3: Prepare stems and build a stable spatial foundation

**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:**
- Prepare phase-coherent stems from a common start.
- Choose beds or objects based on musical function.
- Establish a static immersive balance that works before automation.

**Checkpoint:** Submit the static mix milestone, bed/object decision log, four-format comparison, and anchor strategy diagram.

**Common diagnostic prompts:**
- The mix feels empty at the front: Restore strong frontal anchors and evaluate whether too many supporting elements were moved away simultaneously.
- Stereo downmix becomes narrow or hollow: Inspect phase, decorrelated widening, surround contribution, and low-frequency routing.
- Height feels detached from the song: Use shared timbre, ambience, or section logic and reduce isolated overhead novelty.

## Module 4: Compose movement, depth, and section contrast

**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:**
- Automate position with musically meaningful timing.
- Create section contrast using density, width, depth, and height.
- Preserve focal stability while secondary elements move.

**Checkpoint:** Submit pre-automation and automated versions, an annotated section map, and a motion audit listing purpose and translation result.

**Common diagnostic prompts:**
- Object jumps at a boundary: Inspect automation breakpoints, coalescing, clip boundaries, suspended parameters, and the value immediately before the transition.
- Movement is obvious on speakers but absent binaurally: Review path, binaural mode, trajectory speed, spectral content, masking, and whether the cue relies mainly on vertical localization.
- The chorus is bigger but less focused: Restore anchors, reduce simultaneous motion, and separate width/envelopment from focal level.

## Module 5: Translate, meter, and quality-control the mix

**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:**
- Run repeatable multi-format listening comparisons.
- Identify renderer, arrangement, and processing causes of translation failures.
- Document loudness and peak behavior for the master and re-renders.

**Checkpoint:** Submit the four-format scorecard, meter evidence, blind-review notes, fault-resolution log, and revised mix milestone.

**Common diagnostic prompts:**
- Integrated values differ unexpectedly: Confirm render selection, complete duration, meter reset, trim/downmix settings, and whether monitor control alters the measured path.
- Mono loses a central element: Inspect polarity, stereo widening, decorrelation, object/re-render assignment, and shared processing.
- Binaural playback is tiring: Reduce persistent near-ear movement or brightness, revisit binaural modes, and create calmer spatial rest points.

## Module 6: Export ADM, re-renders, and delivery evidence

**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:**
- Export an ADM BWF with the required programme range.
- Create named re-renders that match the delivery brief.
- Verify the master by import, playback, metadata inspection, and documented QC.

**Checkpoint:** The capstone package is the checkpoint: ADM BWF, required re-renders, session, configuration record, translation matrix, QC report, and walkthrough.

**Common diagnostic prompts:**
- ADM re-import has missing elements: Compare object mapping, active paths, export range, mute/solo states, unsupported routing, and export log.
- Re-render does not match live monitoring: Confirm source session version, renderer state, trim/downmix, re-render definition, monitor-only processing, and bounce selection.
- Master tail is truncated: Extend the explicit export range for reverberation and object automation returns, then re-verify all deliverables.

## 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.