User's Manual
Table Of Contents
- A Letter from Bill Putnam Jr.
- Introducing Apollo Solo USB
- Getting Started
- Hardware Controls & Connectors
- Apollo Solo USB System Overview
- Working With Apollo Solo USB
- Essential Apollo Solo USB Concepts
- Setting the DAW to use Apollo Solo USB I/O
- Accessing Apollo Solo USB’s I/O in the DAW
- Input Monitoring with the DAW
- Using Console with the DAW
- UAD Plug-Ins: Console versus DAW
- Virtual I/O
- Using Apollo Solo USB for System Sound I/O
- Using Apollo Solo USB Without Audio Software
- Console Overview
- What is Console?
- Console Functions
- Global Functions
- When To Use Console
- Interactions Between Console and Apollo Solo USB
- Accessing Console
- Console Layout
- Global Window Elements
- Meter Bridge Overview
- Info Bar Overview
- Current Bank Overview
- View Column Overview
- Monitor Column Overview
- Channel Strips Overview
- Console Plug-In Inserts Overview
- Insert Effects Overview
- Popover Windows
- HP Cue Overview
- Sends Overview
- Console Sessions Overview
- Console Settings Overview
- Multiple Undo/Redo
- Keyboard Focus & Control
- Adjusting Console Controls
- Controls Shortcuts
- Keyboard Shortcuts
- Console Reference
- Console Plug-In Inserts
- Insert Types
- Inserts Signal Flow
- Inserting UAD Plug-Ins
- Removing UAD Plug-Ins
- Editing UAD Plug-Ins
- Insert Assign Popover
- Inserts Display
- Insert State Indicators
- Insert Hover Options
- Insert Options Menu
- Channel Insert Effects
- Plug-In Editor Window
- Channel Strips
- Presets Manager
- Presets Manager Popover
- Save Preset Popover
- Console Settings
- Unison
- Console Recall Plug-In
- UAD Meter & Control Panel
- Using UAD Plug-Ins
- Tempo Sync
- UA Account & Store
- Latency & Apollo Solo USB
- Device Drivers
- Troubleshooting
- Glossary
- Specifications
- Hardware Block Diagram
- Universal Audio History
- Notices
- Technical Support

Apollo Solo USB Manual Console Reference 125
Console Sessions
The Sessions controls provide methods for managing complete Console configurations
as session preset files. When a Console session file is saved, the current Console
configuration is written to disk.
When a session file is subsequently reloaded, Console is returned to the exact same
configuration state, regardless of any changes to Console that were made in the interim.
Content of Session Files
Console session files contain most, but not all, Console settings. The specific parameters
saved and not saved are listed below:
Saved – All knob, slider, and menu values, all inserted UAD plug-ins, settings contained
within the plug-ins, input labels, show/hide status, and settings in Console Settings
window (except those listed below).
Not saved – Monitor Gain, Sample Rate, and Cue Outputs settings are global parameters
that are not session-specific. Most of these settings are managed in the Console Settings
window.
Default Session Files Location
By default, session files are saved to, and loaded from, the user’s home folder at:
• C:\Users\UserName\AppData\Roaming\Universal Audio\Sessions
Although session files can be saved to (and loaded from) any location on disk, using the
default location offers the most convenience, because Console always uses this location
for the Sessions Manager window and also Open/Save dialogs presented by the OS.
Note: Session files must reside in the default location to appear in session lists
within Console.
Sessions Sub-Folders
The Session Files folder can contain one level of sub-folders for additional session
organization capability. The contents of sub-folders (if any) are displayed in the SUB-
FOLDER column in the Sessions Manager Popover when a folder in the SESSION column
is selected.
Session Files Suffix
Console’s session files have the “.uadmix” suffix. The suffix is added to session files
automatically when saving to disk; however, the suffix is not displayed in the file save
dialog (the suffix should not be manually typed when saving a session file).
Note: Without the .uadmix suffix, the session files will not be visible in the
“Open” file dialogs or the Sessions menu, and they won’t be opened when they
are double-clicked in the OS file system.