Universal Audio has long had a successful business selling hardware DSP effects, many of them carefully-modeling classic analog gear. These products use dedicated DSP hardware for number-crunching, requiring that you connect an extra box to your computer. UA has certainly had their loyalists, and for fans of the products, the dedicated gear is simply a convenient way to get all of these sound-processing goodies. But it’s fair to ask the question, as many producers have who read this site, what’s the advantage? Why not simply use native processing on your computer?

Apollo, UA’s new hardware, answers that question more emphatically. By integrating the processing prowess of the UA platform into a high-quality audio interface, you can now add UA effects live, as you record and mix, with extreme low latencies. UA reports latencies below a couple of milliseconds. That’s possible, theoretically, on a desktop computer, but not generally on a laptop and very often not with any real reliability. You can do it in a lab, but it’s not something typical users see.

So, in one box, you effectively get your whole studio: the audio interface, the DSP power, and real low-latency sound processing. It’s not the first audio interface with DSP, but it might be the most compelling case yet for why that combination make sense.

And here’s where things get interesting: via Thunderbolt, a single MacBook Air, costing just around $1000, could be your whole studio machine. And while Apollo runs a couple grand above that, that means the total price tag is stunningly low compared to what you’d pay just a short time ago.

UA briefed me earlier this week on the technology. Even as NAMM raves about iPads, you begin to see the real power of conventional computers. Steve Jobs once compared those computers to “trucks” – while quietly leading a company that profits on how cool trucks are, too. With an Air, adding only slightly to the weight of an iPad and at only twice the cost, you can connect to vastly greater native processing power, greater outboard processing power, and greater I/O. And now with Thunderbolt, you could connect a high-res display or two, a big, fast hard drive, and the audio interface, all without running out of power or impacting performance. (No, seriously – you can. The reason you haven’t seen this in action is that we haven’t had the hardware to show it off. Apollo will be a compelling case for that.)

All of this is academic until you actually have something to do with sound. So, UA is also expanding their developer platform to additional outside development; more on that soon.

Apollo isn’t for everyone; obviously, some people won’t like being tied to hardware, and native plug-ins do work for a lot of people. But it does solve problems for many potential producer customers by making something reliable, predictable, low-latency, extensible with lots of excellent processing tools, and all in one single-box solution.

Apollo will initially be Mac-only, but will come to Windows, too – and with more PCs supporting Thunderbolt in 2012, that means the MacBook is far from your only choice. So, you’ve got one add-on that’s your interface, your pres, and your mix/master/effect toolbox.

More specs:

• 18 x 24 FireWire/Thunderbolt-ready audio interface, 24-bit/192 kHz
• “Premium” mic pres – UA stresses that they’re also building on their mic pre reputation, and they claim the “lowest THD and highest dynamic range” in their class
• Dedicated front-panel controls: preamp gain, channel selection, mic pad, +48V phantom power, low cut, monitor level, and dual headphone controls.
• 4 digitally-controlled analog mic preamps, 8 balanced line inputs and outputs, dual front-panel JFET DIs, digitally-controlled analog monitor outputs, 8 channels of ADAT, 2 channels of S/PDIF, word clock I/O, FireWire 800 (standard), and a Thunderbolt expansion bay — making it a well-equipped centerpiece for the modern project studio.
• Core Audio drivers; ASIO coming, so you can use this with your DAW of choice
• Console application and plug-in for recalling all your interface and plug-in settings at once
• UAD-2 acceleration
• Analog emulation plug-ins from Ampex, Lexicon, Manley, Neve, Roland, SSL, Studer, etc.
• Thunderbolt will be available on a sold-separately Option Card; UA says it reduces latency and audio buffer sizes, improves high sample-rate performance, and allows greater UAD plug-in instances over FireWire.

Of course, because Thunderbolt also connects to FireWire devices, you don’t lose your FireWire investment. The only bad news is that you only get Thunderbolt here as an Option Card; I imagine we’ll eventually see UA ship Thunderbolt connections standard.

There are both two-core and four-core versions, powered by Analog Devices SHARC processors, running an estimated street of US$1999 and $2499, respectively. Apollo’s Thunderbolt Option Card will be shipping in the first half of 2012, with pricing TBD.

www.uaudio.com/apollo

Videos are available on the UA blog: http://www.uaudio.com/blog/apollo-intro-video

Windows 7 summer; 10.6 and 10.7 Mac OS X when it ships.

Software Images

With all the horsepower computers are now packing, you might be surprised at the idea of adding on dedicated hardware for sound processing. Or, you can look at it another way: with computers more powerful than ever, with digital processing sounding more convincing both as emulation of traditional gear and in imagining never-before-possible sounds, the digital studio in a backpack is even closer.

Into that picture, enter the Universal Audio UAD-2 Satellite. Enclosed in a metal housing about the size of a large-ish external hard drive, the Satellite could absolutely fit into the side pocket of a computer backpack or messenger bag. Coupled with a MacBook Pro laptop, you could very easily carry your entire studio on a bicycle. That’s not to take away from the joys of outboard gear, but if you’ve got some decent engineering chops, such a rig could really be a studio that can live anywhere.

I’ve had a chance to begin working with the Satellite as my main platform for UAD’s plug-ins for some months now, and it’s an extraordinary box. The most important thing to know about it is that it’s intended for select Intel Macs, and it’s equipped with FireWire 800. Dedicated DSP processing goes back to the very first days of digital audio on computers. (Early Digidesign products and even the IRCAM-developed predecessor of Max/MSP all used DSP hardware.) DSP also naturally appeals to sound engineers: it’s hardware built for the sole purpose of doing the kinds of number crunching in audio, as opposed to the general-purpose architecture of a computer CPU.

The challenge has always been how to get data between the computer and the DSP device. That’s led to an array of buses, like PCI Express slots (which requires jamming a card into a desktop computer) or ExpressCard. As Apple have largely phased out ExpressCard expansion, Mac users have found themselves without a solution.

The UAD-2 Satellite makes use of FireWire 800 instead, thus opening up compatibility with recent Intel-based MacBook Pro laptops as well as the iMac and Mac mini. The 17″ MacBook Pro continues to support ExpressCard, but FireWire 800 offers greater processing power (and is less prone to popping out, as cards in the ExpressCard slot have a nasty tendency to do). The Satellite is available as a “DUO” and “QUAD,” indicating the number of internal processors. (You do the math to work out how much more you get from a Quad than a Duo. I’ll wait…)

As an aside, readers routinely ask if something like the mini or, especially, the iMac could work for audio production. Resounding answer: yes, absolutely. The iMac in particular has a pretty compelling price/performance ratio if you want a compact machine to drop on a desk and don’t have a spare monitor. The mini’s no slouch, either, and seems a logical addition to, say, a project studio.

And that brings us back, full circle, to the reason the Satellite is compelling. It unlocks processing power exclusively dedicated to some tasty and useful processing, all emulating classic gear, while freeing up your computer to do other things. You might, for instance, focus on native processing for a software synth and some creative effects, then bring in the Satellite’s UAD-platform effects to add some historically-accurate compression. And even an entry-level, lowly Mac mini, coupled with the Satellite, is perfectly capable of handling typical compositional and mixing environments without bouncing to audio or freezing tracks.

You certainly need to be interested in the UAD catalog of audio processing tools before this really becomes relevant. For some insight into how Universal Audio does their development and conceives what they do, with the obligatory drool-inducing photos of some retro hardware, see our interview with Dr. David Berners:

Modeling Analog in a Digital Age: A Conversation with Universal Audio’s Chief Scientist; Gallery

But if you are looking for a platform on which you can run these effects – or if you’re ready to upgrade from a previous UAD system (your existing plug-in registrations will port right over) – read on.

What UA Says About the Satellite

Looking at a Satellite, you can’t really see much – it’s a magical, mystery box that processes sounds. It’s what’s under the hood that matters. So I talked with Amanda Whiting of Universal Audio about some of the technical details of the Satellite.

CDM: How has the Satellite evolved from previous UA gear?
UA: The UAD-2 Satellite marks the first Firewire-based external DSP unit offered by UA, for Intel-based Mac laptops and desktops. The Satellite provides up to a four-processor UAD-2 DSP Accelerator for the many people mixing and mastering on the road with their laptops, and for those who don’t have a desktop system that includes PCIe slots. It also allows for easy session compatibility — so you can take your UAD-2 plug-ins with you, and mix on another Intel-based Mac system that may not have a UAD-2 card installed. The FireWire 800 onboard provides twice the power of FireWire 400. This allows you to connect a UAD-2 Satellite and a FireWire audio interface together on the same FireWire bus, and still have enough bandwidth for lots of plug-ins.

Ed.: That’s an interesting detail, in fact – hard disks and most other accessories take advantage of only a fraction of the added bandwidth of FireWire 800, meaning for many applications, the “800″ is a bit of a misnomer. Us audio folk are different – we really are talking about maxing out that additional bandwidth for the UAD-2.

Any rough practical info on the DSP horsepower? I’ve done some tests as far as what I can run simultaneously and it’s a great step from ExpressCard, but curious how best to quantify it.

The UAD-2 Satellite QUAD is four times as powerful as the ExpressCard-based UAD-2 SOLO/Laptop card, which has a single chip. For your reference, here’s a couple of links:
http://www.uaudio.com/blog/uad-2-satellite-basics-faq
http://www.uaudio.com/support/uad/satellite-support

Also here is a link to the instance chart. The UAD-2 Satellite has the same theoretical instance counts as the PCIe cards, except at very high instance counts where the FireWire bandwidth is exceeded. Still you can run 152 mono plug-ins or 77 Stereo plug-ins with UAD-2 Satellite, so the FireWire bus is not typically a factor.
“http://www.uaudio.com/support/uad/compatibility/instance-chart.html

What real world uses are you seeing so far from your users? To me, it seems really practical for even live laptop performance, and of course mobile production … not to mention the ability to take your UA faves to a studio.

The UAD-2 Satellite definitely provides a level of portability that we haven’t been able to offer previously. It’s great to take into any studio and pull up your UAD-powered sessions, and it’s absolutely ideal for mobile production. As far as live use, latency is always an issue with running audio over Firewire, but with certain effects — particularly reverbs and delays that lend themselves to live tweaking — the latency may come across as a pre-delay and sound just fine. We’ve heard this more than once from our users. We’ve also seen a lot of adoption with Pro Tools HD Customers – these customers typically have all three PCIe slots taken up on a Mac Pro so the UAD-2 PCIe version may have been a non-starter, but with Satellite, they can keep their cards in the machine and simply connect UAD-2 Satellite via FireWire with great results.

Ed.: One note on latency: with a recent update, you can set minimum latency to an impressive 256 samples. So, at the very least, the software itself is not a limiting factor.

Setup and Use

Setting up the Satellite is fairly easy. I’d actually struggled a bit with an ExpressCard UAD-2 – firmware updates, a card that initially didn’t work, and difficulty, as with all ExpressCards, with the card popping out of the slot. (That’s not UA’s fault: it’s the result of overly springy slots on typical laptops, and the fact that the spring-loaded eject is itself a really terrible idea for something you want to stay connected.) The Satellite was much easier: plug in power, plug in a cable, boot up the machine, and go.

As with all UA products, the Satellite relies on a single, unified installer that gives you all of the plug-ins ready-to-use as VSTs, Audio Units, or, for Pro Tools, RTAS. (On the Mac, I’d recommend defaulting to the VST in hosts that support it.) You get a 14-day trial of everything; for longer use, you’ll need to purchase and authorize the plug-ins. (Various bundles with the hardware get you started with licenses for a range of tools.)

Download and open an authorization file, and you get access to the plug-ins you need.

On the hardware side, you need two cables to connect the Satellite: power and FireWire 800. (Bus power over FireWire 800 is insufficient to drive the Satellite.)

Stop and consider this for a moment: you get exactly the same power out of a Satellite that you would out of the equivalent internal card. That means the argument for a desktop chassis is greatly reduced versus a more convenient iMac, mini, or MacBook Pro.

Because the authorization is associated with the hardware, you can also move the Satellite between multiple locations. These days, a lot of us do production and mastering and such against tight deadlines or in time on the road. Now, you can do that, but still bring your arsenal of effects into a physical studio environment when you’ve got a couple of days booked for recording.

The hardware itself is really lovely; it’s definitely been rugged enough to hold up to all that travel. For anyone considering this for an institution or studio environment, there’s also a Kensington Lock so someone doesn’t walk off with your valuable gear and authorizations. There’s also a pretty, glowing UA logo that shows you power is provided. Unfortunately, the LED that shows you if you’re properly connected to the computer is hidden away on the back; it would have been nice if UA had associated that to the giant herald on the front, instead, so you could actually see it.

Also, I was surprised to learn that hot-swapping is okay. So long as you shut down your UAD software first, UA says you can feel perfectly safe disconnecting and reconnecting the hardware to an active or sleeping computer. That’s a nice boon to us laptop users.

“Ah,” you say, “this FireWire business is great, but I also use FireWire 800 for my project drive. And an audio interface.” The Satellite gives you a couple of options here. For one, it has a pass-through port, so you can daisy-chain additional hardware without a hub. Again, power becomes an issue. Most hard drives I’ve found have power ports, so you can simply bring along their power wall wart and power them separately. (You’ll want to bring along a little power strip.) UA suggests that for gear that lacks that – like certain Apogee audio interfaces – you can use a FireWire repeater, an affordable accessory which injects power externally.

The more significant issue is bandwidth and speed mixing. Any additional device will take up some bandwidth, because they’re sharing the same bus. In my use, I chose to simply run audio over USB2 and connected, with the addition of my wall wart, a portable Glyph project drive to the FireWire 800 port on the UAD-2. If you’re doing something fancier than that, you can allocate bandwidth in the UAD software.

The trick is if you add a FireWire 400 device to the mix. If chained in the wrong order, any single FW400 gadget will cause the FW800 gear to slow to 400 speeds. The solution: just connect that 400 device (like, say, an old MOTU audio interface) last in your chain.

This, to me, brings up an unexpected reason the new Thunderbolt port on new-model Macs becomes useful. The UAD-2 Satellite, for its part, gets plenty of bandwidth from FireWire 800. Universal Audio has expressed an interest in supporting Thunderbolt in the future, but for now, FW800 works just fine. If you invest in a Satellite now, but you’ve got a Mac with Thunderbolt, you could in future connect a different accessory to that Thunderbolt port rather than the FW800 port, thus leaving the Satellite its own bus. (Got that?)

In the meantime, I’m absolutely, positively happy with my 2010-model MacBook Pro, which I picked up steeply discounted when the new Thunderbolt models came out. I maxed out the RAM and saved hundred of bucks, and the combination of 2x USB2 and FW800 more than suits my needs. No complaints here.

As Amanda indicates, the Satellite gives you a significant amount of processing power. For my use, this was perfect for experimenting with creative effects and adding UA’s excellent compression and channel processing tools. I’ve got some mixing and mastering projects coming up, and can’t wait to bring the UA stuff into the workflow.

Recommendations

Whether you want access to the UAD platform is really dependent on your needs and tastes. Certainly, there’s a wide variety of native processing tools that don’t rely on external DSP hardware. The main appeal, as I’ve said in the past, is the unique, historically-informed modeling approach that Universal Audio take to their work. Their catalog is certainly extensive, and I’m especially happy with the quality of the recent additions, like the Studer multitrack tape emulation and some superb reverbs, compressions, and the like. (One new entry: the Lexicon 224.)

The question is really whether the FireWire 800 bus is big news for UA, and there, it’s tough to overstate how much this changes working with UA’s stuff on a variety of Macs and on the road. The SOLO I’d tested previously is nice enough, but the DUO and QUAD really give you the amount of processing power you’d want to do some real work, to experiment live across a number of tracks without running out of horsepower – and that’s, after all, the point of using a DSP platform.

A new Mac and a Satellite are really all you need to build an impressive digital studio. They now give you the freedom to make that studio exist anywhere, and with almost any set of tools. We’ve seen that kind of liberation with native processing, but to get that native power and DSP power at once is really a dream. For existing users, moving over is a no-brainer, since sharing authorizations is a cinch. For newcomers who’ve been waiting for the optimal hardware choice to unlock the UA catalog, this is it. (It’s worth looking into bundles to try to get your collection of effects rolling.)

Even with Thunderbolt on the horizon, external DSP on a MacBook Pro or mini is now finally accessible. UA’s stuff isn’t cheap, but if the value proposition makes sense to you, and you’re a Mac owner, you now have the combination you’ve been waiting for. The only bad news, really, is for PC users left in the cold – and there, we may just have to wait and see what direction laptop buses take in the wider market.

Universal Audio UAD-2 Satellite DUO and…
Satellite QUAD

Got questions for me, or for UA? Feedback on this gear or this review? Fire away in comments, as always, folks.

The competition for your audio interface dollar is pretty heated these days, but MOTU’s latest – the Audio Express – packs a pretty impressive feature set for something costing US$449 list. It’s both a 6×6 audio interface and a mixer, with standalone mixer functionality so you can mix signals from the front-panel knobs without a computer attached. It also has connectivity features generally seen only in pricier, physically-larger boxes. MOTU tells CDM the quality is equal to their higher-end offerings, and other rivals in the $500-800 range.

MOTU winds up on my short list as far as hardware that makes happy audio interface owners. For now, we’ll just have to look at the Audio Express “on paper.” That looks like this:

• 6×6 interface, 6×8 independent input/output channels.
• Use either FireWire (with bus power, generally only if you’re on a Mac) or USB2 (without bus power).
• Some nice monitoring options. Each output pair – main, line, S/PDIF, and phones – can have its own independent mix of six inputs, with or without your computer tracks. And naturally, that also lends itself to use by DJs and live electronic performers.
• Two mic/guitar combo jacks: Hi-Z 1/4″ guitar input or XLR mic input with phantom power, 20dB pad, etc. (Often only one is a guitar jack, especially at this price.)
• Balanced stereo inputs, balanced stereo outputs, 24-bit/96kHz S/PDIF digital.
• Trim on the volume inputs is digitally-controlled analog, for approximately 1dB adjustments.
• Front-panel mixing with LEDs for metering and dedicated volume knobs on each input.
• Time code support, low jitter.
• Connect your MIDI gear: sample-accurate MIDI on 1 in x 1 out.
• Connect your analog gear: DC-coupled TRS outputs for software like MOTU’s own Volta.
• Operate as a standalone mixer, no computer – just connect power.
• Plug-and-play USB2 operation, plus 32-bit and 64-bit native drivers for Mac and Windows.

You can also rack-mount it as a half-rack unit, although I like the ability to toss something this small into a backpack or messenger bag to head to the gig.

To me, just having dedicated front-panel input knobs, decent-enough I/O, and standalone mixing on a box with good timing and audio quality is pretty nice. I have to say, I think the Audio Express could fill an ideal niche as a mid-range audio interface – it’s a crowded field if you get cheaper or if you get more expensive, but there isn’t much in the $400-500 budget that competes well with this. And for that reason, I’ll try to get one in for review. As commenters suggest, the real question is whether you spend a little extra on the additional I/O on MOTU’s UltraLite. But the UltraLite doesn’t have those convenient front-panel mixing knobs, and I’m not sure everyone necessarily needs DSP effects. I think it depends on your needs, and we’ll have to see what street may be on the Audio Express.

MOTU Audio Express Product Page

Also, judging from those product shots, it’ll look great on my clean, white, mirrored lab table next to my MacBook Pro. Boy, am I glad I got that off the set of THX 1138.

Those of you in the market for a new MacBook Pro are no doubt already tuned into the product news. So let’s talk about what isn’t changed on the new MacBook line, because it’s a good thing.

• You still get FireWire 800 ports on all models, including the entry-level 13″ machine.
• ExpressCard is still standard on the 17″ MacBook Pro.
• Your dongles for video adapters still work.

I’m researching implications for audio of the new Thunderbolt connection. My guess is it’s a little too early to say; 10 GBps storage sounds fantastic, but it’s far beyond the needs of all but the craziest audio applications. (That is, fast FireWire and USB drives work really well already.)

Where you’ll see it in audio is likely two places: one, more high-performance audio I/O, and two, clearing the bottleneck with DSP chips that has long plagued external hardware DSP. The latter is maybe a bit ironic as we look at ongoing performance gains from GPUs and integrated architectures there, but it’s no accident that Universal Audio and Avid are excited about it, as they have DSP products. And enthusiasm from Avid and Apogee means you can expect to see high-end audio with lots of I/O for this format. See the Intel technology page. As for specifics, we’ll be watching.

For adoption, this is certainly big news. Thunderbolt faced a chicken and egg problem; Apple is the 800-lb chicken.

The short version of the other specs: these machines are faster. Again, though, current audio applications run pretty well on the previous machines; I’m pleased to say we’re now in a place where people aren’t red-lining their CPU every day.

In fact, for those reasons, if you want a bargain on a MacBook Pro for audio work, now could be a great time to pick up a closeout on the old machine. On the audio side, the new models are largely appealing because their Thunderbolt port ensures future-proofing for whatever comes next – without having to give up the I/O on the previous models.

More discussion on the Motion side, focusing, naturally, on what we know about the graphics chips:
MacBook Pro Revision Updates GPU, adds Thunderbolt, but No New Display Dongles (Phew)

And yes, you have choices in this competitive marketplace, including PCs. But there you go – anyone who thought we’d see a step backward in I/O today can now exhale. And anyone looking for greater architecture performance, your machines have arrived. And anyone saying that laptops aren’t still awesome and improving in the age of low-end mobile and tablets? You’re just kinda all-around wrong. As for tomorrow, well, who knows, who knows…

It’s difficult to describe Universal Audio’s plug-ins until you’ve tried them. It’s a bit like having chocolate sauce at your disposal, sonically speaking. Whatever your higher-level brain may have to say, somewhere deep in your mammalian brain, you hear only … mmmmmm. Chocolate. It’s the word I get from UA users, and I’ll also have an interview with UA to post next week in which we get deep into the philosophy of sound, software design, and modeling, a conversation that transcends any one product. They’re not for everyone – they demand a price premium, to be sure, versus rival CPU-native options, and those with access to a studio might just use the real thing. But for enthusiasts, they can be a delight.

The trick is actually having access to UA’s extensive library of analog-modeling effects. Even as CPUs have marched forward in performance, dedicated DSP chips haven’t stood still. That makes these number-crunching brains a convenient platform for sound, as they are on UA’s effects. If you’re not using a desktop PC with a PCI slot, that means you need an external bus through which the hardware and your computer can connect. ExpressCard is a big boon, but especially for Mac users, it’s been an obstacle. A powerful MacBook Pro is now available for around a grand, but to get ExpressCard, you now need the wallet-busting, messenger bag-cramming 17″ model. It’s clearly a deal breaker.

The UAD-2 Satellite DUO and QUAD should greatly broaden the appeal of the platform, making it accessible to inexpensive, recent iMacs and MacBook Pros. I’m sure Universal Audio is smiling at the idea that you can take that $1000-2000 premium and spend it on UA instead of Apple.

By connecting via Firewire 400 or 800 on a “select” (recent) Intel Mac, the Satellite gives you access to models of vintage hardware UA has made with the likes of Roland, Neve, Moog, Studer, dbx, Solid State Logic, Lexicon, Manley, Empirical Labs, Trident, SPL, and EMT.

On the PC, I’d still recommend the inexpensive ExpressCard option to get started. It’s cheaper, and won’t have the strict compatibility requirements. On the Mac, though, with $500 plug-in vouchers or 50 plug-ins included, the US$899 starting point on these models doesn’t look bad at all. In fact, someone out there may be over at the Apple Store already pricing out one of the “low-end” iMacs or MacBook Pros, as they represent desktop-class performance from just a couple of years ago, particularly with what you can do now with USB2 and Firewire.

UA also recently added Pro Tools compatibility, so that combined with FireWire options means just about anyone can now consider their platform. If it’s something that interests you and you’ve got questions, fire away in comments and I’ll pass them on to the engineers at UA.

http://www.uaudio.com/

UAD-2 Satellite DUO Product Page (the entry-level model … more specs on compatibility forthcoming)

Darnit. Now I mentioned chocolate, so I have to go eat a chocolate.

FireWire may be getting rare these days, but new hardware proves that doesn’t mean serious external audio interfaces are in any danger. In the latest iteration of its tried-and-true 828 line, MOTU combines both Firewire and USB 2.0 for Mac or PC, and a wide range of features. The MOTU 828mk3 “Hybrid” in a nutshell:

• 28 inputs, 30 outputs. Combo jacks for 1/4″ guitar in, XLR mic. Phantom power, of course.
• Balanced/unbalanced 1/4″ analog ins and outs running at 24-bit/192kHz. Separate main XLR outs with dedicated volume controls on the front panel. (Quick, turn that down!) Two headphone jacks with independent volume controls.
• No channel sharing (the sort that tends to exaggerate those in/out counts) – you get dedicated mic inputs, ADAT optical, S/PDIF digital I/O, headphone output, and mains, all as separate channels. Just to reiterate…
• Dedicated headphone out.
• Hardware sends.
• Onboard mixing: a 28-input, 16-bus digital mixer.
• Onboard effects: extensive reverb, compression (both standard and one that models a vintage compressor), modeled EQ, and Mac/Windows software for editing.
• Instrument tuner.
• Audio analysis tools.
• CueMix gives you multiple monitor mixes, send/return loops with gear, all with zero-latency.
• Surround mixes if you want them, user-defined or quad, 6.1, 7.1.
• Toaster oven, cappuccino machine modeling the legendary Italian bistro model, controllable through cross-platform BreakfastFX(TM) editing software. Kidding.

In all seriousness, the fact that you can do this much with USB 2.0 raises some question in my mind about how much we really need USB3 for audio. But I’ll be interested to see what happens as that spec and available hardware develops.

What you may miss amongst all the specs is an important feature of the 828mk3 – this interface can run both as an audio interface and as a very versatile standalone mixer, complete with those effects and routing options. That makes it an easy investment to justify. As a rack module, it’s still a bit short on convenient front-panel controls – digging into those settings is still easier with software – but then again, that also means it remains compact.

You also get extensive driver support, with native 32-bit and 64-bit drivers for Mac and Windows, superb MIDI support (sample-accurate connections), low-jitter performance thanks to a DSP-driven clock, and extensive time code support – the features that have made MOTU one of the best-loved, grown-up audio interfaces.

(Side note — really, my only complaint is the lack of Linux support for MOTU boxes, though there’s some hope that could change. Developers complained, MOTU a user voluntarily loaned a unit, and there’s been some progress. If you know anything about how to write drivers, ahem… I’m sure just saying that, some folks in Cambridge, MA are rolling their eyes, but hey, it is another tool some of us use to do our job.)

The 828mk3 Hybrid isn’t big news – it’s the latest evolution of a long line of audio interfaces – but that’s why it’s big news. It consistently winds up on a short list of the most versatile, balanced interfaces out there, and from hardware to software, it’s extremely mature gear.

MOTU says pricing will be the same as on the previous 828mk3, which should cause it to land around US$750 street.

828mk3 Product Page [MOTU]

Windows matters. It’s what roughly half of CDM readers use, and – for all the attention Apple gets – it’s a big part of the computer music world. Windows today also faces many of the same under-the-hood challenges that other operating systems do, so even if you’re a die-hard Linux or Mac user, you may want to pay attention.  You don’t need to love Windows, and you certainly won’t be hosting a Windows 7 launch party. You want to know if the OS will get out of your way and let you get to work.

Windows Vista proved what happens when an operating system’s many interconnected pieces are out of alignment. Even a graphics driver out of sync with underlying changes in the OS could render audio unusable, because just one missed sample can produce an audible glitch or dropout. Part of why I’m optimistic about Windows 7 is that Vista today is a radically different picture, thanks to many, many fixes delivered by Microsoft in updates and more mature audio and video drivers. But that means not just whether 7 is better than XP, but whether 7 is also better than Vista.

Vista wasn’t entirely alone: Mac and Linux have all had their share of growing pains in recent years. The devil is usually in the details. So, I again turn to one of the best guys in the business for sorting out all those technical details. Noel Borthwick, the CTO for Cakewalk, probably has a better big-picture view of how music and audio work in Windows than anyone on the planet. He’s a person hardware and software vendors outside Cakewalk often rely upon as a resource. Noel kept us technically honest on Vista, and he’s doing it again on Windows 7, with some exclusive information for CDM.

Those details get mighty technical, so here’s the punchline: Windows 7 is an OS Noel would use himself. It was hard to get anyone to recommend Vista over XP; loyal Windows-using developers I know still largely stick to XP. But would Noel switch from XP to 7?

Yes, absolutely. Windows 7 finally delivers on the stability and performance that users hoped for from Vista. The kernel changes and optimizations for large scale multi-core processors make it very attractive to DAW users who are interested in better low latency performance. I will be building a new DAW soon and Windows 7 X64 will be my OS of choice.

What’s new in Windows 7?

• Better multithreading: Improved performance of highly-multithreaded software and hardware by removing a significant bottleneck, especially relevant to a tool like SONAR
• Better memory management: Improved memory management when working with multiple threads
• Less nagging: More customization over UAC prompts (meaning they don’t have to nag you more than you want)
• More lightweight: Fewer system services run by default on a stock system, plus a leaner footprint of the OS
• Media support: More native media format support, including QuickTime MOV and H.264, plus drag-and-drop media transcoding
• Composite devices: More logical display of hardware with multiple functions (like audio and MIDI).
• FireWire: Enhanced FireWire support, with IEEE 1394b
• Multi-touch: Multi-touch display support
• Usability improvements: An improved user interface, task bar, and Libraries for managing files

If you’re ready for all the gory details, read on – including a frank appraisal of how all of this compares to XP in real-world performance, and what compatibility issues to look out for if upgrading from either Vista or XP.

Noel Borthwick of Cakewalk effectively wrote this story in response to my questions, so these answers all come from him. Microsoft has not responded to my requests for a review copy, so I’ll be able to evaluate this on my own system – albeit far less scientifically than Noel can – closer to launch.

WARNING: Extremely geeky details of the inner workings of Windows 7 follow, in keeping with our “never dumbed down” policy. If you’re a developer, you can likely get some leads on how to better support Windows 7 in a single point, something even Microsoft doesn’t provide as completely. But if you’re willing to dig, you get a rare view of the OS from a developer view – no marketing speak, no cheerleading, no fanboyism, no platform wars, no writing for the lowest common denominator.

What Actually Improves Audio Performance

Peter: In terms of performance for audio production, what are the significant differences in Windows 7?

Noel: Windows 7 on the surface is very similar to Windows Vista. It has the same audio driver support and same audio system infrastructure as Vista. However, it’s some of the under-the-hood improvements that are more significant for audio production. There are some interesting innovations and optimizations in the Windows kernel, making the OS more scalable for concurrent processing. This makes it attractive for highly multithreaded applications like SONAR. Additionally there are various new API’s/SDK’s that may be of significance to developers. Some highlights are below:

Multi-threading: Removal of the kernel “global dispatcher lock”

In Vista and earlier, on a highly multi-threaded system (e.g. SONAR running on an 8 core hyper-threaded Intel Core I7 PC), you have many threads all processing tiny audio buffers at low latency. All these threads are ultimately waiting on the dispatcher lock when it comes time for them to be managed by the Windows scheduler. This global lock becomes a bottleneck in the system and prevents efficient multi-core workload distribution and scalability. This problem gets magnified as you increase the number of cores since they are all gated by a common lock. In Win 7 the kernel team changed the logic in the Windows scheduler to abolish this global dispatcher lock and use per object locks. This effectively removes this age old bottleneck and allows Win 7 to scale better even under workloads of 256 processors.

This change means a lot to applications like SONAR that rely on multithreaded processing of very small workloads. Initial benchmark results have been promising in this regard. SONAR performs more efficiently at low latency on multi core machines.

Improved Memory Management – PFN database lock

The PFN (page frame number) database lock was used by the memory manager to lock pages of memory in the working set. Like the dispatcher lock above, this would gate memory access from different threads causing resource contention. Work in this was first done in Windows server 2003 SP1 and Windows 7 has now has this optimization as well, improving asynchronous access to memory.

Power Optimization: Core Parking

Windows 7 has a new feature called Core Parking. Core Parking is a power saving optimization that shifts processing load to one or more cores and puts other less busy cores to “sleep”. The objective is to let other cores idle if workload levels allow for it. This optimization had us scratching our heads when we ran a benchmark test on a Quad Core I7 machine. At any point in time, we would notice that some cores were idle in task manager. The reason for this turned out to be Core Parking. Core parking can be useful to save battery life while running projects on laptops.

Better WaveRT Performance

Unlike Windows Vista, Win7 now uses event mode internally. This is good news, since it will help guarantee that HDAudio drivers in Win7 support WaveRT event mode properly. Additionally event mode is now part of WHQL logo certification for driver vendors, so any WAVERT device must support this to get a Win7 compatibility logo.

Ed. note: The plain-English translation here is that WaveRT, Microsoft’s own real-time audio driver facility, now is more likely to work the way you expect. Cockos, makers of REAPER, actually provided the ability to turn off WaveRT Event Mode at the end of last year because of unpredictable results. Windows 7 should resolve these issues.

Other Improvements

Peter: Noel also assembled some other improvements worth noting in Windows 7. They’re subtle, but useful: you may finally be able to avoid installing QuickTime/iTunes just to play some video files, interfaces with audio and MIDI jacks don’t have to show up separately any more, there’s improved FireWire support, usability improvements, and multi-touch on mainstream computers is now nearly here.

Noel:

Additional File Format support

Windows 7 adds native playback support for media in MP4, MOV, 3GP, AVCHD, ADTS, M4A, and WTV multimedia containers. It has native codec’s for H.264, MPEG4-SP, ASP/DivX/Xvid, MJPEG, DV, AAC-LC, LPCM and AAC-HE

Yes you read that right – QuickTime MOV file support is now natively available in Windows 7 so you don’t need to install QuickTime. Another big plus is that this is supported under the X64 version of Windows 7 as well, something you cannot do with Apple’s native QuickTime itself!

All media files using these codec’s should play in Media Player. It appears that these new codec’s are exclusively available to Media Foundation applications and not via other legacy API’s such as DirectShow etc.

File format transcoding

File format transcoding of many popular formats is now built into the Windows 7 shell. I.e. dragging and dropping files onto a device automatically performs the necessary format transcoding if the format is supported. This was primarily done to copy formats to portable devices like cameras but should be useful in other scenarios as well.

Multi-function devices and Device Containers:

Prior to Windows 7, every device attached to the system was treated as a single functional “end-point”. While appropriate for single-function devices (such as an audio interface), this does elegantly represent multi-function devices such as a combination audio/MIDI interface. In Windows 7, the drivers and status information for multi-function device can be grouped together as a single "Device Container", which is then presented to the user in the new "Devices and Printers" Control Panel as a single unit.

http://www.microsoft.com/whdc/Device/DeviceExperience/ContainerIDs.mspx

Note: this should not be confused with device aggregation as is available with Core Audio on Mac OS. On the Mac, you can treat multiple audio interfaces as though they’re one interface, so, for instance, you could get extra outputs by combining a couple of audio interfaces, and your software will see them as if they’re just one box. But SONAR provides this capability on its own, so if you’re a SONAR user, you can get the same functionality.

FireWire/USB

Windows 7 contains a new FireWire (IEEE 1394) stack that fully supports IEEE 1394b with S800, S1600 and S3200 data rates. According to reports, USB 3.0 may be supported in a future Windows Update. It was initially planned for Win7 but is not supported in the shipping version of Win7 due to delays in the USB 3 specification.

Multi-touch

Windows 7 includes integrated support for multi-touch displays.

Libraries

Libraries are user-defined collections of content including folders. It’s a handy way to categorize and create shortcuts to samples, music, etc. Special shell folders (Documents, Pictures, Music, and so on) are now Libraries.

Accelerators for Windows

Windows 7 Accelerators provide a way for learning more about selected text, optionally using voice control.

Virtual hard disks

The Enterprise and Ultimate editions of Windows 7 incorporate support for the Virtual Hard Disk (VHD) file format. VHD files can be mounted as drives, created, and booted from.
An installation of Windows 7 can be booted and run from a VHD drive, even on non-virtual hardware, thereby providing a new way to multi boot Windows.

Leaner Footprint

Win7 has a leaner footprint and has been tweaked to work well on less powerful PC’s, laptops and Netbooks. I have heard reports of Win7 working more smoothly on machines that would be slow under Vista.

Listen Mode

Another nice touch in Win 7 is that they now have a listen tab in the audio properties. Turning on "listen mode" basically routes input to the default output device allowing you to monitor an input device in Windows itself. Sadly this runs via the Windows audio engine which is always running in WASAPI shared mode, so it’s subject to a 30 msec delay. Of course you can always load an application like SONAR and route the audio inputs to an output for low latency monitoring.

Compatibility: What to Watch

Upgrading from Vista

Peter: Relative to Vista, are there any changes that are likely to introduce new compatibility issues with hardware or software?

Noel: With any new OS there is always the potential for compatibility issues. Win7 is built on the Vista foundation and one of its goals was better compatibility. As such most applications that are Vista compliant should work as well or better in Windows 7. UAC in Windows 7 has been improved so this might also help with general compatibility problems with some applications.

We have run into only a couple of compatibility issues in Win7 during the course of our development/testing of SONAR 8.5.

The MMIO API in Win7 (typically used for writing RIFF wave files) has a compatibility issue with the mmioDescend API with LIST ‘WAVE’ chunks. This caused our code that reads audio bundle files to fail and read scrambled audio data. We worked around this problem in 8.5

In WASAPI exclusive mode under Win7, the minimum latency you can achieve is now unfortunately 3ms and the code reports an error if lower. The fact that Vista has no such limitation has been reported to Microsoft. Hopefully its a mistaken fence in their code and this issue is fixed via an update, since it’s a step backwards for low latency in WASAPI mode.

Ed.: That last issue is an interesting one for anyone really pushing the envelope with low latency, so I’ll keep in touch with Noel if there’s any update.

Upgrading from XP

Peter: What hardware and software compatibility issues should users be aware of if they’re thinking of migrating not from Vista but from XP to Windows 7?

Noel: The compatibility issues that typically affect users migrating from XP to Vista/Win7 are:

UAC problems: Many applications and plug-ins are not built to handle the newer security settings in these OS’s. For example, if an application relies on something that requires administrative access it will fail when running as a limited user in Win7. This is a serious issue since in Vista/Win7 even if you are running from an administrator account; programs are launched by default with limited user privileges. Unlike XP, you have to explicitly run as an administrator to use such programs. To be Win7 logo-compatible, all applications need to should support running as a limited user.

Drivers: Although for most practical purposes audio drivers in XP and Windows 7/Vista are similar (you still need to write WDM drivers) there are sometimes quirks in specific drivers may cause problems. Most typical driver issues here are caused by installers that make assumptions about the OS version. In many cases this issue can be solved by the end user by setting the “compatibility mode” to Vista in the file properties for the appropriate driver installer file. (Right click the setup exe file to set its properties)

Ed.: I don’t feel either of these is a deal-killer, as I’ve been living with Vista for some time, but they’re still worth watching out for if upgrading from XP. And it means if you have an older machine that’s still working properly, you’re just likely to leave it on XP and worry about sorting the upgrade on a new box.

Less Nagging?

Peter: We talked when Vista came out about User Account Control and particularly audio-specific tasks that required elevation or different handling of permissions in Vista. I know UAC has been streamlined in W7. Do these changes impact audio apps at all? Are there corresponding under-the-hood changes?

Noel: The UAC changes in Win7 are primarily to allow more customization over the UAC elevation prompting process. There are no changes to the fundamentals of how UAC itself works that I am aware of. The classic problem with audio applications with UAC is when programs or plug-ins write to areas of the registry or file system prohibited from standard user access. Even when you are running as an administrator, by default when you launch a program (or the program itself launches a secondary process) Windows 7 will run that process with standard user privileges. If a program or plug-in attempts to write to an area which it doesn’t have write privileges for, virtualization will kick in. While this may allow the program to work, in general it is bad practice to rely on virtualization, since it can cause many unwanted side effects and behaviors in applications.

There are now four customization settings for UAC:

1. Never notify (least secure). The user is not notified when a program tries to install software or make changes to the computer. The user is not notified when they make changes to Windows settings or when programs try to do so.

2. Only notify me when programs try to make changes to my computer. The user is not notified when a program tries to install software or make changes to the computer. The user is not notified when they make changes to Windows settings. However, the user is notified when programs try to make changes to the computer, including Windows settings.

3. Always notify me. The user is notified when a program tries to install software or make changes to the computer. The user is also notified when they make changes to Windows settings or when programs try to do so.

4. Always notify me and wait for my response (most secure). The user is notified when a program tries to install software or make changes to the computer. The user is also notified when they make changes to Windows settings or when programs try to do so.

Customization and Tuning Advice

Peter: How much customization would you advise people do to their OS? That is, you’ve just installed a build of Windows 7 for working with SONAR on a test machine. Do you run the stock configuration, or start turning off services, disabling disk indexing, etc.?

Noel: Optimization and customization is a topic that can’t be fully discussed in the scope of a brief article. In general you need to optimize a system when you have known bottlenecks. Otherwise you can spend a lot of time tweaking things that have little effect on the end goal. In fact, you may even end up destabilizing a perfectly working system. A stock Win7 machine is not optimized for audio necessarily but it appears MS put some thought into trimming out unwanted startup tasks to cut down on startup time. For example there are now “Triggered start services” in Windows 7, so out of the box you can have fewer services running after a fresh boot. There are probably many background services in a modern DAW that could be suspended if you don’t need them but they should be evaluated on a case by case basis depending on what you use the machine for.

Peter: A lot of users were advising running Vista with Aero off, certainly in the early days. Do you think it’s now advisable to leave Desktop Window Compositing switched on for audio work? (Note: I am aware that there’s actually no way to *completely* disable the Aero windowing environment in a way that it reverts to XP, as even in Class mode with no compositing settings the engine has been altered.)

Generally speaking, turning off Aero will free up some resources on your system, since it uses more costly 3D graphics rendering and transparency a lot. However on any modern graphics card, Aero offloads a lot to the GPU so unless your DAW is also competing for the same GPU resources, turning it off may or may not make an appreciable difference to performance. Most applications that are not graphics intensive use GDI for rendering to the screen and since GDI doesn’t take advantage of DirectX hardware acceleration it’s normally not contesting with the GPU. If you are using plug-ins that use Direct 2D or Direct3D, you are probably better off disabling Aero.

Launch Party, After All?

Thanks, Noel. So, the big news behind all of this is that a move from XP to Windows 7 is finally advisable.

I would still caution, as I did recently with Mac OS Snow Leopard, that you typically don’t want to upgrade to a new OS the day it launches. You’ll want to verify compatibility with your software and hardware before making the jump.

That said, this is an unusual upgrade in that it appears to resolve more issues than it introduces. I actually haven’t been able to find a single user out there testing Windows 7 who has found any issues with audio or music production. Of course, when it launches, we’ll have a much larger test base, so I expect we’ll find something – even Windows Service Packs and point releases of Mac OS have been known to create some issues. As we get closer to launch, I’ll review how you would backup your existing XP or Vista system to ensure that if you do choose to upgrade, you can revert to a previous version.

I am, however, cautiously optimistic. And now is an especially good time to make the jump to 64-bit. It’s easier on Windows than any other OS at the moment, and easiest in SONAR, because SONAR allows you to easily migrate 32-bit plug-ins into the 64-bit environment. You’ll need a 64-bit machine and enough memory to make 64-bit worthwhile, but if you’re building a new workstation, as Noel is, the timing could be perfect.

I also think there’s plenty of room left to talk about issues that go between operating systems, particularly how audio software can better support multi-threading and processing on the GPU, multi-touch, as well as emerging I/O standards like USB3. (OpenCL, much-touted in Snow Leopard, is also supported on Linux and Windows, and Linux actually beat both Mac OS and Windows to the punch in providing a first implementation of USB3.) Correction: I should also add that the excellent Reaper has also added this feature. With full 64-bit support in Cakewalk’s own Dimension and other instruments, NI’s Kontakt sampler, and the bundled 64-bit-native plug-ins in Reaper and SONAR, that means you can build a really capable 64-bit rig on Windows.

With fixes getting the OS out of your way, we can return to issues that really matter, many of which apply to every OS.

Music is, as always, the perfect place to talk about these issues. We push our machines harder than just about anyone, and in ways that are the least tolerant of timing discrepencies and glitches. I’ve said it before, and I’ll say it again: if you want to look into the future of computing, ask a musician.

And that calls for a party.

Previous coverage:

SONAR 8.5 and how it can smooth the transition to 64-bit (8.5 is the build that includes Windows 7-specific improvements)

Vista Tweak: Use the Audio Profile Cakewalk’s CTO Uses

Optimizing for Vista: Inside the Mechanics of SONAR 8 with Cakewalk Engineering

Adieu, XP; How Vista SP1 is Doing, and Why This OS Generation Has Been So Tough

Vista for Audio, 1 Year Later: Talking OS Plumbing with Cakewalk’s CTO

Vista for Music + Pro Audio: Exclusive Under the Hood with Cakewalk’s CTO

And yes, I think Noel deserves an Honorary Contributing Editor position for all he’s done giving us absurdly-precise inside details for how Windows works.

Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.

It’s been one of the few constants in music technology. To use Pro Tools software, you need Pro Tools hardware – that means M-Audio interfaces for M-Powered (and now Essentials) and Digidesign interfaces for LE and HD. Without M-Audio or Digidesign hardware actively plugged in, the software refuses to run. And there’s no way for a third party to get their audio hardware working with the software.

Or so everyone thought. Without the cooperation of Avid, Mackie says they have managed to get their Onyx-i mixer line working with Pro Tools, and they’ll even “certify” compatibility. At the end of July, a number of audio sites (including Mix and Sonic State, but not CDM) received a package with one of Mackie’s new mixers, a video, and a copy of Pro Tools M-Powered. The message: a “secret” driver provided compatibility between Mackie’s mixer-audio interface package and Pro Tools. (See Sonic State’s writeup.)

So, what’s going on?

Onyx-i – What’s “i”mproved

Before I get into that, first, a word about Mackie’s new Onyx-i mixers. Viral videos aside, I already know many CDM readers don’t actually like Pro Tools, and the Onyx-i has plenty of other features to recommend it. The original Onyx was already an interesting solution, with the potential to combine a full-blown Mackie mixer with a FireWire audio interface. But the hardware was bulky, and adding FireWire support required buying and installing a separate add-in card.

The Onyx-i solves both problems. The entry-level Onyx 820i model adds a compact, inexpensive (street just US$500) 8-channel by 2-channel output option. Also, all of the new Onyx line (up to the 16×16 1640i) have FireWire built-in – no expansion needed. The line still has a rather hefty bulge that sits below the mixers, but at least with the addition of the 820i, there’s an option I could imagine throwing in a backpack. (That’s good news, I think there are more scenarios where you might want simple mixing than need to lug around a 16×16 mixer-interface.) The cheaper Onyx-i models are also competition for the Cakewalk VS-100 I reviewed recently. The Onyx lacks the VS control surface, flash recorder, and the Cakewalk software bundle, but if you were more interested in the mixer to begin with, the Onyx series could be worth a look.

At the high end, the 1640i can stream full 16 x 16 audio channels in and out of your DAW.

The Onyx also makes “universal” compatibility a selling point, and that’s where this Pro Tools saga comes in. The Onyx-i is “qualified for use with all major DAWs,” including Logic, SONAR, Cubase, Ableton Live, and … Pro Tools M-Powered 8. Of course, the last entry was assumed to be technically impossible, and Avid has, to my knowledge, never been compatible with any hardware other than their own. (The only exception I can recall is the brief availability of something called Pro Tools FREE, which worked with standard audio drivers and cost nothing, though it had a number of other limitations.)

Mackie’s announcement came with this disclaimer:

The Onyx-i Series Mixers are qualified by Mackie for use with Pro Tools® M-Powered™ 8. Mackie will release a driver (via www.mackie.com) together with full details of how to use the Onyx-i series with Pro Tools® M-Powered™ 8 in the coming weeks.

Avid has declined to comment for the time being on the Onyx-i compatibility claim, though they at least confirmed that they were not involved.

Shaunna Thompson of Mackie emphasized to CDM that there was “no reverse engineering” involved in creating the Onyx-i driver for Pro Tools M-Powered, and that they were “in discussions” with Avid but could not comment further on those discussions or how Avid would respond.

Conventional wisdom about Avid and Pro Tools has been that hardware “lock-in” – the reliance on their hardware – is good for their business. That may well be, and I do believe in hardware choice; it’s part of why Pro Tools hasn’t ever been my main DAW. I do have to point out, though, that every other audio software maker, from big developers to people maintaining open source software, will tell you compatibility is a huge pain. Massive amounts of time get spent on testing and compatibility, particularly when you start combining different operating systems and different combinations of hardware and drivers. So there’s no question that the other thing Avid has been able to do is to reduce some of that complexity, some of the additional sources of support problems, and all the costs associated with both.

But that made me all the more curious about just how the Onyx-i support works.

Q&A with Mackie

CDM: Can you comment on the inclusion of Pro Tools M-Powered?

Mackie: The “Ransom Packages” that were sent out as part of a viral campaign included a copy of Pro Tools^® M -Powered^™ 8. However, the mixers do not come with a copy of Pro Tools; users will need to purchase this separately.

CDM: I’m sure you can’t talk about all the details, but is there anything you can say about how the M-Powered support was reverse-engineered?

Mackie: Mackie did not ‘reverse engineer’ support for Pro Tools M-Powered 8. We created a custom universal driver that enables use with all major DAWs including Pro Tools^® M -Powered^™ 8.

CDM: For that matter, at the risk of asking the obvious, why would Mackie want to support Pro Tools given support for other hosts and your own DAW (Tracktion)?

Mackie: The Onyx-i Series interfaces with all major DAW’s including Pro Tools^® M -Powered^™ 8 and our very own Tracktion Software. Our customers have been telling us for years that they want a mixer that can interface with Pro Tools^® – we are simply giving our customers what they want. 

CDM: Aside from the Pro Tools questions, I’m a little unclear – what’s new in the "-i" versus the original Onyx predecessors?

Mackie: The biggest difference is that the Onyx-i Series has deep FireWire integration. Now you don’t have to buy a separate FireWire card because it’s already built into the mixer offering a significant increase in performance and value over the older Onyx Compact Series. This effectively means you get a premium analog mixer AND an ultra-high quality digital interface. These are the tools you need for serious computer recording.

Every channel on the mixers can be routed pre- or post- EQ to the computer, allowing the user to choose whether to implement EQ to tape or not. Returns from you computer can be routed back through the channel strip for integration into the mix or for mastering the Perkins EQ.

So, Does it Matter?

It seems that if this had happened a few years ago, it might have been explosive news, which is not the sense I got with Mackie’s attempt to “go viral” with that guy, his little dog, and his pantyhose mask. Then again, I’d better not speak too soon, lest I wind up with 100 comments on this post…

For many users, people who want hardware choice may already have found DAWs with which they’re happy. Pro Tools has its loyal users, and people make great music with it – it just happens that the same can be said of Ableton Live, Apple Logic, Reaper, and many others (just in descending order of recent reader interest on this site). And, of course, Mackie also makes their own Tracktion. Mackie actually risks overshadowing the other news here – the ability to buy a single piece of gear that’s both a Mackie mixer and a FireWire audio interface for under $500.

On the other hand, it’d be a fairly significant acheivement to release this driver, and perhaps even to get Avid’s support. And while I had to ask the question above, of course, Mackie wouldn’t do this if they weren’t getting customers bugging them for it. That’s why interoperability ultimately matters: users want certain choices, and (perhaps rightfully) don’t understand why they might be denied those choices.

I’m going to place the burden on Avid on this one, for one reason: Avid claims “interoperability” is one of their new corporate goals. It’s never been entirely clear what they mean. Some of that goal seems to have more to do with interoperability between products in their own product line. (In fairness, that seems a logical place to start!) So I hope whenever Avid and Mackie do finish their discussions, whatever Avid’s decision, we get clear communication for exactly what the “new” Avid’s interoperability goals are. If they feel they have a case for not supporting hardware like Mackie’s, that’s their prerogative. I’d just like to see clear communication from either company, to explain to their user base why they make those choices.

And, of course, I don’t expect that communication from either Mackie or Avid will come from anyone wearing a mask and a disguised voice.

I’ll be watching for the outcome of the discussions between these two industry giants. Stay tuned.

As you no doubt heard, Apple today refreshed their MacBook lineup with across-the-board adjustments to pricing. I’ll let other sites comment on the news more generally, as this is a music site, not a notebook site. But the big news for audio in terms of I/O, just so you don’t miss that:

• FireWire on more models: Finally, you can again get a 13” MacBook (now called MacBook Pro) with onboard FireWire – a FW800 connector. That’ll restore the use of audio interfaces and certain high-speed storage, and means the MacBook is again a good choice as an audio machine at the US$1199 base price point.
• ExpressCard on fewer models: Oddly, the addition of a lowly SD card slot (nice for photography and mobile recorders) has supplanted the ExpressCard slot on the 15” MacBook Pro. If you want ExpressCard, you have to buy the 17” – which, in turn, loses the SD card slot.

Now, generally the news here is pretty good. For music, you probably aren’t too concerned about the GPU, so the 15” MacBook Pro at US$1699 is looking like a nice deal. But PC users are no doubt puzzled, given that all of these connections are standard equipment on the vast majority of PC notebooks, including ones that cost less than a grand. And there still aren’t as many USB ports as you’d like – you get two ports on all but the 17” model, which has three, and very often only one of those may actually be usable because of power issues.

MacBook Pro [Apple]

The battery life is also greatly improved, but unfortunately is no longer user-upgradeable. See further comments on CDMotion.

Apogee Electronics has just announced they’ve dropped support development for Windows. Now, that’s their prerogative – not least because customers who prefer using Windows can simply choose to buy their competitors’ products. But in a press release entitled “Apogee Discontinues Windows Support,” “Apogee Discontinues Windows Development,” Apogee decides to tell you why, if you’re using Windows, you’re using an inferior platform.

Correction: Apogee just sent an updated press release.

ATTENTION ALL RECIPIENTS: Correction to Apogee’s most recent press release titled “Apogee Discontinues Windows Support”.

IMMEDIATE: Please revise headline to read “Apogee Discontinues Windows Development”

Guess Apogee is either reading CDM, or they just got some email about that subject header. And yes, dropping development of new products is not the same as dropping support for old ones, so this makes more sense (though the arguments I’m making about the tradeoffs between supporting platforms still apply).

Apogee Electronics will no longer develop products for the Microsoft Windows platform. Apogee has made this decision in order to focus all research, development, and support resources on the Apple platform with its unparalleled power and stability. Apple offers a wide range of affordable, powerful desktop and laptop solutions ideally suited for music creation and audio production.

This comes as no surprise, as Apogee’s interface line has already focused on the Mac. And, honestly, maybe that’s a good thing; the added focus could benefit Apogee as a small, boutique vendor.

More helpful advice if you are using Windows:

Windows users can obtain the Apogee sound by connecting Apogee converters to their Windows-compatible audio interface via AES, optical, or S/PDIF. Apogee technical support will continue to support legacy Windows configurations installed on Windows XP Service Pack 2.

Well, of course, that’s correct: if you’re just using Apogee for their converters, you can connect to Linux or FreeBSD or an Amiga or whatever you like, provided the audio interface itself has digital ins and drivers on your OS of choice.

Now, don’t get me wrong, I think Apogee is free to do what they want. It also doesn’t speak well for Windows – it’s a vote against Windows as a platform and the costs of developing for and supporting it. But locking yourself to one platform has dangers, too. Apogee invested a lot of time and resources into supporting their Duet FireWire interface, only to see Apple drop FireWire from their non-Pro MacBook line.

Anecdotally and statistically (in surveys and server logs), we see about 40-50% of you using Windows. So, whatever Apogee’s opinion of the Mac platform’s merits, I don’t see this as making that market any less relevant. In fact, I expect the handful of vendors paying attention to Linux, too, could have an edge as platforms evolve over the coming years. Apogee may be better off focusing on the Mac, but that leaves some opportunities for those vendors supporting PCs.