Prepare stems and build a stable spatial foundation

Clean, group, gain, and balance the supplied production before adding movement, then establish a coherent front, surround, and height foundation.

By the end of this module

  • 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.
Six-stage workflow diagram for Prepare stems and build a stable spatial foundation.
Use this workflow to keep technical operations connected to editorial or musical decisions.

Core knowledge

Principles before controls

A weak stereo mix does not become strong in space

Correct timing, noise, phase, gain, arrangement, and spectral conflicts before spatial placement adds complexity.

Anchors create orientation

Lead vocal, kick, snare, bass, or other focal elements need stable perceptual roles even when support elements widen or move.

Objects should earn independence

Use an object when individual position, movement, binaural behavior, or re-render control matters.

Static placement is a complete decision

An immersive mix may feel deep and enveloping without constant automation. Start with stable placement and add motion only for structure.

Guided build / approximately 90-120 minutes

Build it in the application

  1. 1

    Audit stem starts, durations, channel formats, silence, noise, clipping, phase, and processing assumptions.

  2. 2

    Build a stereo-compatible static balance using clip gain and submix levels before assigning depth or height.

  3. 3

    Choose an anchor strategy for lead vocal, rhythm section, and principal harmonic element.

  4. 4

    Place stable ensemble and shared ambience material in suitable bed or multichannel paths.

  5. 5

    Promote only elements requiring independent localization or metadata to objects and document the reason.

  6. 6

    Use front width, side/rear support, and restrained height to create depth while preserving a readable frontal image.

  7. 7

    Check low-frequency and strongly correlated elements for stability through stereo and mono renders.

  8. 8

    Compare the static Atmos balance with the stereo reference at matched loudness and revise missing musical relationships.

  9. 9

    Save a STATIC milestone that remains available throughout later automation work.

Independent challenge / 45-60 minutes

Prove the principle

Build two static balances: conservative translation-first and enveloping listener-inside. Select one using evidence from 7.1.4, binaural, stereo, and mono.

Portfolio checkpoint

Evidence to retain

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

Store this evidence in 01_ADMIN/checkpoints/module-3 and include it in the final decision log.

Failure modes

Diagnose before retrying

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.

Working vocabulary

Terms you must be able to explain

anchor
A stable element that establishes focus or orientation.
decorrelation
A reduction in signal similarity used to create width, with possible downmix consequences.
common start
A shared timeline origin that keeps stems aligned.
static balance
A mix state created without time-varying panning or level automation.

Primary sources

Verify current behavior

Lesson reviewed 2026-07-13. Verify menus and shortcuts against the lab release.

Translate this page

Machine translation provided by Google Translate, on Google’s servers. We do not check these translations and they will get technical terms wrong. The English page is the authoritative one. Following a link sends this page’s address to Google. Your browser may also offer to translate this page itself, which keeps the request on your device.