Mastering Ambisonic Audio in Cubase

Ambisonic mastering isn't a scaled-up version of stereo mastering. You're not finishing a fixed two-speaker mix — you're preparing a soundfield that will be decoded multiple ways downstream: binaural for headphones, speaker arrays from 5.1 up through 7.1.2, and often a stereo fold-down for previews or fallback playback. Cubase has native Ambisonics support built into its bus routing, panning, and monitoring chain, which makes it a workable environment for this, but the workflow looks different from a standard mastering session and it's worth understanding where the native tools stop and where you need to build around them.

Set Up an Ambisonics Bus

Start in Studio > Audio Connections, add an output bus, and set its format to Ambisonics rather than stereo or surround. Cubase natively handles first, second, and third-order Ambisonics buses and tracks (third order tops out at 16 channels). Confirm your channel ordering and normalization convention — ACN/SN3D is the modern standard, FuMa is the older convention — before routing anything in, since mismatched conventions between your source material, your bus, and your eventual delivery target won't throw an error; they'll just quietly produce a wrong-sounding decode.

Route your ambisonic stems, or sources panned through VST MultiPanner in Ambisonics mode, into a group track set to match your bus format. One practical quirk worth knowing early: cue sends don't work on Ambisonics channels, so if your session relies on cue mixes for collaborators, route those separately before committing to an all-Ambisonics signal path.

Why a Generic Mastering Chain Doesn't Belong on the Raw Bus

A normal stereo mastering chain — EQ, multiband compression, a brickwall limiter — assumes two channels that map directly to left and right ears. An Ambisonics bus is a set of encoded signals (W plus directional components) that only resolve into something audible once decoded. Insert a generic multiband compressor across all 4, 9, or 16 channels of that bus and you'll get inconsistent gain reduction per channel, which smears directionality and can partially collapse the soundfield on decode — often without an obvious red flag in the meters. Processing needs to either be built for the Ambisonics domain specifically, or applied to the W and directional components in a way that keeps their relative levels intact.

Splitting W From the Sphere

Cubase doesn't give you a native per-component insert point inside an Ambisonics bus channel, so the practical route is to freeze or export the bus down to its individual mono components (W, X, Y, Z, and higher orders if you're working beyond first order), then work on them as separate mono tracks. W behaves like a mono sum and can take broadband EQ and compression the way you'd treat a mono master bus. The directional components should get identical, linked gain-reduction treatment relative to each other — if you brighten or compress one of X, Y, or Z on its own, you're steering the soundfield, not mastering it. Once processing is done, reassemble the components into an interleaved Ambisonics file or route them back into the bus for final encode.

Monitor the Master Through a Binaural Decode

With the Ambisonics bus set as your Main Mix in Audio Connections and Control Room enabled, Cubase's Phones channel can auto-decode to binaural stereo using VST AmbiDecoder. In Preferences, under VST - Control Room, enable "Use Phones Channel as Preview Channel," then on the AmbiDecoder panel select Headphones as the output and choose an HRTF mode — Standard for Cubase's built-in algorithm, SOFA if you're monitoring against a personalized HRTF file, or the Facebook/YouTube modes if you want a decode check that matches how those platforms handle VR audio playback. If you'd rather monitor through a third-party binaural decoder that isn't built for the Phones channel slot, insert it on the Control Room Main channel instead.

Spot-Check a Speaker Decode Too

A master that sounds convincing binaurally can lose definition or balance on a loudspeaker decode, and vice versa — don't finalize on headphones alone. Control Room's Downmix Presets let you audition the same Ambisonics bus decoded to a 5.1 or 7.1.2-style layout without re-routing your session. While you're there, check a mono and stereo fold-down as well; low end doesn't localize well, and content that's panned aggressively into the sphere can produce phase cancellation once it's collapsed down to fewer channels.

Loudness and Headroom Before You Export

There's no single agreed LUFS standard for raw ambisonic delivery the way there is for stereo streaming or Dolby Atmos. Loudness-check the binaural or speaker decode rather than the raw B-format signal, since that's what a listener actually hears. Leave more true-peak headroom than you would on a stereo master — somewhere in the range of -3 to -6 dBTP going into final encode is a reasonable safety margin, since the decode math can generate peaks that weren't present in the unencoded signal.

Exporting the Final Master

Use Export Audio Mixdown with the Ambisonics bus as your source, and double-check the channel order and normalization convention against your delivery spec one more time before bouncing — this is the easiest place for a late-stage mismatch to slip through unnoticed. Keep an unprocessed archive of the raw ambisonic capture alongside your stems; re-rendering to a different order or a different decode target later almost always goes back to that untouched file rather than the mastered one.

Cubase Ambisonic Mastering Checklist

  • Ambisonics bus created with the correct order and channel convention (ACN/SN3D vs. FuMa) confirmed before routing
  • Processing applied to W and the directional components separately, not as a single blanket chain across the bus
  • Binaural decode checked via Control Room's Phones channel or an inserted third-party decoder
  • Speaker decode spot-checked using Downmix Presets, plus a mono and stereo fold-down check
  • Loudness and true-peak measured on the decoded output, with extra headroom left for encode-stage peaks
  • Unprocessed raw ambisonic file archived separately from the final master

If you'd rather have this handled end to end — mastering checked across binaural, speaker, and stereo fold-down decodes — Axis Ambisonic Lab offers ambisonic mastering and upmixing services for immersive audio projects.