What’s in 8.0.1

If you’re an existing Pro Tools 8 owner, you’ll want 8.0.1:

• Improved interface performance (“snappiness”!)
• Improved selection drawing in audio
• Workflow improvements, fixes

Those of you who grabbed the update in the last week or two, I’ll be curious to hear what you’ve found in some of those subtler improvements. Avid, to their credit, does do a lot of work on these point releases, not only in bugfixes but in other improvements, as well.

Software update for 8.0.1 (LE + HD + M-Powered)

End of the Line

Pro Tools 8.0.1 is the end of the road for quite a range of "legacy" hardware. 8.0.1 (in one or several of its LE, HD, and M-Powered flavors) will be the last version to support:

• Original Mbox
• Expansion|HD Chassis
• Macintosh PowerPC Computers
• Pro Tools MIX-era Peripherals

See last week’s End of Software Support announcement. Now, I suppose you can look at this as glass-half-empty or glass-half-full; it means if you have a studio with that gear in it and a PowerPC-based Mac at its center, you have a stable, modern, brisk version of Pro Tools that could last you a while.

PowerPC support is generally waning; Apple also dumped PowerPC for its own Logic. But there’s still a surprising amount of life in the processor. MOTU’s Digital Performer 7, released this week (news story on that coming) will actually run on a 1 GHz G4; see their System Requirements. I wouldn’t recommend that system, necessarily, but if you’ve got a fast Mac tower with a PowerPC, it could still make a fine studio machine. And DP7 is also compatible with Pro Tools HD, including Pro Tools 8. Ableton Live, also popular around these parts, also still runs on a PowerPC.

New OSes? Not Yet.

Absent from the 8.0.1 update is support for either Snow Leopard (Leopard only is supported) on the Mac side or Windows 7. Now, in fairness, Windows 7 isn’t even shipping yet, though in stark contrast to Vista’s RTM version, developers I’ve talked to have found their software runs without modification – and can run better without intervention than under the previous Vista release, which is something that almost never happens.

Ordinarily this wouldn’t be a problem, but it does mean that studios with “legacy” gear could wind up with a version that doesn’t support Mac OS X 10.6 or Windows 7, if 8.0.1 is in fact the last version of that gear. It obviously won’t matter for the PowerPC Macs, since they run neither Windows nor Snow Leopard, but I can imagine some folks with the HD chassis or MIX peripherals who won’t be thrilled. It’s a small handful of people, but – well, before you complain in comments, yep, I’ve figured it out, too.

Snow Leopard looks like a promising upgrade for Mac users. Most importantly for music users, 10.6 is the first operating system with what looks like a mature foundation for 64-bit support in the future. Previous versions of the Mac operating system had begun this transition, but Snow Leopard is the first to have a proper 64-bit kernel mode. Also, some Mac developers are likely to be able to take advantage of new multithreading capabilities provided by OS APIs. (Others, particularly those targeting more than one OS, will continue to provide multithreading and multi-core support via their own mechanisms.)

However, there are very few scenarios that are likely to benefit from upgrading today. Nearly all software developers (Propellerhead, Avid, Ableton, Plogue, and Native Instruments) advise waiting as support stabilizes. A number of hardware issues (Digidesign, M-Audio, Tascam, PreSonus) are known to exist, and many more likely simply haven’t responded this week to our call for information. Other hardware and software issues are likely to be uncovered now that the final OS build is available for widespread testing by end users.

Also, while Apple’s own software (Finder, Mail, and other apps) appear to get performance improvements, and startup/shutdown is better, the advantages of new OS services aren’t likely to be realized immediately. In fact, even measuring what the difference will be may take additional time.

Compatibility issues should be resolved fairly quickly – which is even more reason to wait. PACE Anti-Piracy, for instance, works now, as does software and hardware for MOTU. Other updates should be available in a few weeks with enhanced compatibility, making that a better time to upgrade.

If you’re looking to reclaim hard drive space with a smaller OS, I recommend Monolingual. By removing PowerPC-native code from Intel systems that don’t need it (or visa versa), it offers the same significant disk space improvement available in Snow Leopard. (Clarification: It should achieve similar net results, though Snow Leopard nips and tucks in a different way – cutting PowerPC but adding 64-bit, while reducing elsewhere – see David Pogue in The New York Times. But that’s academic – if you need extra gigs, you can get it both ways, and I expect we’ll eventually see Monolingual on Snow Leopard, too.) It also removes extra languages you don’t need to save space – something even Snow Leopard doesn’t do. I was able to nearly halve the size of my OS install using the tool, the same gain claimed by Snow Leopard. And it’s free.

http://monolingual.sourceforge.net/

This advice doesn’t mean that Snow Leopard is a “bad” operating system – just that the OS is currently ahead of the other pieces you need to make it useful for music. Developers are largely talking about new updates in “weeks,” not months.

Another way to look at it: Snow Leopard might run just fine for you today. But it’s almost certain that it will run better – and fully supported – in a few weeks. Stay tuned.

That said, just as 10.6 is coming out, 10.5 is maturing. Ableton notes that the latest version of 10.5 is recommended for maximum graphics performance. Native Instruments now considers 10.5 its officially supported operating system. As you’ll recall, early builds of 10.5 offered a very rough road for audio, as it contained more significant under-the-hood changes than 10.6 does today. Audio and music applications simply acheive their best results on fully-mature operating systems, and they tend to require more extensive testing and tweaks by both the operating system vendor and third parties.

If you do like being on the bleeding edge, more power to you. If you encounter issues, let us know about them, and that may help get them resolved more quickly.

So… relax. And enjoy your weekend.

While you wait for full compatibility, remember you can watch updates at:

http://createdigitalmusic.com/snowleopard

MOTU has a comprehensive update page, and I’ve added the news to the http://createdigitalmusic.com/snowleopard round-up page.

That said, while MOTU has the greatest level of out-of-the-gate support I’ve seen from any vendor for 10.6, even they have run into a showstopper issue. Their Ethno Instrument isn’t yet compatible; an update is expected. Sure, that’s just one instrument. But the lesson here? If you don’t mind the occasional wrinkle, you can live on the bleeding edge. But if you want to keep your software up and running, your best bet is to be patient and wait to upgrade. That’s not to discourage you from testing the latest-and-greatest, it just means you need to have the expectations to match.

The news remains, though: MOTU does have updated drivers for those of you with MOTU hardware or software who want to get a head start on setting up Snow Leopard.

That does not seem to be the case with other hardware vendors (Pro Tools, M-Audio, Tascam, and PreSonus all suggest waiting), and even some of the drivers that will initially become available should be considered “beta.” That is, they may even be designed to work with 10.6, but could use additional testing. I think that could probably generally be said of this update for musicians – just as with any significant operating system update on any platform.

Okay, that’s technically not a snow leopard, but I came pretty close, right? Photo (CC) Mark Kenny.

For the latest on Mac OS X Snow Leopard (10.6), be sure to check out our full round-up. It’ll be regularly updated through the coming days.

We have updates from Propellerhead and Ableton. Basically, the message is what we’re hearing across the board – developers have been testing their software, but you should be cautious about updating and ensure all the hardware, software, and plug-ins you want to use work. More details on the state of development from these favorites to follow… notably, including an expected update to Live 8 that will bring full, official support to 10.6.

Updated: More news coming in and added to the round-up page. Antares reports their software works — good news. But the big news is that many Tascam hardware products will need driver updates. That is suggestive of changes to the OS that could impact other audio interfaces from other vendors. I’m going to keep saying this – upgrade on launch day at your own risk. Writing and testing audio drivers is tremendously time-intensive, so if you want everything to work, you’ll need to verify compatibility before you upgrade. Snow Leopard’s improvements will only be cool if your audio box works, too.

Ableton’s Dom Wilms, Manager – Technical Support, writes CDM:

10.6 is not officially supported yet, as we’re currently testing it with Live 8 and based on the results we will release a free bugfix update during the next weeks that will officially support 10.6.

It’s likely that Live 7 will also be just fine with 10.6 – but we don’t want to promise this right now before the tests are all finished and us being sure that we can achieve 100% compatibility.

And yes, we also do not recommend upgrading yet if stability is crucial for the used system. In this case customers should wait until all third party software and hardware products are confirmed to work with the new cat…

We will come up with a little FAQ regarding those questions in our forum today or tomorrow.

Note that reader Jae sent in a thread from the Ableton forums with some testers, but I wouldn’t take it as scientific evidence. It begins with a user finds a reduction in CPU usage that’s actually too large – that is, it seems there’s some significant variable that’s not controlled.

None other than CEO Ernst Nathorst-Böös writes in with the official statement from Propellerhead. So far, so good – just, again, approach this new OS with caution.

Mac OS X 10.6 (Snow Leopard) Compatibility Statement

Apple have released a new operating system, Mac OS X 10.6 also known as Snow Leopard. Our products have been tested on this new OS X version and we are happy to report that all our applications are fully functional.

Please note the following non-critical issues:

ReCycle – You need to activate Rosetta to make ReCycle work. This is similar to what happened if you ran ReCycle on a Intel-based Mac under Mac OS X 10.5.

Reason and Record – The text in the device patch selector has a display bug. The characters O, o and 8 have filled rather than hollow circles.

Record – The Record installer reports an (actually non-existing) problem after installation, but Record runs fine. You can safely use Record without any problems.

Hardware Note

Your music system does not consist of software alone. Please be aware that you may need to update the installation of your audio hardware, keyboard controller or other controller when upgrading to Mac OS X 10.6. We recommend that you consult the hardware manufacturer for more information about compatibility, before you upgrade your operating system.

Disclaimer

While Propellerhead Software has gone to great lengths to verify the information above, please note that it is based on early versions of Mac OS X 10.6 and that the testing performed is by definition limited. This information does not constitute any warranty, express or implied.

By the way, I want to thank developers who do post frank information on the forums and who have helped us out with this series – at a time when they don’t have all their testing data yet.

The changes may be subtle, and you may not notice a thing. But if you upgrade your OS – any OS – the day it comes out for the ever-delicate work of live music and visuals, you should think of yourself as a tester. There’s a good chance you’re going to find some issue somewhere. Guess what: griping about it gets you nowhere. If you find a problem, fill out a detailed bug report with the vendor. And be patient. Anyone who’s tried developing software or drivers knows what I mean: stuff breaks. The advantage now is, we can arm ourselves with information through the power of the Web.

I’ve created a page for tracking Snow Leopard compatibility, changes, and other information, with a visual equivalent to follow after launch. (Right now, most of the visual information we want to talk about is still under NDA.)

Bookmark it at:
http://createdigitalmusic.com/snowleopard/

What kind of updates? Well, this just in: Iced Audio writes us to let us know they’ve successfully tested their awesome AudioFinder under 10.6.

This is information that’s constantly changing, and it’s an unscientific compilation – just think of it as a place to start your research and testing process if you do want to hop onboard 10.6 early.

As we get closer to Windows 7’s launch, we’ll give Windows a page, too, and I hope to have some centralized info for Linux, too.

Word from developers confirms what I had suspected: developers were as surprised as we were to learn Apple was shipping a new operating system on August 30.

If you have to ask yourself whether you want to upgrade, then the simple answer is – don’t, not yet. And via Christopher Wimbrow on Twitter, here’s the first tool that we can confirm will outright break if you jump too soon – PreSonus hardware. From their forum, earlier today, PreSonus’ Nick RICK Naqvi tells a user (unofficially):

Right now, we are planning to have support for Snow Leopard by the end of October. We had originally heard they were going to release it in September, so our plan was to test it thoroughly and then release a new driver about 30 days later. They moved up the date to August 28 so it looks like we will be a little more than a week later than we expected.

Please note, if you update your OS, your PreSonus hardware will not work.

If you have to install it to play with, I’d recommend doing a partition. But leave Leopard on it so that you can continue to record.

Ouch. I’ll let you know if this gets fixed sooner. And remember, this is an operating system that is being tested under a Non-Disclosure Agreement; more incompatibilities are likely to appear next week.

This illustrates a problem, too. Shipping an application early is great news. Shipping an operating system early – with countless hardware and software vendors pulling time from other work (like new features) to keep their stuff working – not so great news.

Fortunately, you have power over your computer. Ignore that Apple email that appeared on Monday saying Snow Leopard is “In store or at your door Friday,” and consider it a bleeding-edge operating system. Assume that for most users, the current build of 10.5 represents the best compromise of Mac stability, compatibility, and features – at least for the time being.

UPDATE – PreSonus WILL have beta drivers. And like the vast majority of vendors, real stable versions are expected in a few weeks.

Earlier in the week, I was told that we weren’t going to have Snow Leopard driver until October, but our engineers worked overtime the last week or so to release a beta driver that is fully functional. We have tested it internally and it is working well and allows for daisychaining of interfaces and full feature functionality. This driver will work with all of our Firestudio Family Interfaces including:

Firestudio 2626
Firestudio Project
Firestudio Lightpipe
Firestudio Tube
Firestudio Mobile
StudioLive1642

Our other interfaces are class compliant and are going to be immediately supported on Snow Leopard:

Firebox
Inspire1394
FP10 / Firepod
AudioboxUSB

Lastly, our new recording software, StudioOne is also ready for Snow Leopard. Here’s a link to the StudioOne page: http://www.presonus.com/products/SoftwareDetail.aspx?SoftwareId=11

If you are an early adopter, let us know your experiences.

Updated: See http://createdigitalmusic.com/snowleopard for a running report.

Apple’s “Snow Leopard” 10.6 ships Friday, which means it’s time to start compiling information about the new OS flavor. Just don’t upgrade too fast, as always.

Want to push an operating system to the breaking point? Ask a musician. Between the demands of real-time performance and the complex ecosystem of mix-and-match hardware, software, and plug-ins, odds are your local audio geek will break an OS faster than anyone else. Not every operating system upgrade is going to have a big impact on music software, but keep in mind that even subtle changes can cause issues that may interfere with your work.

Of course, all of this means music users should treat any OS update with caution. :

• If you’ve got a critical, primary production machine, your best bet is often simply to wait. Confirm that software works before you upgrade rather than after.
• If you’ve got some time to invest in an upgrade or have more than one machine, be sure to do a full backup and system image so you can revert to the previous, known working OS.
• Best solution: Boot off an external hard drive. Don’t commit to installing internally until you’re sure everything is working. Once you are, go enjoy. (as noted in comments, and yes, I should have said this initially… still, the latest 10.5 build is still the preferred OS for now.)

So, sit back. Enjoy life. Go for a walk on a beach. Recline in your favorite chair with your MacBook running Mac OS X 10.5 Leopard. Isn’t it great? Need to waste time? Plants vs. Zombies is out for Mac.

What? Still want to upgrade?

Fair enough. We’ll be tracking changes to Snow Leopard and which of them may impact audio.

The short version: Snow Leopard introduces only small changes, but if a developer hasn’t been on top of those changes, you could see issues. And as for the 64-bit mode that’s attracting most of the attention, the short answer is, you can’t use it for music yet.

Native Instruments and Plogue have each responded to CDM with information on their software.

Executive Summary

• NI and Plogue have tested their software as functioning on 10.6
• Neither NI nor Plogue recommends you upgrade your OS yet – Plogue uses stronger language to discourage you
• 64-bit support, expanded in Mac OS 10.6, is not yet relevant to music use because nothing (not even from Apple) supports it yet, but don’t worry – you can get more RAM through other methods
• Audio MIDI Setup gets a tune-up, and built-in audio support appears to be improved

Native Instruments

If you’re a Mac user who uses NI products on any version of the operating system, you should stay tuned to this URL:

http://www.native-instruments.com/en/support/compatibility/mac-os-x-compatibility/

NI tells CDM they’ve just updated it today with Snow Leopard information:

Native Instruments has conducted initial compatibility tests with Mac OS X 10.6, which have shown all current NI products to work without any specific issues under standard installations of this operating system.

However, users involved in professional audio production or live performance should be cautious about upgrading to Mac OS X 10.6 until compatibility with third-party audio software and hardware has been widely confirmed by the relevant manufacturers.

Native Instruments is currently conducting further systematic compatibility and performance tests with Snow Leopard, and will provide additional information on this page as it becomes available.

The second paragraph sounds like what I just wrote, huh?

Plogue

Plogue, an independent developer of a variety of software ranging from the awesome modular environment Bidule to sampling engines for Garritan’s orchestra and piano products and an upcoming library of vintage chip sounds have been doing their own work. Privately, I talked with them about some of the work they had to do after Apple rewrote underlying operating system plumbing with Objective-C (from C and Carbon). Here’s their official statement to CDM on Snow Leopard and, in the parallel Windows dimension, Windows 7:

10.6 and W7 each caused only minor modifications to our code base, however these mods are necessary for proper functioning of our products on those platforms. Most of our transition efforts as a company will be of a user support nature.

Any musician foolish enough to jump on new OSes without a hint of caution, inevitably makes me wish for a new kind of Darwin Award prize.

(Emphasis mine. Consider yourself warned.)

Ableton (Unofficial) and a Plug-in Warning

From the Ableton forums, via comments:

It’s currently being tested internally over here, so the current version is not officially compatible yet – on the other hand this does not mean that it doesn’t run.

We will release an update after the tests during the next weeks that will be officially compatible, but we don’t recommend upgrading yet if stability is your main concern.

It’s likely that a few new third party plugin problems will show up due to the changes under the hood in 10.6 and experiences show that the latest 10.5 versions now are the way to go after the gfx performance problems with earlier 10.5 and 10.4 versions.

So, in other words, now is a great time to upgrade to 10.5!

More in the thread here:

Ableton Forums

Now, note, mostly what this extensive discussion reveals is that Snow Leopard is poorly understood, partly thanks to a very successful hype campaign on Apple’s part. (Ahem.)

There are not magical performance and speed improvements found by installing Snow Leopard – or, most likely, any OS. (Would that such things were true.) The presence of a set of multithreading tools, for instance, is specific only to developers for whom that set of tools is useful. Audio software already has finely-tuned multithreading implementations specific to real-time applications, and in the case of something like Ableton Live, it really needs to work across platforms.

If you install a new OS with the expectation that it’ll be “faster,” you’ll almost certainly be disappointed. If you install a new OS hoping you’ll “break things,” then you probably won’t be disappointed. I don’t mean to suggest don’t ever upgrade or live in fear of all software, just that you should imagine that, like redoing the plumbing in your basement, long-term advantages will come, but with significant effort and time.

PreSonus Hardware

See a separate post: at Snow Leopard launch, PreSonus audio interfaces are likely to be entirely incompatible.

About 64-bit (Nothing to see here…)

NI notes that the 10.6 offers significant changes to 64-bit support, including a new 64-bit kernel mode – this being the rough equivalent of the “x64” 64-bit versions of Windows (and Linux) that have been available for some time.

Here’s the bottom line: 64-bit support on Mac OS isn’t yet relevant to audio users, period. It’s not supported by Apple’s own Logic Studio, or any other major host at this time. This is a situation we’ll be watching, as it is something developers appear to be investigating.

But before we get too far into that issue, you should consider why you’re asking about 64-bit in the first place. 64-bit computing offers two potential advantage. First, running processor computation natively at 64 bits offers a marginal improvement. Second – the issue most people care about for music – 64-bit memory addressing offers access to massive amounts of memory, beyond the approximate 4 GB barrier that applies to 32-bit applications.

More memory is a very good thing. But you probably don’t want to sacrifice compatibility just to get it. Fortunately, you don’t need the 64-bit OS to get beyond that 4 GB barrier. On the Mac, some workarounds have extended the practical life of 32-bit memory addressing for music applications – thus avoiding the need to get a 64-bit native version of every driver and every piece of software you want to use.

On Windows and Linux, you can indeed get a number of audio applications (like SONAR on Windows, for instance) that have excellent 64-bit support, and a number of the drivers have followed suit. Even, then, though, many users choose to stick with 32-bit versions in order to have superior compatibility.

Note that processing “64-bit audio” – that is, digital audio represented using 64-bit data – is a completely different issues. A 32-bit processor and 32-bit operating system and 32-bit software can all do 64-bit audio processing. Whether you really need 64 bits for audio production is a whole other can of worms I won’t open here.

Getting More Memory – Without Any 64-bit Snow Leopards

When I spoke to Apple earlier this month, they downplayed the 64-bit issue and pointed out that their own EXS24 sampler in Logic Studio can access additional installed memory just fine with 32-bit – that means if you have Logic 8 or later, Pro or Express, Tiger or Leopard or Snow Leopard, you can use additional RAM. Each EXS24 sampler instance has its own memory space, so you can use as much memory as you want.

Apple even has a support doc on the subject:

Logic Pro/Express 8: How the EXS24 sampler addresses RAM in Logic 8

Last month, we looked at the situation for Native Instruments’ Kontakt. Again, using some of the flexibility of the memory architecture unique to the Mac, they’ve managed to access bigger amounts of RAM even on 32-bit OS.

Kontakt, Battery: Enhanced, More Compatible, 64-bit Memory

Kontakt is able to get up to a whopping 32 GB thanks to something called the Kontakt Memory Server. Again, you can get still more than 32 GB using 64-bit Windows, but for most users, that’s overkill.

All of this is to say, 64-bit is not a reason to upgrade to Snow Leopard for audio work – at least, not yet. Some of the built-in applications (like the Finder and Safari) get performance boosts from 64-bit optimization on 10.6, but none of that is critical to audio and music – and it’s certainly not worth upgrading too soon only to find some compatibility wrinkle we haven’t yet found.

Updates to Audio MIDI Setup

A reader tips us off to some small changes to Apple’s centralized Core Audio settings panel, Audio MIDI Setup. Audio and MIDI are now separated into separate windows, and Audio gets some nice improvements.

Note the per-app settings and adjustments for sample rate, bit depth, and Format. As in previous recent versions of Mac OS, you can also aggregate multiple physical audio interfaces into one – one of a number of reasons we really love Core Audio as a sound system.

The reader also notes that the update seems to improve support for his built-in hardware:

It’s now possible to choose a higher sample rate and resolution for all inputs/outputs on the built-in sound card of my MacBook Pro early ‘08, which is pretty cool. Before there was clearly hearable, annoying digital fragments when playing back any sounds, especially on low volume – all magically gone, i don’t hear anymore noise.

Got More Information?

Help us continue our “More Than You Wanted to Know,” obsessive series of coverage on CDM and tip us off!

Corrections and clarifications are welcome, too – that’s why I enjoy the maleable nature of the Web.

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.