The first audio interface I ever used was a Presonus Firestudio. My parents bought it for me in high school because I had a desire to learn how to record drums, as well as other instruments. My practice space was a concrete paradise in the basement of my parent’s house.
I’m sure I annoyed the living daylights out of them. While the interface did do its job, and I did learn a lot about recording by utilizing it, it wasn’t until much later on that I discovered how poor of an interface the Firestudio truly was. I used it for a solid five years and eventually decided it was time to retire it, trade it in, and buy something now.
The Apollo Twin USB
The Apollo Twin: an interface regarded with high praise among most audio engineers. Universal Audio is one of the top brands in the business and it’s no wonder why this product gets such high notes across the internet.
I originally bought the interface with the intention of cutting vocals, as there are only two inputs on the back. Had I known how much I’d be using this thing in the future, I would have bought it much sooner.
Now, Universal Audio did release an updated version of the Twin called the MKII. I do not own the MKII, but the improvements made to the new version of the interface are small.
Note: This article deals with the Apollo Twin USB MKI. The MKII is very similar to the original version and thus, I have noted the changes UAD has made in the newer version. Even though the USB variant is different than the Thunderbolt for connectivity, they are the exact same product for a usability standpoint.
General thoughts on the Apollo Twin
When I first opened the box of the interface, I was immediately impressed. It just feels very well-crafted. You know how when you pick something up and it feels solid? This is the exact feeling I got. It feels like a great piece of gear.
Buttons and knobs
The front of the interface has many buttons and toggles, though I rarely use these knobs. They allow for pre-amp selection, gain, input type, hi-pass, +48V, pad, phase, stereo link, and switching between monitors and headphone volumes.
The newer version of the Apollo Twin did add a mono button to the front of the Twin. I mainly use the giant knob in the middle to control my monitor volume. All of these parameters can be controlled on your computer via the UAD Console.
Inputs and outputs on the back
On the rear side of the Apollo lies two analog inputs, which are switchable between mic and line (important to note that there is also a Hi-Z input on the front of the interface for recording instruments like guitars and keyboards).
For outputs, there are two monitor outs and an additional stereo line out. Depending on if you bought the Thunderbolt or USB 3.0 variant of the Apollo will determine which connector lies next.
One of the biggest selling points for me on the Twin is the Optical In. I own lots of pre-amps that are ADAT compatible. This is huge for anyone who wants to expand their input count for recording drums. I currently use my Twin alongside a MOTU 8pre. I’ve never had any issues connecting via ADAT.
Finally, there’s the 12V DC input and a power switch, but no one cares about that part. 🙂
Getting connected on a Windows PC
Universal Audio, in general, has been designed with Macintosh computers in mind. When I got all connected and booted up my PC, I immediately had issues. I scoured the internet for answers on support forums of all kinds to no avail.
I truly believed that my motherboard could not function with this audio interface. After many hours of troubleshooting I decided to try one drastic idea: change the USB cable.
The cable that is used with the Twin is known as a USB 3.0 B-Type. It’s not very common and I for sure didn’t have one at home. I took a trip to my local Best Buy and low and behold, they had one. When I got it home and plugged it in, I immediately saw the ‘New Devices Found’ indicator and was relieved of my painstaking hours of troubleshooting.
At this point, I thought I was in clear, and for the most part I was.
One annoying quirk with my Apollo Twin and Windows 10
For some reason, if I boot my computer from the off position to Windows and fire up my Twin, Windows will not recognize it until I reboot my computer a second time. It works completely fine after this reboot. To this day I have no idea why this occurs!
Even though I have to deal with that quirk, the interface itself makes up for it ten-fold.