UAD Console & Apollo Stack

Studio Foundation · Configuration Reference · Last updated: April 19, 2026

The Goal

Before building any Cubase templates or recording a single note for TALISMAN, establish a properly optimized studio foundation — configuring the UAD Apollo stack correctly from the ground up, establishing proper gain staging across all 42 inputs, and setting up the monitoring environment so that latency, headroom, and signal flow are all working optimally together.
Why this matters: The studio has never been properly optimized from a signal flow perspective. Proper Console configuration unlocks zero-latency monitoring, Realtime UAD Processing, correct gain structure, and a monitoring environment that makes mixing and recording decisions trustworthy rather than accidental.

Key Concepts

Target Recording Level
−18 dBFS average
Preserves headroom for transients
Buffer Size
128 samples @ 48kHz
~2.7ms latency — do NOT increase sample rate
UAD Console Role
Zero-latency hardware monitoring
Live performance, direct monitoring, Realtime UAD Processing
Cubase Role
Recording, production, mixing
Full plugin access — Waves, Arturia, Cherry Audio, GForce, iZotope etc.
The Fundamental Relationship: Console acts as a parallel zero-latency mixer running alongside Cubase simultaneously. Console replaces the DAW's software input monitoring for any instrument being played live in real time. Sequenced/automated instruments run through Cubase without latency concern. UAD plugins handle monitoring and tracking effects in Console only.
Critical Reminder: Do NOT work from highlights or assumptions. Full manual understanding first, then decisions based on complete picture of capabilities. The OSCar40 lesson applies here.

Apollo Stack

42 inputs total

UnitModelLocationDSPRoleKey Inputs
A Apollo 8Apollo 8 QUADRack #1, 3UQUAD CoreMonitor UnitMoog One, Super 6, SH-1, CS-5, Prodigy, Odyssey MkI
B Apollo 16 #1Apollo 16 MkII QUADRack #1, 5UQUAD CoreExpanderIridium, M1R, D-550, K4r, TVS-1, Pro One, 001, 002R/K5000R, 100f, System 100
C Apollo 16 #2Apollo 16 MkII QUADRack #1, 7UQUAD CoreExpanderDMNO, OSCar40, MiniKorg 700, 3rd Wave, E4XT, SM10 Mix, Hydrasynth
D Apollo TwinApollo Twin MkII DUOMain deskDUO CoreExpanderSA47 mic (Combo 1), CP-70B (Combo 2)
UAD-2 Satellites #1 & #2Rack #1, 12UOCTO Core ×2DAW OnlyCannot be used for Console Realtime UAD Processing — Cubase only

DSP Configuration

Set April 4, 2026

UnitDSP PairsVirtual Ch.Cores
A Apollo 824QUAD
B Apollo 16 #124QUAD
C Apollo 16 #224QUAD
D Apollo Twin20DUO
SettingValueNotes
Input Delay CompensationOFFSingle source workflow — no multi-mic phase alignment needed
DSP Pairing Latency Cost+69 samples per inputOnly incurred when DSP is actually paired, not just when PAIRS > 0
Cue Bus Count2Sufficient for current workflow
Alt Count / Digital Mirror0 / OFFMixCubes managed as Cubase output bus — not Console ALT

Hardware Panel Settings

Console Settings → Hardware

SettingValueNotes
Sample Rate48 kHzDo not change — increasing sample rate worsens latency
Clock SourceInternalApollo manages all inter-unit clocking via Thunderbolt automatically
Input Delay CompensationOFFSingle source workflow — no multi-mic phase alignment required
Cue Bus Count2Default — sufficient
Alt Count0MixCubes on dedicated Cubase bus, not Console ALT
Digital MirrorOFFLeave off
Mon Output Gain (A8)ONApollo 8 monitor unit
Mon Level (A8)14 dBuVerify during gain staging session
Output Reference Levels (A8)+4 dBu allCorrect for pro gear throughout
Line Input Gain (A8)ON — Moog One, Super 6Preamp channels only

Options Panel Settings

Console Settings → Options

SettingValueNotes
MeteringPre-FaderShows actual incoming signal level — correct for gain staging
Clip Hold3 secDefault — fine
Peak Hold3 secDefault — fine
Modifiers Timeout6Default — leave
Controls ModeLinearCorrect for precise gain staging — drag up/down

Virtual Channel Routing

I/O Matrix — configured April 4, 2026

UnitDirectionChannelsNamesPurpose
AOUT Console → DAWVirt 1–4A8 Virt Out L/R/3/4Capture Console mix with UAD effects printed into Cubase
AIN DAW → ConsoleVirt 1–4A8 Virt In L/R/3/4Route Cubase soft synth / ACE Studio into Console for Realtime UAD Processing
BOUT Console → DAWVirt 1–416-1 Virt Out L/R/3/4Capture Console mix from 16 #1 instruments
COUT Console → DAWVirt 1–416-2 Virt Out L/R/3/4Capture Console mix from 16 #2 instruments
DNoneTwin has no virtual channels — CP-70B and mic only, no DAW routing needed

Apollo 8 Output Labels

I/O Matrix — named April 4, 2026

OutputLabelDestination
Mon LMon L (HS8)Yamaha HS8 left
Mon RMon R (HS8)Yamaha HS8 right
Line 1MixCube LAvantone MixCube left — Cubase bus
Line 2MixCube RAvantone MixCube right — Cubase bus
Line 3E4XT In LE-mu E4XT Ultra sample input L
Line 4E4XT In RE-mu E4XT Ultra sample input R
Line 53rd Wave InGroove Synthesis 3rd Wave sample input (mono)
Line 6CP-70B RokitCP-70B dedicated KRK Rokit 5 — Cubase bus
Line 7Available 7
Line 8Available 8

CP-70B Console Channel

Apollo Twin MkII — Combo Input 2 — Configured April 2026

Signal Chain — Console (HS8 monitoring path)
CP-70B → Twin Combo Input 2 → UA 610-B → Brigade Chorus → EMT 140 (35% wet) → UAD MON

Monitor path only (UAD MON). IO Preset: Master Setup. Brigade Chorus = renamed CE-1 emulation (Roland license expired) — not upsampled, safe for Console Realtime monitoring. Twin DUO configured with DSP Pairs: 2 — both cores used for this channel, supports 3 stacked plugins.

CP-70B Rokit 5 Monitoring — Cubase Output Bus
CP-70B track in Cubase → Inspector Routing → Output: "CP-70B Rokit" → Apollo 8 Line 6

The Rokit feed is assigned in the Cubase track inspector, not in Console. Both monitors are active simultaneously — Console handles HS8s via UAD MON, Cubase handles Rokit via dedicated output bus. The CP-70B Rokit output bus must be set in the Cubase channel inspector for each session or saved in the Writing Session template.

Key discovery April 19, 2026: Cue Bus outputs in Console cannot be targeted to a specific input channel — they route a mix bus, not a single source. For single-instrument alternate output routing, the correct method is a dedicated Cubase output bus assigned to the target Apollo line output. This applies to CP-70B Rokit, MixCubes, E4XT inputs, and 3rd Wave input.

Monitoring & Sampling Workflows

Alternate Output Routing — General Method

All alternate output routing (beyond the main mix) is handled via dedicated Cubase output buses assigned to specific Apollo 8 line outputs. The method is identical for all destinations:

In Cubase: open the instrument track Inspector → Routing section → set Output to the desired named bus (CP-70B Rokit, E4XT In L/R, 3rd Wave In). The signal flows out of the corresponding Apollo 8 physical output.

Sampling Workflow — E4XT Ultra

Route instrument to E4XT for sampling
Source instrument track → Output: "E4XT In L" + "E4XT In R" → Apollo 8 Lines 3/4 → E4XT sample inputs

Set source instrument track output to E4XT In L/R in Cubase inspector. E4XT SUB 1 L/R outputs feed a dedicated KRK Rokit pair directly — isolated monitoring of only what's playing through the sampler, independent of Apollo. No Apollo involved in the E4XT monitoring path.

Wavetabling Workflow — 3rd Wave

Route instrument to 3rd Wave for wavetable import
Source instrument track → Output: "3rd Wave In" → Apollo 8 Line 5 → 3rd Wave sample input (mono)

3rd Wave accepts a mono input for wavetable capture. Different workflow from E4XT sampling — wavetable import rather than traditional multi-sample recording.

Planned Cubase Templates

TemplatePurposeDefault Routing
Writing SessionComposition and productionAll instruments → main mix. CP-70B → Rokit bus active.
Sampling TemplateE4XT multi-sample captureSource instruments pre-routed to E4XT In L/R. E4XT record-armed.
Wavetabling Template3rd Wave wavetable importSource instruments pre-routed to 3rd Wave In. Mono.

Key Technical Discoveries

IO Preset files are plain XML — live at Users/[UserName]/Documents/Universal Audio/IOPresets/ with .uaudio extension. Directly editable in TextEdit for channel reordering. The only reliable way to reorder channels in a multi-unit setup.
Cascade function is unreliable with mouse — designed for touchscreen swipe interaction. Use the TextEdit method above for any channel reordering instead.
Console mixer display order is independent of I/O Matrix order — cosmetic only. I/O Matrix order is what Cubase sees and is what matters functionally.
UAD Satellites cannot process Console Realtime UAD plugins — Satellite DSP is exclusively for DAW-loaded plugins. Console Realtime UAD Processing uses only the DSP inside the Apollo units.
Channel DSP Pairing adds 69 samples latency across ALL inputs when active — even channels with no plugins. Minimize DSP Pairs setting to avoid unnecessary latency tax on unused channels.
Apollo Thunderbolt Software Manual PDF — still live at https://media.uaudio.com/support/manuals/11.4.0-2roV4n/Apollo+Software+Manual+-+Thunderbolt.pdf. Console Manual itself is web-only at help.uaudio.com.
Console saves require Master Setup — changes are not automatically saved on quit. Always save via Master Setup before quitting Console.
Cue Bus outputs route a mix bus, not a single source — cannot be used to send a single instrument channel to an alternate physical output. Use dedicated Cubase output buses for all single-instrument alternate routing. (Discovered April 19, 2026.)

Session Sequence

01
Console Hardware Panel & I/O Matrix ✓
02
Console mixer gain staging & CP-70B channel setup — pending
03
Cubase audio connections setup
04
External instruments configuration
05
Full Cubase template build
Next Session Trigger: Fresh chat → fetch index → "UAD Console setup session — Hardware panel and I/O Matrix complete, ready for mixer gain staging and CP-70B channel setup."

Manual References

PDF — fetchableApollo Thunderbolt Software Manual v11 Web onlyUAD Console Manual Web onlyI/O Matrix Settings Panel Web onlyManaging Latency in UAD Console PDFApollo 8 Hardware Manual PDFApollo 16 MkII Hardware Manual PDFApollo Twin Hardware Manual