Post Format

Three FireWire Audio Interfaces in Six Months

In late 2012, I started using an Echo AudioFire 12 to route analog audio into my 2010 Apple MacBook Pro. On paper, the AudioFire 12 was exactly what I wanted: 12 analog inputs and 12 analog outputs converted to digital and sent across FireWire. I’m using outboard preamps, so I’m not particularly needing the A/D interface to offer built-in preamps. The AudioFire 12 didn’t offer anything fancy; it was an A/D interface with FireWire output.

Initially, all seemed well. Very occasionally when recording I got a spurious digital pop noise on a track. I thought I was probably overdriving something somewhere, and investigated possible causes as a background task.

After a few months, the popping noises increased. About a year after acquiring the AudioFire 12, I was using it for a series of recording sessions, some of which turned out flawless, while others were littered with pops, in some places so bountiful that it came across as a crackling noise.

I learned that these noises are called gaps: essentially, a brief lapse in successful transmission of audio data. In the recorded wave file, when you zoom in far enough, you can see that a normal audio wave is a generally smooth, continuous line. A gap introduces a sudden discontinuity; the wave line jumps from one point to another. Once you locate a gap in the wave file, you can manually fix it by repairing the wave line, making it smooth and continuous again. You can also use a number of software tools to repair gaps automatically.

So I was able to salvage my recording session data, but it was obvious that sloshing around with frequent gaps in recorded audio wasn’t an appealing path forward. Research on the web suggested a number of things to try different in configuring my system, but when all of those failed, I resolved that the problem almost certainly was an incompatibility between the FireWire chipset in the AudioFire 12 and the FireWire chipset in my computer. Had it been a full desktop computer instead of a laptop, I could have installed a secondary FireWire interface card that would hopefully be compatible, but that wasn’t an option for me.

MOTU 828

I decided to sell the AudioFire 12 and replace it with another interface. I had had good success in the past with an audio interface from MOTU (Mark of the Unicorn, based in lovely Cambridge, Massachusetts), and, not needing anything fancy, I bought an original MOTU 828 unit, reportedly the very first FireWire-based audio interface, with eight channels of analog inputs, only two of which sported built-in preamps.

The MOTU 828 was something on the order of 12 years old, but it worked perfectly. Its minimal ability for routing and monitoring audio felt a little archaic, and it lacked the convenient MIDI I/O tacked on to nearly every modern FireWire audio interface, but I was able to make do. It chugged away in service of my home recording studio for an astonishing four months before its internal FireWire chipset flaked out, connectivity between it and the computer failed, and it started emitting a high-pitched squeal which gave me a moderate headache as I tried to make it stop.

I read online that MOTU tech support could, as of 2011 anyway, replace the FireWire ship and refurbish an 828 unit for $75, plus shipping charges. I called MOTU the next morning only to learn that they no longer service the ancient original 828.

So I needed to buy another new interface. I ended up selecting a new interface from Focusrite.

Focusrite Saffire Pro 40

The Echo AudioFire 12 is fairly unusual; audio recording professionals favor using outboard preamps, and buy $2000 interface units that have no built-in preamps. For my needs, I wasn’t looking to spend $2000 on an interface, but, apart from the Echo equipment, I’m not aware of another <$1000 interface that isn’t cluttered with its own preamps.

Built-in preamps are not necessarily bad, but they almost certainly will not be as good as standalone preamps. I have a Focusrite ISA two-channel preamp that sells for $900. The Focusrite Saffire Pro 40 audio interface has eight built-in preamps, one on each input channel, and sells for $500. It doesn’t seem credible that these <$60 preamps would be designed and built as well as a $450 preamp from the same manufacturer. This does, though, get usable preamps into the hands of people who might not have bought them otherwise.

I’ve used the Focusrite Saffire Pro for all of about ten minutes and so far it sounds great. Or I suppose I should say, it doesn’t sound like anything in particular; it functions as an audio interace, converting between analog and digital signals. I have some extra built-in preamps should I need them, and the overall design is (not surprisingly) more modern than the old MOTU 828. It lacks clock input, but I don’t need to synchronize it with anything else at the moment. In addition to the eight analog inputs, it also has digital inputs through ADAT, so I could plug up a really nice A/D converter and use the Saffire just to feed the digital data to the computer over FireWire. The front-panel buttons feel cheaply made out of plastic. (The knobs and power switch feel fine.) I imagine that Focusrite could increase the price by $50 and use the same quality of buttons they use on the ISA preamps.

Basically, it’s a lot like many other similarly-priced interface units. I don’t find these extremely interesting in themselves, but rather, just a needful component in recording audio. They do though become very interesting when they don’t work correctly in one way or another. Hopefully this brand new Focusrite Saffire will function well for years to come.

Leave a Reply

Required fields are marked *.