In a little while, Steve Jobs will be keynoting Apple’s developer conference. I doubt that anyone will be thinking about audio drivers. So in the remaining moments to do that, let’s go — because 10.5 looks like it’s yet another release from Apple that takes music production seriously.

Most of us didn’t expect any major improvements in Apple’s Core Audio in 10.5 — nor need them, as Core Audio is rock-solid for most of what we need to do, in terms of performance and reliability. That’s not to give Apple a free pass; there have been some compatibility issues with point releases (10.4.9 comes to mind), bumps in the AU plug-in format’s evolution, and so on. But at the end of the day, the Mac is an OS that works for music production, more seamlessly and easily than anything else out there. Yet Apple is in fact making some improvements to its audio driver system even in 10.5:

164 Professional Audio Input and Output with Leopard Mac OS X Essentials Presentation
Discover Leopard’s support for the recently-approved USB Audio Device 2.0 class specification and how to write spec-compliant descriptors for your high-speed USB audio device. Find out how to unleash the power of FireWire peer-to-peer networking using Leopard’s all-new FireWire audio drivers and enhanced Audio/Video Control (AV/C) media services. Learn how to implement user interfaces and vendor-specific AV/C commands to control your audio device.

So, wow, in other words … in a release that’s largely focused on Core Animation and the visual side of the operating system, Apple has added new FireWire support, networking over FireWire, and driver-free USB 2.0 support. (Right now, you can plug-and-play class-compliant USB 1.1 audio devices, but not USB 2.0. Erm … or whatever those two USB specs are really supposed to be called; that’s another discussion.)

I’ve been hearing a number of reports that the Mac OS X 10.4.9 update causes significant issues with some Audio Unit plug-ins, including those from popular developers Audio Damage and Ohmforce. (See Analog Industries blog for a comment thread and reports on Audio Damage; there’s also discussion on the Core Audio developer list which I hope will yield some revelations. Update: Note that Audio Damage is having only development issues; their plug-ins will work just fine if you’re a user.) This update apparently installs yet another version of the AU validator, which could be one clue. Apple has also made significant changes to QuickTime in recent releases, which can also cause issues with audio software in some cases.

Your best bet: don’t install the updates the Software Update recommends unless you can easily go back to the previous version. And hold off on 10.4.9 for now.

Users and developers are understandably angry with Apple: rather than bundle updates together, Apple has been making lots of minor changes in successive updates, and developers too often find about changes after things break. That’s especially problematic when the changes are being made to an API like AU — the whole point is supposed to be providing a solid platform for developers. Apple either needs to adjust the way it rolls out updates or communicate better with its developers. Be aware, as well, that the upcoming 10.5 upgrade is an enormous release; I expect you may want to wait for updates to catch up with that when it comes out (when that is, no one knows).

Now, no Windows vs. Mac arguments, please: the bottom line is, developers are having a rougher time than they should on both platforms. (On the Vista side, what I’ve heard from developers is that they had the same difficulties the rest of us did — it was tough to get test systems up and running because of new compatibility and driver issues, so it was hard to test in advance.) Updates and the resulting bugs are a necessary evil, but there’s clearly room for improvement on both the Apple and Microsoft side that could result in a healthier, happier platform for everyone.

I’ve tried, Behringer, really I have. I’ve tried to support and defend you, to explain your quirks and help people use your promising but terribly flawed BCD2000. How do you repay me? You make some OSX drivers, fix compatibility with Traktor, give the BCD2000 a new coat of paint and then sell it as the BCD3000.

There is time, however. You can save yourselves from utter scumbagdom (at least in my eyes). This thing is obviously the same hardware as the BCD2000, so you can do it. Update the BCD2000 drivers and firmware and we’ll never speak of this again.

The alternative is to get crushed by Numark’s NuVJ and Total Control/ION’s iCue, Vestax’ VCI-100, MAudio’s Xponent… Seriously people, when the BCD2000 was announced it was basically the only kid on the block at the price point, 18 months later there are similarly functioned devices from all of the major players, and all you’ve managed is a coat of paint and platform support which was put together by a hacker sniffing USB packets?

Dude, ouch.

The BCD2000 has been somewhat of a contradiction for me since purchase. On one hand the hardware is fantastic; robust and seriously cheap. On the other hand the included software and drivers are absolutely abhorrent, PC only affairs with broken midi implementation. I’ve always hoped that Behringer would update the BCD to have similar (extensive) MIDI configuration options to the BCR and BCF. That hasn’t happened, and almost 2 years after its initial release the BCD is almost in the same position as it started. Almost.

Evinyatar has commented on our early BCD2000 Not Mac Compatible post to announce that he - sick of waiting for Behringer to actually do something useful with their gear - has written and released OSX Universal drivers (MIDI only so far):

My first subject is Behringer’s BCD2000. When it was released about two years ago it was rumored that MacOS X drivers would be released by the end of 2005. Rather than waiting for those to appear (which they probably won’t) I decided to have a go myself. The result is quite good, if I say so myself. It works, which is more than I expected.

Currently only MIDI in and output works. Audio does not. That means you can control Traktor the way you would on a Windows computer, but you won’t hear anything through the BCD2000’s audio ports or record anything trough them. You can still, of course, use other audio outputs, built-in or external, that do work with MacOS X.

Right now the MIDI input and output are should be identical to the Windows driver in B-DJ mode. Which means a reasonable amount of pain is implied when trying to configure Traktor for the BCD2000. Basically, the same hack that works for Windows (using MIDI-Rules and a loopback device, in our case Apple’s built-in IAC) is also required for Mac. I hope to incorporate similar functionality inside the driver in the future, eliminating the need for the hack. For now, this will have to do. A more detailed guide to setting this up will be posted sometime later this week.

Sure, between applications as full-featured as Bias Peak and Apple’s own Soundtrack not to mention freeware like Audacity, Mac users are a bit spoilt for choice when it comes to audio editors. But for those like myself who long for the simplicity and elegance of the long gone SoundEdit, Rogue Amoeba may just have the answer.

Fission is the first (and currently only) OS X audio editor to support lossless editing of MP3 and AAC audio. The software has a super simple interface which provides an accurate dual-waveform view and a handful of editing commands that let you split, cut, crop, and fade audio. While still clearly a 1.0 version, it does have some slick features including audible audio scrubbing.

Fission’s streamlined interface is a joy to look at and use. Its only flaw may be that it is too stripped down for some. With a few more features, particularly support for VST and AU plug-ins, Fission could become my go-to audio editor for those times when bringing up Peak is just overkill.

Fission works with mono and stereo MP3s, AAC, Apple Lossless and AIFF audio files and is available now as a Universal Binary that runs natively on PowerPC and Intel Mac for US$32.