M-Audio has actually gotten in touch in response to frustrations about incompatibilities with OS updates — updates which, admittedly, have recently been frequent and sometimes troublesome on both the Windows and Mac sides. Niels Larsen, General Manger at M-Audio, responds in comments with some specifics on where drivers are, some new drivers that were released literally today, and some comments on the OS situation in general.  (I’ve copied it here just in case you missed it in comments.)

I’ve also heard from Digidesign/M-Audio public relations; I hope to have additional updates soon.

This is well worth reading whether or not you own M-Audio hardware.

Speaking of drivers, PreSonus announced today that they’re allowing users to register for open beta drivers. They’re hardly the first to do this — M-Audio has done the same historically, even if I’m not thrilled with their pace at the moment. But this raises an interesting question: could opening a beta help improve driver quality and get updates in users’ hands faster? Do audio users really want to "beta-test" drivers in the first place? (I guess that depends on how mature the "beta" release is.) We’ll have to see how PreSonus fares.

How is PreSonus doing with released drivers? Reasonably well from what I can see — and what I’ve heard. But they do have some blips. There isn’t a Vista driver for their FaderPort or V-Fire, and there’s no Leopard driver for V-Fire though the rest of their product line is up-to-date with Vista and Leopard.

How have PreSonus drivers treated you? I see a number of improvements in terms of stability on Mac OS on their downloads page via recent releases.

There aren’t many positive ways to spin this: if you’re a user of Digidesign and M-Audio products and looking to use current operating systems, very often you’re out of luck. In some cases, this isn’t so surprising — given issues with Leopard, I actually suggest running Mac OS X Tiger if you can until some issues are resolved. And while I have one machine here running Vista happily, suffice to say Windows XP remains the choice for many, as drivers from a variety of vendors mature.

Still, I think it’s bad to see drivers missing altogether this late in the game — especially in the case of Windows XP SP3, a minor update to a six year-old OS. Maybe some of this isn’t M-Audio’s fault — maybe OS driver development needs to be easier. But either way, when a major music hardware vendor is this far out of sync with the software shipping on new machines, it’s a problem. And while their loss may be good for their competitors in audio hardware, it’s not terribly good for the music tech industry in general.

(Okay, Digidesign/M-Audio — before you start throwing things at me, I’m not saying this to be mean or to single you out, I’m saying this because I hear this all the time from your customers. I think if there are problems on the Apple/Microsoft side, then that’s worth examining, too. But I do think this is a situation that could stand some improvement.)

Background: Many laptop-based Mac OS X users are experiencing significant audio issues on Mac OS X Tiger and Leopard. On Tiger, the culprit appears to be the AirPort Extreme Update 2008-001 released earlier this spring. One workaround on Tiger is to simply turn off AirPort. On Leopard, the problem appears to be slightly more complex, but generally linked to 10.5.2; several software vendors are recommending music users avoid that update for now. (10.5 / 10.5.1 appear unaffected.) The issue is not universal on Leopard (some laptop Mac users report no problems), but if you are experiencing issues, the only current solution appears to be downgrading your entire system to an earlier release (via Time Machine or reinstalling).

Fortunately, on Tiger there’s a more specific temporary fix.

Tiger Fix: Musician Georgi Marinov has posted step-by-step instructions for reverting the AirPort Extreme Update to the previous release (2007-004). This fix will work only for Tiger users, apparently on specific MacBook Pro and Mac mini models.

tiger airport audio dropouts fix

I’d personally like to see Apple add some facility for uninstalling updates on all releases, as some other operating systems do. (Yes, you can use Time Machine, but that’s more of an argument for building this feature into Software Update.) But regardless, with any OS and any update (and certainly with this unsupported procedure), be sure to backup before applying any update to a critical machine.

If you do apply this, let us know if it works for you.

Previously:

Mac OS X 10.5.2: Music and Audio Problems on Apple Laptops? (Or Blame AirPort?)

Mac Audio Glitches: Serato Reports; Avoid 10.5.2, AirPort For Now

Photo: Telstar Logistics. (Hey, it was either that shot of SFO airport or another apple or tiger or something silly.)

Update: via Kris on comments, it appears the newest ("Penryn") Apple laptops are unaffected, presumably a side effect of using Broadcom chips. (That’s not to say the chip is to blame, but the software support for the different chips might be.)

Apple’s "point" releases — those seemingly-harmless updates you get automatically in Software Update — do sometimes break stuff. I tend to ignore the updates until I’ve had a chance to confirm they’re okay. Case in point: it looks like 10.5.2 can result in glitchy audio on laptops.

Native Instruments has an official statement out on the problem, but according to them, this issue can affect software from other vendors, as well:

User feedback and internal testing indicates that recent changes introduced by Apple in Mac OS X 10.5.2 can cause audio dropouts and similar problems on Macbook/Macbook Pro computers. This issue is not limited to NI software in particular, but applies to performance-criticial music software in general.
Therefore, Native Instruments currently cannot guarantee the proper operation of its products under Mac OS X 10.5.2. If possible, users should refrain from upgrading beyond Mac OS X 10.5.1 until further information about this issue becomes available.

Now, I will say this: I am frustrated with Apple’s OS upgrade approach — and I think on any OS, media support is the most vulnerable area.

It’s been almost a year since Windows Vista was released to consumers. We know that nearly half of our readers use Windows, so the future of the OS is something we take very seriously — even if many of you, for now, are staying cautious and working (happily, in many cases) on XP. We’ll be examining Vista from various angles over the coming weeks, both measuring the OS and telling you how to make the most of it if for music you are giving it a go.

To start out, we’ve again caught up with Noel Borthwick. Noel CTO of Cakewalk, and one of the most knowledgeable experts on Windows technical details. (He’s also a veteran Linux developer, so his perspective on operating systems goes beyond those from Redmond.)

When we talked to Noel this time last year, a lot of what was new still hadn’t been tested in the real world. Now, Vista has been in the hand of users, and there’s both some good news and bad. A year of Vista has meant a year of improvements, both from Microsoft and third parties. In my own testing, for instance, what began as a disastrous experience running Vista earlier in the year has now become more comparable to XP. (I’m currently on Vista SP1 release candidate on a modest PC desktop.) But there are still areas that could use improvement — and while general Vista improvements were welcome, I think there’s still the real question of whether Vista offers enough that’s unique to compete with its real rival, XP.

We’ll revisit some of those broad issues, but first let’s actually get the technical story, and clear up some misconceptions.

Much of the OS discussion tends to devolve into generalities, philosophical debates, and religious wars. We’re going to try something different: wherever possible, squash the bugs. Here’s a tip for Windows Vista that finally allowed many of my USB devices to work properly.

Many music devices, including simple audio interfaces and (in particular) USB MIDI keyboards, don’t require drivers. These are sometimes called class-compliant devices, as they’re covered by standardized classes that describe what they do. There actually are drivers for them, but they’re provided by the operating system. And that’s a good thing.

Unfortunately, many people have found that Windows Vista has problems finding the drivers for these devices. Here’s a fix that works for me (and, apparently many others):

Your ears and mind are incredibly sensitive to tiny details of sound. Result: if your operating system can’t keep up with sound output for any reason, you’ll get a noticeable “glitch” in the sound — and that’s a big deal. Windows Vista promised to be “glitch-free” in development, later reworded to “glitch-resistant” or “glitch-resilient.” Then it shipped, and a lot of us noticed it was, well, just plain glitchy, at least at the beginning of this year when Vista met up with half-finished, buggy drivers.

All operating systems will glitch under certain circumstances, though, and the causes are many. Microsoft has a great post on their Vista Team Blog today from Steve Ball, who seems to be a really sharp guy and has a great handle on how Vista can continue to improve in terms of audio performance.

An Overview of Windows Sound and Music “Glitching” Issues

Well worth reading, whether you’re a Windows user or not. (Linux and Mac can absolutely encounter the same issues, and as you look through the full list of possible causes you’ll see why.) There’s quite a lot missing from this discussion, but the blog promises this is part 1 of 2, and you’ll find some more meat in the discussion in comments.

I did enjoy this description of why we’re so bothered by glitches:

My colleague on the Windows Sound team, Larry Osterman, also pointed out to me recently that humans are actually “hard-wired” to be disturbed by audio glitches. In an exchange about this topic, Larry observed that audio glitches are more obvious than video glitches because the ear’s tuned to notice high frequency transients — his visceral example of this idea is an image of a stick snapping in the woods behind you as an audio event that wakes you up before a bear wanders into your path.

I think I have the same visceral reaction to software bugs. (Help! A bear!)

I’m writing this from Vista right now, and I have to say, I found all kinds of reproducible glitching problems early on. But now, various hotfixes and driver updates better, Vista’s audio performance is running really smoothly for me. I think the major culprit on Vista in the early months of the release was video drivers, an issue which for me, and many others, has finally been fixed.

Some of my favorite audio interfaces are now available for Windows Vista. The INSPIRE 1394, FireBox, FP10 and FirePod are now all available for 32-bit and 64-bit Windows Vista. A bit late? Yes, but at this point, I care more about quality than punctuality. Anybody with the PreSonus boxes and Vista, we’d love to know how they’re working.

PreSonus Vista Downloads

Note that when you’re talking about FireWire, you’re talking ASIO and the new driver model under Vista. “WaveRT”, technology that allows greater audio performance of some hardware under Vista, is a feature that’s not supported by any FireWire or USB devices. (GearWire posted a splashy headline saying Native Instruments wasn’t supporting WaveRT, when really that just translated to “NI Only Makes USB Interfaces.” I can forgive the confusion, given the various Vista driver complexities, but let’s just say — look for Vista-compatible and leave it at that.)

I still can’t see running 64-bit Vista, even for a marginal performance gain, as it knocks out some significant hardware and software compatibility. But, as Craig Anderton just observed in his preview of Cakewalk SONAR 7 for EQ, one advantage of the new SONAR is that it’s basically a complete 64-bit music toolkit, with some decent bundled instruments and the awesome Z3ta+ synth.