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.

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.

Generally, Mac OS X 10.5 Leopard has been working pretty well for most users, though we continue to hear a number of complaints about compatibility with M-Audio hardware. There are some annoyances, though, including one glitch as far as routing audio between apps. Updated: the good news is, this is fixable.

In the “bad” category, Paul Davis, the creator of JACK and Ardour, writes:

Leopard has stopped JACK and other inter-application audio routers from being used as the default audio device. Apple is now distributing an SDK that is aimed at “aiding” developers in writing user-space CoreAudio “drivers” such as JACK and SoundFlower. Early reports suggest that the SDK requires a much more complex design. JACK still runs on Leopard, and so JACK-aware apps (i.e. Linux audio apps ported to OS X like Ardour and Jamin) can use it, but native apps can no longer be connected to each other or to JACK applications. Work is underway to make JACK use this new SDK but it appears to be a non-trivial effort. Apple’s motive in making this change is not clear.

Now, the good news. JACK OS X’s developers chime in in comments to point out progress is being made. And this is even a good thing. (Unfortunately, such is the way with OSes — for even small improvements, you have to break, then fix things, then reap the benefits, sometimes not immediately.) From Stephane:

SoundFlower is actually a “kernel space” driver that is somewhat much more easier to develop and maintain

• Apple SDK is definitively a step forward to develop more compliant “user-space” drivers, even if mastering the new code layering takes some time…
• as Dan said, the new version is almost ready and should be more compliant (more application working correctly with it)

And a beta is available now.

In other words, if you use these apps in a critical project, you might want to hold off upgrading, but otherwise all is well. I’ll be sure to post an update when a fix is ready. Note that Audio Hijack is now compatible with Mac OS X 10.5, though that doesn’t allow many of the musical applications possible with JACK and SoundFlower.

A subtler UI annoyance, Apple has somewhat crippled the audio previews you get in Finder’s multi-column view. You get the “play” button in the last column, as before, but no scrubbing or volume control. QuickLook, fortunately, solves the problem. Hit space and you get a full view of your audio file. At first, I thought this would be less convenient, thinking you’d have to preview files one at a time. But you can navigate from one file to another by scrolling up and down with the keyboard to select different files. Thanks to David Hollands for this tip; David says he’s finding QuickLook to be slower than using multi-column view.

Another alternative would be to use a dedicated utility like Iced Audio’s AudioFinder for your sample sorting, which may be better than Leopard or Tiger anyway, depending on your preference.

Sure enough, today we learn that AudioFinder’s new sample editor is in beta. Combined with AF’s other sample juggling tools, the fix may actually be more interesting than the problem.

Digidesign has “announced” their Vista support information, but it’s leaving some users scratching their heads. Fully a year after Windows Vista went Gold Master, Digidesign doesn’t seem to be able to get a clear support picture together. How odd is Digi’s Vista support? Let’s see:

• Only Windows Vista Ultimate and Windows Vista Business are supported, not Home Premium — even though that’s a version typically bundled by default on most new Vista machines. This makes absolutely no sense whatsoever, as hardware support for audio is identical across versions, even in Vista Basic, and not a single other developer in the industry appears to be taking the same approach.
• M-Powered and LE are supported, but no HD. And, in fact, there’s not even an announcement about when to expect HD support.
• Digidesign still has no 64-bit support. Maybe not a deal killer, but SONAR has had 64-bit support for ages, and even Steinberg recently got in on the game with Cubase and Nuendo in a technology preview. MOTU has 64-bit Windows drivers, among others.

All of this comes with basically no explanation. If the operating system really isn’t ready, couldn’t Digidesign say so, or give some timetable on when they expect the situation to be remedied? And what’s the deal with failing to support Home Premium, again with no reasoning? This seems like not simply a failure of support, but a failure of communication. Vista may not be perfect, but given the number of PCs shipping with the OS onboard, ignoring it entirely doesn’t seem like a reasonable option. Maybe some more details for us, Digi? (I’ve had problems with Vista, but support from music software and hardware makers I’ve actually found to be good, with this exception.)

Information on Pro Tools Compatibility with Windows Vista [Digidesign]

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.

Native Instruments and MOTU have each posted compatibility update pages for Mac OS X Leopard. There’s not a whole lot of information yet (particularly form MOTU), but now’s the time to bookmark those pages!

Be sure to watch comments from readers for other helpful compatibility information — much of it positive at this point.

Native Instruments: Compatibility with OS X Leopard
NI’s latest versions of Kore, Traktor, Guitar Rig, and Kontakt are all good to go. But other software has some issues related to installation and dialog box operation. While it’s not reported on this page, we’ve also heard one person with a hardware problem. You should see patches over the coming weeks, with major updates in November and December.

Unleash a Leopard in your MOTU studio
Despite the title, actually, you might not want to unleash anything just yet. MOTU says testing is ongoing and hints updates for hardware and software may be likely. MOTU’s virtual instrument line is ready, though, and there are no significant issues reported yet. Best bet: bookmark that page and keep watch. That’s what we’ll be doing.

Tiger in your tank? I’ll say it now: while the issues are minor so far, I don’t recommend upgrading to Leopard on a critical machine. For folks with more than one Mac, many are having relatively smooth experiences, so on a second machine it could make sense. I’m expecting most of the rest of us will just wait a month or two; at least on the Mac updates are usually pretty speedy in coming and the OS itself looks solid.

Oh, yeah, and one other important thing: this is the first Mac OS X update that really doesn’t benefit music users, at least not out of the box. (There are some driver changes, but I don’t think there are yet devices that take advantage of them.) It’s actually good news, in that Core Audio and Core MIDI are mature at this point — you don’t want to regularly update the music and audio plumbing. But that means Tiger will be just fine for some time.

More Java bad news: While I know this interests a smaller audience, there’s been still more disappointments on the Mac Java front.