Software update for both MC Control and MC Mix that fixes compatibility issues with Mac OS 10.5.7. Includes recent MC Control touch-screen response optimization, as well as improved Digital Performer integration and more.

http://euphonix.com/artist/support/downloads.php

We live and die by hard drives for music. There’s no substitute for redundancy and backups (hey, you could be Matthew Dear and have a drive stolen during your set). But it is helpful to know whether a drive is healthy or not. S.M.A.R.T. monitoring features built into drives can help.

Lifehacker today points to a free Windows utility for the job called CrystalDiskInfo:

CrystalDiskInfo Monitors Hard Drive Health and Uptime [via gHacks]

But that got me thinking about other tools. There’s quite a range of choices for Mac, Windows, Linux, and even some obscure operating systems. The only bad news: generally you’ll only be able to monitor internal drives, unless your external drive is eSATA rather than USB or FireWire. (eSATA is where I’d like to go generally – it’s quite a lot faster, and frees up your USB and FireWire buses for other things — but that’s a discussion for another day.)

Cross-platform / Linux

The smartmontools package is a powerful ATA/ATAPI/SATA monitoring tool that runs on – well, pretty much everything. There’s a Windows package, plus a *nix version for Mac, Linux, BSD, Cygwin on Windows, Solaris, OS/2, QNX, and so on. This looks like your best choice on Linux.

Mac OS X

SMARTReporter (pictured at top) is probably the friendliest way to get at SMART data for SATA, ATA, and eSATA drives on the Mac. It even includes a handy menu bar item so you can monitor how your drive is doing at a glance. It’s free via Open Source “MIT License.”

You can also use the command line, via something like this:

diskutil info disk0 | grep SMART

Windows

In addition to CrystalDiskInfo, you have a number of options:

SpeedFan is a general-purpose monitoring and management tool for just about everything, including (as the name implies) fans.

HDD Health is a hard disk-only monitoring tool, like the others here. One thing it has going for it: friendly feedback and tidy tabs to view it.

More Information

The good folks at SpeedFan have an article on what SMART is and how to interpret data you get – well worth reading whether or not you’re a SpeedFan user.

Yesterday marked the official phase-out of Windows XP. That in itself isn’t terribly big news; it’s easy enough to get XP systems for the foreseeable future, and custom builders can even put together an XP machine for you. Heck, you can even boot XP on an Intel Mac. But it seems like the perfect time to talk again about Vista. As with any OS, the branding (“we’ve got a new thing called Vista”) masks the more complex reality evolution of software and drivers. In other words, Vista today isn’t what it was the day it shipped. (That’s a relief.) And personally, I’d like to start talking about real-world performance and dispense with the kind of schoolyard rivalry the platforms have had over the years. I think it’s a safe bet to say none of us is excited about operating systems. We’re excited about actually making music. The good news is, Vista is finally looking like an OS on which you can do that.

The OS Generation Gap

It’s a funny time for operating systems and music applications, in that the most recent generational changes in Windows and Mac were unusually significant. On Windows, XP and Windows 2000 improved both audio and hardware support, and finally saw Windows NT really mature for music. On the Mac side, albeit slightly later, the bumpy transition to Mac OS X finally paid off as Tiger and Panther brought major audio improvements and reliability and performance enhancements. And Tiger got musicians onto Intel x86 CPUs, which helped unleash the live use of laptops we see today. Each of these updates came with compatibility hurdles, but there was a clear payoff. They’re must-have upgrades for music. Many music and audio apps won’t even work with earlier versions.

By contrast, while Mac OS X Leopard and Windows Vista each introduce important features, they’ve proven less essential to the music and audio segment of the market. By extension, I’d say they haven’t yet made major enhancements to real-time performance or hardware support – at least not in a way you can currently experience as an end user – in the way their predecessors did. That’s not to say you won’t find reasons to upgrade; you just may not see a big difference in Ableton Live. That has made the compatibility issues each OS has introduced for music more painful, because the reason you’re upgrading may not always be as clear.

But don’t listen to anyone who says OSes are so mature that there’s “nothing left to do” to them. I don’t think that’s the problem. Leopard and Vista aren’t entirely comparable, but they do have a lot in common – and the common theme, beneath eye candy in the UI, is that both OSes are trying to tackle some very difficult problems.

Both make changes to the driver model, thread scheduling, multiple core support, and (including XP x64) 64-bit support. These are tough challenges for OSes that have years of development behind them and broad compatibility requirements. But these are changes on which computer musicians, even indirectly, are absolutely dependent. Support for better performance, more reliable drivers, and more memory is vital to a lot of the stuff we do.

The issue is, you may not see some of the payoff in these changes right away – or even in this OS build. Even with Apple’s Mac OS X Leopard, which has been relatively positively received, I think some of the real benefits of multiple core support and 64-bit compatibility won’t become evident until the upcoming Snow Leopard at the earliest. Microsoft’s under-the-hood driver model changes may have a positive impact on driver reliability and performance in the long run, but those benefits have been masked by just getting things working.

Microsoft had still-bigger challenges, too: while they jettisoned some much-publicized functionality promised for Vista, they still made massive changes to driver support, the graphics driver model, and the way things on the screen were displayed.

So moving onto Vista: did something go wrong? Yes – at the beginning, that is.

Vista, Take One: Yipes!

For all the over-analysis of what bombed in the Vista launch, I’ve been surprised by how little attention has been paid to what seems to have been the single biggest issue. Vista’s new graphics model just didn’t work for a lot of people out of the box, and that caused other issues to snowball. This is especially true in audio. If the graphics drivers weren’t working properly, just touching a UI element could make the sound glitch. Some people I think misunderstood the source of the problem and blamed DRM or other more dramatic causes. But if anything manages to starve the CPU for cycles, performance suffers fast.

I saw how nasty this could be in my early Vista tests – and was equally struck how dramatically the fix could be when installing new drivers, particularly on my NVIDIA test systems.

Would it have helped if Microsoft had kept its vendors more in sync? Absolutely. Should Vista have held off a little longer to resolve lingering quality issues? I think so. Should Microsoft have hired acrobats to climb buildings and staged other surreal Cirque-du-Soleil style antics to launch an OS before it was ready? Sigh.

Those things aside, though, some of the problems remain fundamental OS issues — and many of you, as a result, were smart enough to steer clear of the OS upgrade until it was fully baked.

Here are some obvious but oft-missed statements in regards to Vista or any other major OS change:

1. Small incompatibilities can cause total havoc. One bad driver can starve the CPU, crash the machine, and generally make performance and stability go awry. Sometimes these bugs come from the OS vendor, sometimes a third-party developer, sometimes a combination of the two that can’t even be fully explained until it’s fixed. And that makes other, arguably more minor incompatibilities, all the more annoying. Problems with video on Vista pushed it out of the “I can live with this” territory and into the panic you saw from a lot of tech users and even press.

2. Music and audio suffer first: Running many apps, you won’t notice sluggish performance. Run video, and you’ll notice a missed frame (about 30 of those per second). Run audio, and you’ll notice tiny timing problems and dropouts and glitches with even a single sample (about 44,100 of those per second). Audio real-time performance is less forgiving than applications like nuclear submarine guidance – literally.

3. If you’re having a problem, who the (*&$# cares how many other people are, too? If you’re having an issue, you’re sad. If  If you have a problem, you have the right to complain about it until it’s fixed. And you get permission to curse at the machine involved and the company who made it – until they fix it, at which point there will be great rejoicing. I’ve seen bloggers complain when people complain about significant problems with both Mac OS and Windows. I gain great comfort in knowing next week, they’ll be the ones cursing because they’ll have the problem. Let my people vent. And fix the problem. Then everyone’s happy.

SP1: What Changed

So, is Microsoft fixing things? The short answer is yes. It may not be a reason to switch from XP to Vista, but I do think Vista is a feasible choice for music production, depending on your environment.

I wouldn’t have said that a few months ago. Vista has changed since where it was even at the end of last year. SP1 is part of that, but changes generally fit into three categories:

1. Internal (Hotfixes): A big portion of SP1 is a big bundle of all the hotfixes that Microsoft released over the first year or so of Vista. It’s just a convenience – you could install all of those hotfixes without SP1 – but it’s a major one. And many of those hotfixes made specific improvements to audio performance, video performance (which also impacts audio performance), and USB and other hardware compatibility.

2. Internal (SP1): SP1 includes some changes that were not released as hotfixes, meaning that in addition to #1 being a big reason to upgrade, this is the only way to get a fully-patched, fully-fixed Vista.

3. External (Third-party): It goes without saying that, aside from what Microsoft has done, third-party vendors have fixed a lot of stuff since Vista’s release. Aside from software patches to music software and plug-ins, that includes changes to mainboard drivers, video drivers, and the like that can in turn impact audio performance and reliability.

We covered some specific Vista audio concerns in the past:

So let’s see how SP1 is addressing those concerns.

Vista SP1 + Music: Report Card

Complaint: Vista’s MIDI Timing is unstable.

Validity: True.

Current status: Fixed in SP1.

Vista introduced some MIDI timing instabilities. It was bad enough that at least some users were able to notice the difference in terms of hands-on experience. Cakewalk, who reported this issue to Microsoft, tells CDM that the problem was fixed as of SP1. (Microsoft previously indicated to CDM that this would be addressed.)

Complaint: Vista audio performance is unreliable: dropouts, glitches, and pain.

Validity: True; not an issue in all cases but reasonably widespread.

Current status: Fixed (at least in many cases). Vista performs like XP — once your video drivers are up to snuff.

Assuming we’re talking primarily about ASIO performance, which requires stability at low latencies, the biggest obstacle early on appears to have been buggy video drivers causing catastrophic audio performance. (If you doubt that incompatibilities not directly related to audio can cause problems with audio, look no further than the bugs gradually being resolved on Mac OS’ WiFi support and Leopard USB/FireWire support.)

Turning off Aero, Vista’s shiny, new UI, doesn’t necessarily fix things in all cases, either. Even with "Windows Standard" selected, Vista uses a new driver model for graphics. (It can be helpful to turn off Aero or other desktop visual effects on an older machine, however.)

Mainly, the fix seems to be installing SP1 and getting video drivers up to date. For that reason, I can’t entirely guarantee this — there are lots of other variables and different possible graphics drivers. But if you’re having symptoms that seem to relate to UI interaction like moving windows or turning soft synth knobs, starting with the graphics drivers couldn’t hurt.

Complaint: Vista can’t achieve the low latencies XP could.

Validity: Difficult to verify.

Current status: Jury’s out, but unless you’re counting milliseconds you’ll be fine — and very reliable, low latencies are possible with Vista as with XP.

Latency is introduced in various parts of a computer music setup, but generally if you’re in the 10-12 ms range and no higher, most users will be happy. I’ve been able to easily push below that even using a USB interface like my Native Instruments Audio Kontrol 1. (Apparently, they hired a very talented driver programmer, so Native, I’m not giving you that one back! Send a bill over.)

Some users do push Windows latencies well below that, and have reported that Vista isn’t performing quite as well as XP. Now, whether driver updates could resolve this, I don’t know.

I can say this: you can get very usable low-latency performance with Vista, just as with XP. As always, the main variable is getting an interface with solid drivers you can trust, and (unfortunately) controlling for other variables like buggy video drivers. On any system, I suggest testing adding new hardware very carefully. But this issue in and of itself seems to me not to be a reason to avoid Vista. (Now, other compatibility problems that can botch audio? That’s a good reason — meaning you will want to test your system before doing something critical with it!)

Complaint: Vista’s WaveRT can yield better audio performance on built-in cards.

Validity: True.

Current status: Your mileage may vary, but if you can get WaveRT support you’ll be much better off than you were on XP.

Vendors Realtek and Analog Devices, who ship the internal audio cards including on many motherboards and laptops, have each supported Microsoft’s new WaveRT driver model, which is intended to provide lower latency for “consumer” audio functions. We knew this would help theoretically, but from reports we’ve seen, users have been pretty happy with this feature in the real world, too. I’ve even heard reports of extremely low-latency playback (as low as 2ms), which had previously been possible only using ASIO. While we’d need more extensive benchmarks to go into greater detail, there’s no question this is a big leap forward from previous drivers for internal audio cards, so this is very good news for those times when you don’t have a dedicated “pro” audio interface handy.

In fact, I could even see someone making use of one of these cards in live performance or installation. If you have, let us know.

Complaint: My (hardware/software) isn’t compatible.

Validity: Check with your vendor.

Current status: Largely fixed by third parties, and certainly most music and audio developers, but always check first.

I’ve been fairly impressed by compatibility between Vista and current music hardware and software. The first half year was, as always, rough, but things smoothed out after that. If you’re concerned about compatibility with older plug-ins, for the most part, don’t be. Once you have a compatible host, plug-ins generally work on Vista as they did on XP — meaning Windows still has Mac and Linux beat when it comes to giving you ridiculously absurd plug-in variety, enough to distract you from ever getting any actual work done. (Not sure if that’s a plus…)

With hosts and hardware, well, there’s not much I can say other than check with your vendor. But on my machine, with hardware from Focusrite, Roland/Edirol, Native Instruments, Novation, M-Audio, and Korg, and software from Native Instruments, Ableton, Image-Line, Cakewalk, Cycling ‘74, and various other obscure things, compatibility hasn’t been a problem. In fact, I think music and audio vendors were more on the ball than the rest of the industry.

If you do have the rare older software that doesn’t work, you can often get it to install and function by turning off User Account Control temporarily or selecting a compatibility mode before launching.

That said, if you do have a lot of older software, I wouldn’t recommend upgrading. If you’re not upgrading your apps, upgrading your OS is unlikely to be a good idea. (The phrase “if it ain’t broke…” comes to mind.) But if you’re running current hosts and audio interfaces and just want to protect your VST plug-in stash, I don’t think this aspect will be a deal-breaker.

Complaint: Vista requires more memory than XP.

Validity: True.

Current status: Unchanged, but it may not be a deal killer.

There’s not much escaping this, but rather than dwell on this, I’ll say this: on a 2GB system, I haven’t found this to be a problem. On a system with 1GB or less, I run XP anyway. End of story. I don’t see a reason to run Vista on an older system or one with less memory, and likewise on a 2-4GB system I don’t think Vista’s memory consumption is significant enough to impact audio work. On a 64-bit system with 64-bit software, which can easily access well more than 4GB, it’s a non-issue.

Nitpicking on memory availability is probably overkill, but of course musicians — unlike mainstream users — do often push the envelope. But on my custom Vista desktop install, which only has a 2GB system, I’ve been happy.

There are things you can do to "slim down" your Vista install, as with XP (actually, literally as with XP in some cases as some of the services are the same). The new Windows Sidebar, for instance, consumes some memory and can be switched off. (I don’t miss it it, personally.) But that’s a topic for another article.

Complaint: Vista requires more power than XP.

Validity: Vista’s (usually) not the problem.

Here’s the thing: you can see massive CPU consumption when software crashes or drivers aren’t working properly. Many of these are reported under the process explorer.exe, because processes run as part of that larger process. On the hardware side, even a slightly-unseated PCI card can cause major CPU spikes. And if you are getting those kinds of spikes, the power of your hardware won’t make any difference. This isn’t really a Vista issue – if stuff is compatible and working, you won’t see the problem.

So, was this true? Yes, probably — but my suspicion is that a lot of these complaints actually originated from buggy drivers and unstable processes, not an inherently hungrier OS.

That said, I do wish Microsoft had made it easier to slim down their OS, in general. And I have found a couple of things especially annoying with Vista:

Media Center: I’d like to be able to switch off Media Center altogether, especially because a process called mcupdate.exe seems to randomly call the mothership and consume CPU cycles. Updated: Richard Burte wisely points out that you can disable this using Task Scheduler. Type “computer management” into the Start menu and select the first result to bring up the Microsoft Management Console. From there, select Computer Management (Local) > System Tools > Task Scheduler > Task Scheduler Library > Microsoft > Windows > Media Center. In the top right pane, you’ll see the task mcupdate. It’s set to run at 4:51 pm daily. You can reschedule it, or simply right click it and choose disable. Thanks, Richard!

My recommended Vista version remains Vista Business. If you’re using a machine for music, odds are you don’t need Media Center’s features anyway – especially not with plenty of media playback options elsewhere.

Desktop Search: For reasons unknown, this service can index and churn away at the hard drive even when it’s not supposed to. I prefer to turn it off, but I’d like to see it get a little smarter about indexing more efficiently and switching on more conservatively.

Bottom line, though, is that Vista, like XP, can be tamed and turned into a well-behaved OS. That wasn’t true in the initial Vista driver train wreck, but I’m finding it’s true now – and that’s a good thing.

Complaint: Vista is full of audio DRM that will ruin your life.

Validity: Not true.

This complaint seems to have come from two sources. First, it seems to be partly a misinterpretation of audio protections Microsoft had to put in to support new US digital cable tuners and formats like HD-DVD and Blu-Ray. Those are in fact in Vista, though they’re also in XP, and they don’t really impact music production. (They’re annoying, but that’s a separate discussion.) Second, Microsoft did apparently plan to do more with DRM in Vista than they did, but backed away from the cliff. Some people were still looking at planning documents and seeing things that weren’t there.

Where I think this rumor continued was when people had glitchy, unreliable audio and blamed DRM, but as I said above, I think they didn’t suspect culprits like video driver problems.

Unfortunately, Microsoft did add some additional validation requirements in Vista as an anti-piracy measure. These are softened in SP1, and I think you can live with them. It does reduce your options for virtualizing the operating system using tools like Parallels, VMware, and virtualbox, but if you’re virtualizing an OS, why not Linux?

Why Run Vista?

I don’t want to get into a Mac versus Windows argument here. That’s an easy one. Want to run Mac OS? Do it. Want to run Windows? Go for it. There are enough choices and enough mature software that you’re unlikely to really regret either one. And it doesn’t really matter which is "better" so much as which is better for you.

Instead, I’ll take on something slightly simpler: XP versus Vista. It’s clear why you should run Windows XP:

1. It’s working, and you’re happy: Insert any software here (Windows, Mac OS, your word processor, your MIDI sequencer), and this statement is true, but it’s worth saying.

2. You’ve got an older machine, or are low on RAM, or both: This is doubly true – older hardware is likely to have the most compatibility problems now that newer drivers have caught up with Vista. And XP is a better choice with less than 1 GB of RAM.

3. You need it for specific compatibility reasons. ‘Nuff said.

But why should you run Vista? Believe it or not, I have a few reasons.

1. It can be more stable than XP. No, you didn’t read that wrong. Microsoft has improved the in-box drivers in Vista, and the driver overhaul has forced vendors to adhere more closely to Microsoft’s specs. Now, I have no particular need to believe what Microsoft tells me — but I have seen this make a difference in the real world. Also, because on many modern machines Vista supports more hardware out of the box than XP, you can go with Microsoft’s in-box and device class drivers, which can be more reliable than drivers that come from vendors.

2. The UI is more usable. I don’t mean in a skin-deep way: generally speaking, the UI in Vista is more usable and functional than XP’s in some subtle but important ways. For instance:

3. The audio mixer is great. Click the sound icon on the taskbar, and there’s a mixer that lets you disable applications. It’s a little thing, but worth mentioning.

4. GPU-native UIs are a good thing. If you have a fairly recent graphics card – even a basic one – I think you’ll probably appreciate glitch-free graphics display on the UI.

5. It is prettier. Aero tends to elicit love/hate responses. If you don’t like it, you can reskin it by using a hacked uxtheme.dll, as with XP. (Search for uxtheme.dll and you’ll get some solutions; various minimalist skins are available online, too.) But Vista is generally easier on the eyes, and improves font rendering and such in a way I find easier to stare at all day. I was surprised that even Create Digital Motion’s Jaymis actually warmed to the new Vista UI on a new PC — and he just bought himself a MacBook Pro for Mac OS X.

6. WaveRT. Internal audio systems work better on Vista, so long as they have WaveRT drivers and apps to support WaveRT. That’s a big enough feature that, assuming you can balance other factors, Vista could be worth an upgrade.

7. Explorer is multi-threaded and more better. While early versions of Vista prompted complaints about file copy speeds, those issues appear to be fixed now, and I find Vista’s Explorer to be much snappier. Multi-threading means Explorer doesn’t grind to a halt any more. I also find Explorer far more usable than it was in XP. Some XP loyalists disagree, but I think they’re crazy.

8. You’ve got a new system. Before you try to put XP on a new machine, it’s worth giving a test run on the stuff that matters and seeing if Vista works.

I’ll admit, I wish this list were longer, and I hope that with Windows 7, it is. But is it worth waiting for Windows 7? I don’t think so – not given that past experience, even on the Mac with its more controlled environment and musical focus, suggests that any OS transition takes time. The day Windows 7 ships will likely be a lot like the first day any OS ships – fraught with compatibility problems. Vista is, at least, finally reaching maturity, and I hope that Microsoft continues to ship patches where they’re needed.

Conclusion

I brought up the Mac just to reiterate something that’s obvious but important: musicians rarely upgrade to a new OS on day one, period, regardless of platform. (Even on desktop Linux, in fact, most stable music and audio systems are using distribution releases behind the latest, fanciest, "experimental" release.) The good news is, we’re not alone — Ed Bott observes today that businesses like Intel holding off on Vista are repeating cautious behavior from the past. Frankly, I’m with them. (I’ve had to make a conscious effort to adopt things too early so I can write about them!)

In short, if you held off on upgrading to Vista, it’s paid off.

If you’re happy on XP, there’s really no pressure to leave.

But I can happily say that, at this point, you can at least consider Vista. I don’t think it’s the doomsday release some made it out to be — though, in fairness, the way it shipped in the beginning I was inclined to agree with them.

And, ironically, at the end of the day I don’t really notice that much which OS I’m using. I’ve got some XP, some Vista, some Mac OS. CDM contributors Liz Knight, Mike Una, and Motion editor Jaymis all use multiple operating systems, too. The fact that we don’t notice? A very good thing, and a testament to the work developers have done to make sure that’s the case. And a far cry from the OS-centric turf wars regularly going on on the blogosphere. But then, we have more interesting things to discuss.

A big thanks to Noel Borthwick at Cakewalk and Robin Vincent at Rain Recording for providing some feedback as I wrote this. The opinions expressed are my own, but I encourage you to disagree — in fact, we’re looking for as much data on musicians and operating systems on all platforms as we can possibly muster, so don’t be shy.

Now, back to music.

Previous Resources on CDM

Summing up some of the growing pains OSes have been having lately:

Digidesign Talks Latest Windows, Mac Releases, Compatibility, Drivers

Fix for Mac Audio Dropouts: Roll Back Tiger AirPort Support

Blame Apple, Not Your Driver Maker, But Leopard Fix May Be Close

And specifically Vista-related:

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

Vista Bug Squash: Fix Driver Installation Problems with Class-Compliant Devices

Windows Sound Glitches Explained, Plus Glitches and the Fight-or-Flight Response

Microsoft Rolls Out USB Fixes for Vista Now; Not Everything Waiting for SP1

Cakewalk Vista Musicians’ Resource Page, Lots of Vista Drivers

How to Kill Windows Vista Bottlenecks: Pt. II, Stop the Disk Churning

How to Kill Windows Vista Bottlenecks: Pt. I, Aero and Display Issues

Vista “Content Protection” DRM Won’t Impact Music Production, Says Microsoft and You

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

We suspected AirPort issues with both Leopard and Tiger; many of you reported the simple fix was to turn AirPort off. The latest update:
“Addresses AirPort issues that may result in slower performance in Logic Studio or MainStage.”

Now, that’s oddly worded. Unless there’s some really specific interaction between Logic and AirPort, but no other audio apps, presumably this line actually means “…that may result in slower performance in music and audio applications.” Update: Readers tell us that’s exactly the case. So, Apple, why not simply refer to audio production apps, since third parties depend on your OS, too?

Leopard is gradually getting fixed for real-time audio performance so the number of you with problems is waning, but those of you who have had trouble through 10.5.3 with AirPort on, let us know if this fixes software from Apple or anyone else.

About the Mac OS X 10.5.4 update

DP6 is here (or will be here soon, say commenters), with a badly-needed UI update and a number of new features. The results still look like DP – in the way that should appeal to current users, that is – but enhancements demonstrate that the ongoing DAW battles carry on.

DP6 New Features

In the usability category:

• Updated UI with vertical track resizing (about time, jeez!) and better zooming and resizing
• Window tabs, which are a pretty cool way of switching between windows and tabbing views a la Firefox, Safari, et al (I’m surprised we haven’t seen more tabs in music software, given their popularity in browsing)
• Inspector palettes
• Build comps by selecting from different takes, which would be exciting if we hadn’t just seen similar features elsewhere

New Effects

As welcome as these features will be, most of the buzz I’ve heard from DP users centers around the new effects plug-ins. The MasterWorks Leveler models the “Teletronix LA-2A optical leveling amplifier.” Translated into plain English, it’s an automatic gain adjustment that can have some of the dynamic-smoothing qualities of compression without their soul-sucking quality – it’s an arguably better way of adjusting dynamics. I know at least one very prominent Ableton Live and Logic lover who wants DP6 just to run this plug-in. See the full description on MOTU’s site.

The ProVerb convolution reverb joins convolution reverbs in various other DAWs, with a few twists. It claims to be more CPU-efficient, which is generally not something you associate with convolution. There’s drag-and-drop convolution support, which allows you to drag audio right into the reverb for convolution use. It’s not the first reverb to support using your own audio files, but drag-and-drop is very hot. And MOTU adds automatic ducking features, called Dynamic Mix. And there are surround features, including the ability to use the convolution reverb to upsample to surround.

Combined, these features should allow you to get cleaner, higher-fidelity mixes th…

Um, excuse me. I need a moment. I feel my Jekyl-like alterego coming on here. Let me put on my mad scientist outfit.

[evil murmuring cackle, growing into loud evil laugh] So, MOTU thinks we’ll use these sound features for good, do they? Drag and drop convolution, to destroy my sounds! Let the world cower in the shadow of the new–

Ahem. Okay, moving on. Other features.

Still-Improved Film Scoring Support

While Apple customers complain that there aren’t more extensive integration features between Final Cut and Logic, MOTU has gone and created their own, with a dynamic link system for translating edits in Final Cut to scores assembled in DP. DP already has a surprisingly-strong corner on the film scoring niche, and this is yet another reason. You can even output visual cues over FireWire. Logic doesn’t come anywhere close to DP’s capabilities here. There’s just no competition. For composers doing actual scores, DP will remain king. It’s not a very big niche, but it’s DP’s domain, period.

There’s also improved Pro Tools front-end support, which I expect may be important to this market, as well.

Plug-In Features

You might think that Apple would lead the industry with AU support in Logic given that it’s all in the same building in Cupertino, but don’t count out MOTU – after a rough start in the early Mac OS X days, they’ve been really close to the Audio Unit spec and development tools. In this version:

• AU side-chaining support (‘bout time)
• Sample-accurate timing
• Cocoa graphics support (I’m not actually sure which plug-ins are using Cocoa – anyone know?)
• Ramp automation
• Prioritized MIDI for support for plug-ins like Access Virus TI

Not terribly exciting, but good to have. The one feature I think people will find exciting is the new, integrated plug-in manager. Boy, would I like this in some other hosts.

There’s also improved soft synth hosting for more efficient CPU use. One trick here is really interesting: DP now pre-renders instrument tracks so that already-recorded soft synths are rendered in advance instead of playing live. Update: See comments; readers are divided about just how useful this will be, and there are still some complaints about the way DP routes instrument tracks. I think we’ll have to see it in practice.

The combination of the pre-rendering with some of the other features here means that DP may be your best choice on older hardware, not to mention a very strong choice for people who want to load up on lots of plug-ins and experiment with sound design.

Bottom Line (Preview)

DP may be a niche player at this point, but boy, does it rock out in its niche. For film scoring, it remains dominant. And I think that the combination of a better UI, CPU-efficient features, a plug-in manager, and the reverb and dynamics additions here could actually increase its appeal to people who want a host for doing creative sound design and scoring, too – as well as continuing to make it a favorite for backing tracks in live performance. I’m still personally happier in some other hosts for various reasons when it comes to creating stuff, but you have to give some props to the things DP does differently. And it’s a relief that DAW competition continues to remain heated-up, even in 2008. If you wonder why Logic hasn’t become the one and only DAW on Mac, look closely at some of the details here. Composers and producers are very picky about the finer points, and as long as that remains true, we’ll have more than one DAW.

7.4.2 Announcement – download is right there [Digidesign]

That’s the good news. The bad news is, your plug-ins may not yet be along for the ride. Digidesign reports some current instruments and plug-ins may be “incompatible.” Based on other reports, I assume this means it’ll run, but may either cause instability or sub-par audio performance.

Digi is maintaining a plug-in compatibility page for Leopard.

Here’s the other bad news news: for the most part, that’s just plug-ins that Digidesign ships directly. Some of them at least have updates, but some of Digi’s flagship instruments (Hybrid, Strike, Structure, Velvet, and others) are awaiting updates as of press time. Your third-party plug-ins require a whole separate set of compatibility checks.

At least what we’re generally hearing from readers is that the situation is getting better, not worse. I’m still far from being able to recommend Leopard, however, especially given the fact that Tiger remains such an adequate OS. Update: Digidesign tells us that they’ll be monitoring other third-party plug-ins on that page, as well.

FireWire Fixes (Non-Digidesign)

Via PowerPage, some users of Leopard are having FireWire connection dropouts. At least for this issue, though, there are some suggested fixes. The symptoms, as reported at MacFixIt:

After the installation of software updates, the FireWire ports on various Mac models may cease to properly function, not recognizing devices or exhibiting other issues. For some users, this has occurred with printer driver updates and for others it has occurred with the latest QuickTime update. One MacFixIt reader reinstalled Leopard and the problem still occurred.

FireWire connection dropouts: more fixes [MacFixIt]

That’s a pretty nasty issue, but it sounds different than the intermittent audio issues users here were reporting, so I don’t know how widespread it is or whether it’s related to problems CDM readers have had.

I’ve actually seen less documentation of the audio issues, which means, brave CDM readers – it’s up to you. You’re the ones pushing your Mac’s audio. So if you are still having issues, even with current drivers and 10.5.3, be sure to let us know exactly what your hardware and software configuration is.

Apple’s airtight secrecy has allowed it to do some wonderful things. But what happens when it’s difficult to tell the path of future operating systems? That’s the situation I’m trying to tackle with Mac OS X Leopard and now the upcoming Mac OS X “Snow Leopard.” The good news is, Apple says they’re focused on improving the "quality" of the OS. The bad news is, it’s not clear what the plan is for the existing 10.5 OS — or what it will take for OS changes to sync up with what we need as musicians and audio producers.

Current Leopard Changes: Still Some Bumps for Audio

First, let’s talk about the existing Mac OS X Leopard release. Leopard audio performance does seem to be gradually improving. (See our previous reports.) But we’re still hearing reports of regular issues, particularly now with FireWire devices (10.5.3 addressed at least some USB problems). These may indeed be affecting a minority of users, and many of you have no problem at all. But that doesn’t change the reality that they’re problems introduced by upgrading to 10.5 from 10.4. Whether Apple, the device vendor, or some combination has to fix the problem, it’s obviously something you’ll want fixed. And in a supreme irony, I can actually set up a more predictable Vista system for music right now than Leopard.

I was recently forwarded a message from a major pro audio developer. The message encouraged their development partners to test Leopard extensively. I can’t divulge the contents of that email, but I can point to two changes in 10.5 that could be related to at least some of the audio performance issues people are experiencing. (This stuff is complex, so please feel free to correct me here, particularly if you know something about, say, kernel programming.)

The significant changes are:

• Multi-core thread scheduling: Leopard changes the way the OS handles thread scheduling on multiple-core systems. Thread persistence helps keep threads “glued” to specific cores, which should improve performance. The issue is, anything that changes the way threads are handled in the kernel can have an impact on digital audio. That isn’t to say the fault is always Apple’s if you are having trouble; these kind of changes can reveal issues in other code. But without assuming that this is related to all the glitches people are having with Leopard – since symptoms like clicks, pops, and dropouts can have a host of causes – it is possible that some of the bumps in Leopard are related to this change. (See Apple’s multicore feature page for Leopard.)
• Memory changes: I’ve had less luck tracking this down, but at least one difference is that Leopard adds memory randomization, a security measure intended to prevent exploits by locating system libraries to random locations. Memory randomization is present by default on Windows Vista, but on Leopard it seems as though it may extend to system libraries and driver loading, whereas on Vista it’s something you a programmer has to manually flag to use. I’m not convinced this is actually impacting audio on Leopard, but it does demonstrate that security concerns in operating systems in general can cause significant changes, something we have to watch as audio users.

It’s not clear what the exact impact on audio is; if anyone knows and would like to share your own experience, please do.

The thread scheduling issue appears to be more significant to music and audio. Because audio tasks happen in real time, thread scheduling is vitally important. Of course, the long-term payoff could be better multi-core performance, which is something audio fans are likely to like. The issue is the intermediate time when you’re ironing out bugs. And that brings us to the mysterious Snow Leopard.

Snow Leopard: SP1?

Fairly or not, some Mac fans are already grumpily referring to Snow Leopard as  Leopard “Service Pack 1.” (If you’re a Windows user, let me explain: the highest insult to a Mac fan is basically to compare something to Windows. Don’t ever call a Mac fan’s mother “Millenium Edition” unless you’re itching for a fight.)

Making all of this worse was this statement from the press release:

“Rather than focusing primarily on new features, Snow Leopard will enhance the performance of OS X, set a new standard for quality and lay the foundation for future OS X innovation.”

Now, personally, I reacted as many people do – stopping adding new features and focusing on improving what’s there sounds great! It raises just two problems: first, if Snow Leopard is “focusing on quality,” what was Leopard focused on? Second, Apple calls this the “next major version” of Leopard, which usually means they’re charging for it. Microsoft, by contrast, doesn’t charge for Service Pack releases even when (as with XP’s SP1 and SP2) they do introduce new features.

I’m not actually so concerned about either of those questions, though. I think all three operating systems — Linux and Windows included — could stand to spend a little time focusing entirely on performance and reliability rather than adding eye candy and gimmicks. I’m even happy to pay for it — maybe even more so than other improvements. The issue to me is planning and wondering what happens with Leopard in the meantime.

That’s made more puzzling by the "new features" in Snow Leopard:

• Multicore improvements
• 64-bit for support up to 16TB of RAM
• QuickTime X, a new version of QuickTime
• OpenCL, a new library for running CPU processes on the GPU (GPGPU)
• Microsoft Exchange support

See: Mac OS X Snow Leopard (Client OS page)

Are you thinking what I’m thinking? If in fact Snow Leopard really is just a "quality" release, why not skip Leopard and go straight to Snow Leopard? (This seems even more tempting than the Vista/Windows 7 split, especially as Vista 7 likely is a feature release and because Microsoft usually rolls out fixes directly in addition to putting them in bigger OS updates.)

OpenCL, QuickTime X, and the Exchange support are just libraries, so we can safely ignore them. It does raise the question of why Apple would roll these into an OS release, although that makes me suspect this will be a free, not a paid, upgrade, or that perhaps QuickTime X will be back-ported to Leopard and available on Windows. (Well, one would hope.)

But the multicore mention is a bit odd, because that was supposed to be what happened with Leopard. This could imply that Leopard’s multicore improvements weren’t fully baked before they went out the door. Of course, it could also mean that Leopard will continue to build on what’s Leopard.

Then again, that’s the fundamental problem: we don’t know. Apple keeps all of their OS development under NDA. Developers who don’t make the trip to WWDC may miss out on information entirely. And Apple is unlikely to communicate to the rest of us until the day Snow Leopard ships, whenever that is (since the pricing and schedule haven’t been announced). In fact, part of the reason I can talk about this at all is that I’m not at WWDC. Otherwise, I might have Apple legal knocking on my door.

Maybe I don’t "need to know" what’s going on. But my plea to Apple, if they happen to be listening, would be to coordinate closely when multicore improvements like thread scheduling can impact audio. I get the sense that this really wasn’t in sync on Leopard.

And of course, this whole issue isn’t unique to the Mac. Windows developers are in a similar boat, wondering what the plan is for Vista as Microsoft shifts its efforts to its own release, Windows 7. Like Snow Leopard, Windows 7’s features are vague, the plan is for "quality" and performance over new functionality and big changes, and it’s not clear how much energy is going into the current versus the future OS — especially as Microsoft tries to make its release schedule more prompt. Bizarrely, Cupertino and Redmond have each adopted parallel strategies.

A Better Way?

I’ll point it out again: as much credit as Apple has rightfully gotten for OS quality, their approach does have some significant downsides.

• New computers ship out with the latest and greatest, whether or not it’s stable for the particular task the user has in mind.
• Operating systems ship out blending various updates, from features for iPhone users to hardware fixes to critical security patches to iTunes updates to new features. There’s no granular control over what gets installed, which is sometimes necessary to maintain a stable system.
• Apple’s "whole widget" philosophy sometimes causes them to compete with themselves. QuickTime updates get tied to improvements in iTunes, for instance — even if some of us use QuickTime for critical professional work and don’t touch iTunes.
• Apple’s "everything’s a secret" approach makes it really hard to plan or fully understand what’s going on.

I do think Apple deserves their reputation for the work they do in software. So I’d really like to see some improvement. I’d like an OS upgrade mechanism that gives us more control. I think Apple could better document changes, and shift some of the knowledge that now is covered under restrictive NDAs to a more public sphere so that it’s easier for people to document and fix problems — many of which involve third parties but reflect poorly on the quality of the Mac platform.

And you do still have a choice in OS. Yes, even including Linux.

Update: Information on Pro Tools Compatibility for Mac OS X 10.5.3

The reason you might still want to wait on Leopard upgrading, in case this hasn’t already made you cautious: not all RTAS plug-ins are expected to be “Leopard-ready.” (TDM plug-ins run on Digi’s DSP hardware and are apparently unaffected once the host works.) We’re told developers are being advised to test rigorously because of changes to Mac OS X. This may not be limited to Digidesign. Based on reports from readers, while users are on the whole happier with 10.5.3 than 10.5.2, there are still some kinks to work out — including users of products other than just those from Digidesign and M-Audio. Best advice: stick with Tiger 10.4.x if you can for the most stable alternative.

Pro Tools Plug-in Compatibility with Leopard

Just as being patient now is advisable, though, it’s equally good advice to reserve judgment on Leopard until the OS matures. Changes made to 10.5 promise better performance on multiple-core systems, for instance — so while the short-term side effect may be glitchy audio until bugs are ironed out, once software is mature, you may squeeze out more performance. The problem is, we can’t know either way until other issues are resolved first. That means patience pays off doubly: sticking with the most stable option if you can is a good way to avoid trouble, while waiting to see how things go means you could reap some rewards upgrading once the software matures. (On the other hand, some readers have no problem, so if you have more than one machine or a new machine that requires Leopard, I’d say go for 10.5.3)

I’ll say those two words I tend to say all the time: stay tuned.

Thanks to Ray Tovey and others for the tips!

“Addresses an issue with stuttering video and audio playback in certain USB devices.”

Also interesting, given that some issues may have been related to wireless issues: “Improves 802.1X behavior and reliability.”

About the Mac OS X 10.5.3 Update [Knowledge Base HT1141 at Apple Support]

Thanks to John for the tip. (I hear shouts of joy from various people as that Software Update dialog pops up…)

This would appear to address at least some of the audio performance complaints with 10.5.2. Those of you who have been having issues who were unable to downgrade, let us know as you test if it seems to make your problems go away.

Because operating systems are complex, however, it was unclear whether this was the only issue with 10.5.x and audio, so we’ll also be watching for more comprehensive testing feedback from CDM readers and music and audio product makers. (Specifically, we had gotten reports of issues with FireWire devices as well as USB, meaning this may not be the complete fix we had hoped for. But Apple software update release notes are notorious for being vague and incomplete; as Vince notes in comments, the version number on the FireWire driver has in fact changed and there may be other changes not explicitly listed in the notes.)

Digidesign has joined its M-Audio unit in responding to our concerns about lagging Mac and Windows drivers, but lest you think this is just a Digi/M-Audio problem, I want to draw attention to this passage by Dave Lebolt, general manager at Digidesign, on the Digidesign user forums:

Many of the problems that Apple addressed in these dot releases [10.5.1, 10.5.2] were critical to improve OS X Leopard operations (you can read about some of them on the support section of Apple’s website). These improvements and fixes were very valuable to a broad base of Mac users. Unfortunately, the currently shipping OS X Leopard release, 10.5.2, contains some changes that actually caused problems with Pro Tools (and some other apps as well). In our case, the problems included audio interfaces not being recognized by the computer, track counts dropping to near zero, and errors coming up during normal operation. Some of you who may have experimented with Pro Tools and OS X Leopard 10.5.2 may have encountered some of these problems.

[emphasis mine]

I certainly can’t recommend Leopard in its current state. If it’s working for you, fantastic. But if you can otherwise avoid it for the time being, I think sticking with your current OS could be a smart move, especially since there’s no real music-specific reason to upgrade. Hopefully a fix is coming soon; maybe 10.5.3 will appear tomorrow and we’ll be rocking out without bugs for Memorial Day Weekend. We’ll see.

This does illustrate the problem — to some, the changes in 10.5.2 were a fix. The issue is, because of the complex, interconnected nature of an operating system, a "fix" can simultaneously be a "break." Being careful with updates is, therefore, par for the course.

We’ve already seen official statements from Serato and Native Instruments suggesting users avoid the update, citing similar symptoms to those above. We’ve heard from users using products from other vendors finding other problems. It’s not just music users complaining — you can read reports from the Mac faithful complaining about the update.

Unfortunately, new Apple hardware comes pre-loaded with the update, although your best bet is to just try it and hope for the best — we’ve heard from readers that new Penryn-based hardware seems immune to audio performance issues for some reason.

Incidentally, I’ve now heard several people suggest that this is some kind of conspiracy theory in which Apple breaks competitive music products. (Wow, that sounds like a great plan, and completely plausible!)

I wouldn’t even bring it up, except to say, let’s all agree now that that’s ridiculous. The changes in Mac OS came from other areas of the OS, not from the audio team. Music developers report that they’re working directly with Apple engineering to fix the problem. Apple doesn’t benefit from stuff being broken, period. And Apple doesn’t even make audio hardware. I think people may just be in denial about how hard it is to develop a desktop OS, and how easy it is for problems to occur, particularly with audio subsystems. So, uh, relax, okay?

Unfortunately, the reality of OS development is that it’s a delicate thing, and fixing one thing can indeed break something else. So, at this point, we’re waiting on 10.5.3 or some other update to resolve the problem.

Now, could there be some kind of engineering and testing effort that makes these problems happen less often on operating systems in general? I’d like to think so, particularly with the rising importance of audio in general computing and the growing significance of so-called "pro audio" (read: sound that works) to Apple’s business, not to mention Apple’s strong track record in the past. I imagine that improving the situation will require effort from both the OS and the developer side. It’s an issue we’ll be watching in the coming months.

Previously:

Mac OS X 10.5.2: Music and Audio Problems on Apple Laptops?