How To Connect Two Apollo Interfaces

Okay, picture this: I’m in my tiny, sound-treated (read: foam-covered) room, staring at two beautiful Apollo interfaces. Both glistening under the dim light, promising audio nirvana. I had spent weeks justifying the second purchase to my bank account (and my partner, bless her heart). Now I had the power of double the preamps, double the DSP...double the potential for creative mayhem! But here's the kicker: I had absolutely no idea how to connect them. Talk about anticlimactic, right?

Turns out, I wasn't alone. Plenty of people find themselves in the same boat. You've invested in the Universal Audio ecosystem, wanting to expand your input count or leverage the power of combined DSP for those ridiculously demanding plugin chains. But the manual? Let's just say it's not exactly bedtime reading. So, fear not, fellow audio adventurer! This guide is for you. We're diving deep (well, maybe knee-deep) into the world of connecting two Apollo interfaces. No engineering degree required!

Why Bother Linking Apollos Anyway?

Before we get into the nitty-gritty, let's quickly address the "why." Why even bother connecting two Apollos? Isn't one enough? Well, my friend, the answer is a resounding NO! (Okay, maybe for some, one is enough, but where's the fun in that?). Here's the lowdown:

• More Inputs: This is the big one. Need to record a full drum kit? A whole band live? Two Apollos are your ticket to multichannel recording bliss. Suddenly, those six input interfaces feel a bit... limiting, don't they?
• Increased DSP Power: Universal Audio's UAD plugins are legendary, but they can be DSP hogs. Linking interfaces effectively doubles (or more, depending on the models) your available DSP, allowing you to run more plugins in real-time. Think reverb on every track, compression galore, and the ability to finally use that ridiculously CPU-intensive tape emulator.
• Flexible Routing: Connecting interfaces opens up a world of routing possibilities. Send different monitor mixes to different musicians, create complex effects chains that wouldn't be possible with a single unit, the possibilities are endless (almost).
• Future-Proofing: Buying a second Apollo isn't just about what you need now. It's about preparing for future projects. You never know when you'll need those extra inputs or that extra DSP horsepower. It's an investment in your creative potential!

So, yeah, linking Apollos is pretty awesome. Now, let's get to the fun part...

The Thunderbolt Connection: Your Bridge to Audio Valhalla

Okay, here's the core of the operation: Thunderbolt. Forget USB, forget FireWire (RIP). Thunderbolt is the only way to connect two Apollo interfaces and unlock their full potential. It's fast, it's reliable, and it's the key to making this whole thing work. (Unless you're using an Apollo Twin X Duo or Apollo Solo, then you may use Thunderbolt or USB depending on the model).

Think of it like this: Thunderbolt is the superhighway that carries all the audio data back and forth between your interfaces and your computer. The faster the highway, the more cars (audio signals) can travel on it simultaneously. Makes sense, right?

What You'll Need:

• Two Apollo Interfaces: (Duh!). Make sure they are compatible with Thunderbolt daisy-chaining. The Apollo Twin MkII, Apollo x6, x8, x8p, x16, and the Apollo 8, 8p, and 16 (Blackface) are all daisy-chainable.
• Thunderbolt Cables: You'll need at least one Thunderbolt cable (preferably two - one to connect the first Apollo to your computer and another to connect the two Apollos together). Get good quality cables. Don't cheap out here. A dodgy cable can lead to dropouts, glitches, and general audio mayhem.
• A Thunderbolt Port on Your Computer: This might seem obvious, but double-check! Most modern Macs have Thunderbolt ports, but some older models (and some PCs) might not. If you're on a PC, you'll need a Thunderbolt card.
• Universal Audio Software: Make sure you have the latest versions of the UAD software and drivers installed. This is crucial for proper communication between your interfaces and your computer.

The Connection Process (Step-by-Step):

1. Power Down: Turn off both Apollo interfaces and your computer. Safety first, folks! We're dealing with electricity here, not magic.
2. Connect the First Apollo: Using a Thunderbolt cable, connect one of your Apollo interfaces to a Thunderbolt port on your computer. This will be your primary interface.
3. Connect the Second Apollo: Using another Thunderbolt cable, connect the second Apollo interface to the second Thunderbolt port on the first Apollo interface. This is the daisy-chaining part. If your first Apollo doesn't have two thunderbolt ports, then you may need to connect your computer to the other Apollo.
4. Power Up (in Order!): This is important! Power up your devices in this order:
   1. The first Apollo interface (the one connected directly to your computer).
   2. The second Apollo interface.
   3. Your computer.
5. Open UAD Console: Once your computer has booted up, open the UAD Console application. This is where the magic happens (or where you troubleshoot if things go wrong – don’t worry, we'll get to that).
6. Check Device Connectivity: The UAD Console should automatically detect both Apollo interfaces. You should see them listed in the "Devices" section of the Console window. If you only see one, or if you see an error message, don't panic! We'll troubleshoot that in a bit.

Configuring the UAD Console: Making Sweet Music Together

Okay, so the UAD Console sees both Apollos. Great! Now, we need to tell it how to use them. This involves a few key settings:

Clock Source: Choosing the Master

This is critical. One of your Apollos needs to be the master clock source, and the other needs to be the slave. The master clock dictates the timing of the audio signals. If the clocks aren't synchronized, you'll get clicks, pops, and other audio artifacts. Trust me, you don't want that.

Generally, you'll want to set the Apollo that's directly connected to your computer as the master clock source. Here's how:

• Open UAD Console Settings: In the UAD Console, go to "UAD Meter & Control Panel" (usually found in your system tray or menu bar). Then, click on the "Hardware" tab.
• Clock Source Selection: In the "Hardware" tab, you'll see a "Clock Source" dropdown menu for each of your Apollo interfaces.
• Set the Master: For the Apollo connected to your computer, set the clock source to "Internal." This tells it to use its own internal clock as the master.
• Set the Slave: For the second Apollo, set the clock source to "Thunderbolt" (or "External Word Clock," depending on your setup and the Apollo model). This tells it to synchronize its clock to the Thunderbolt signal coming from the master Apollo.

Important Note: If you're using an external word clock generator (a separate device that provides a super-accurate clock signal), you can set both Apollos to "External Word Clock" and connect them to the word clock generator. But for most people, using Thunderbolt as the sync source is the simplest and most reliable option.

I/O Matrix: Routing Heaven (or Hell)

The I/O Matrix is where you configure how your audio inputs and outputs are routed between your Apollos and your DAW. It can seem a bit daunting at first, but once you understand the basics, it's actually quite powerful. (And yes, it can quickly become a routing hell if you're not careful!).

Here's the basic idea: you can assign physical inputs on your Apollos to virtual inputs in your DAW, and vice versa. This allows you to, for example, record a microphone plugged into the second Apollo on a track in your DAW, or send a monitor mix from your DAW to a specific output on one of your Apollos.

To access the I/O Matrix, go to "Console" -> "I/O Matrix" in the UAD Console. You'll see a grid with inputs on one axis and outputs on the other.

Here's a simple example:

• Let's say you have a microphone plugged into input 1 of your second Apollo (the slave). You want to record this microphone on track 1 in your DAW.
• In the I/O Matrix, find the intersection of "Apollo 2, Input 1" and "DAW, Input 1."
• Make sure this intersection is enabled (usually by clicking on it). This tells the UAD Console to route the signal from input 1 of your second Apollo to input 1 in your DAW.

You can repeat this process for all of your inputs and outputs, creating a custom routing scheme that suits your needs. Don't be afraid to experiment! Just remember to keep track of what you're doing (a spreadsheet can be helpful for complex routings). Trust me, you'll thank yourself later.

Naming Channels: Sanity Savers

One of the best things you can do for yourself (and your sanity) is to name your channels in the UAD Console. This makes it much easier to keep track of what's connected where. Instead of seeing "Apollo 2, Input 1," you'll see something like "Snare Mic" or "Guitar Amp." Much more intuitive, right?

To rename a channel, simply right-click on it in the UAD Console and select "Rename." Choose a descriptive name that clearly identifies the source of the signal.

Troubleshooting: When Things Go Wrong (and They Will)

Okay, let's be honest. Connecting two Apollos isn't always a walk in the park. Sometimes, things go wrong. But don't despair! Here are some common problems and how to fix them:

• One Apollo Not Detected: If the UAD Console only sees one of your Apollos, try these steps:
  • Check your Thunderbolt cables. Make sure they're securely connected to both Apollos and your computer. Try using different cables to rule out a faulty cable.
  • Restart your Apollos and your computer in the correct order (as described above).
  • Make sure you have the latest UAD software and drivers installed.
  • Check your Thunderbolt drivers on your computer (especially if you're on Windows).
  • Try resetting the UAD System. You can do this by holding down the "Preamp" and "HPF" buttons on one of your Apollos while powering it on.
• Clicks and Pops: If you're hearing clicks and pops in your audio, it's usually a clocking issue. Make sure your clock sources are set correctly (as described above). Try experimenting with different sample rates. Sometimes, a slightly different sample rate can resolve clocking problems.
• High CPU Usage: Running a lot of UAD plugins can strain your CPU, even with the added DSP power of two Apollos. Try these tips:
  • Freeze or bounce tracks that are using UAD plugins.
  • Use the "Unison" preamps on your Apollo inputs to offload some of the processing to the Apollo's DSP.
  • Increase your DAW's buffer size. This can help reduce CPU load, but it will also increase latency.
  • Close any unnecessary applications that are running in the background.
• Routing Issues: If you're not hearing audio on the channels you expect, double-check your I/O Matrix settings. Make sure the correct inputs and outputs are routed to the correct channels in your DAW.

If you've tried all of these troubleshooting steps and you're still having problems, don't hesitate to contact Universal Audio support. They're usually very helpful and can provide more specific guidance.

Final Thoughts: Embrace the Power!

Connecting two Apollo interfaces can seem a bit daunting at first, but once you get the hang of it, it's a game-changer. You'll have more inputs, more DSP power, and more routing flexibility than you ever thought possible. So go ahead, unleash your creativity! Record that full drum kit, create those complex effects chains, and make some amazing music. And remember, when in doubt, read the manual (or just Google it!). Happy recording!

And hey, if you’re ever feeling overwhelmed, just remember my initial panic. We all start somewhere. The important thing is to keep experimenting, keep learning, and keep making music. Now go forth and conquer the audio world!