This week, while we poll readers to find out what platforms they really use and care about for music, we’re launching a new series to help you get the most out of whichever OS you choose.

We’ve been covering the complexities of Windows for a while, from the bumpy Vista transition to the smoother advent of Windows 7. I also wrote up a feature in Keyboard Magazine covering Windows 7 and Mac OS X Snow Leopard. Here, I’ve worked with Noel Borthwick, Chief Technical Officer of Cakewalk, and Kevin Jacoby of custom computer house Rain Computers, in order to get both the software and hardware developer perspective and the OEM side. They’ve offered some frank opinions in the past; Noel had some criticisms for Vista, and Jacoby and Rain kept XP the default for a while. But that means when they say Windows 7 can work for musicians, they mean it.

If you’re still on XP or Vista, or if you’re pondering going to a 64-bit version, we have some advice there. If you’re already on Windows 7, we’ve some tips on how to make the most of optimizing the OS.

When is the OS to blame? (aka, “Glitch” music when you don’t want it)

Before we get into talking about Windows itself, I think there’s a bigger issue to address.

Now that I’ve been testing Windows alongside a variety of operating systems, I can say this. I think the press and user base have sometimes blamed the Windows operating system itself when it isn’t directly at fault. A lot of the most annoying obstacles to music making on computers – glitches, audio stability issues, and an inability to run at lower latencies – depend on a complex chain of interoperating hardware. (That’s true even on the Mac platform; in fact, even given Apple’s relatively focused computer offerings, I think Apple deserves the same credit a PC vendor does when they have all their components working in concert. When we have seen issues on the Mac, drivers and chipsets are often to blame.) Chipsets and components, particularly on laptops, can cause problems. It’s simply easy to blame (or credit) the OS because it’s so fond of flashing its logo at you, and it’s the part of the computer with which you interact.

This also means the choice of Windows itself may not be as important as the choice of computer hardware. Custom shops like Rain Computers are unique in that they test their components for audio applications – that’s not an advertisement for them; it really does make a difference. Because part of what attracts readers to the PC is vendor choice, I’m working on ways of evaluating mainstream machines, too.

The bottom line is, because musical and visual applications are more demanding, there’s a greater need to remain educated and share information. Too much of that information in the larger tech press devolves into petty platform advocacy and bickering. We really need the information just to keep our machines running smoothly.

Windows 7, After Some Time in the Hands of Musicians

We’ve now been living with Windows 7 for some time, which means when you do choose to upgrade, you’ve got plenty of information behind you. When I first looked at Windows 7, it was clear the OS was better than Vista, but it wasn’t yet entirely clear how it compared to XP. And while Mac vs. Windows vs. Linux comparisons tend to be apples to oranges, you ought to at least be able to be pretty objective about comparing Windows releases to other Windows releases. Now, we do have a lot of empirical evidence, and both Rain and Cakewalk – the folks on the other end of the phone when people call to complain about problems – have pretty strong endorsements.

Kevin at Rain goes as far to say that Windows 7 exceeds XP:

Windows 7 is by far the best operating system we’ve seen for pro audio and video production. It’s got all the modern bells and whistles that were missing in XP, none of the craziness from Vista, and has managed to retain the benefit of an open architecture that lends itself to great application design. It’s given us the opportunity to squeeze every ounce of power from the apps and hardware we see most often like Pro Tools, Cubase, Adobe CS5, etc.

In terms of support, our tech support staff is over here celebrating. Windows 7 has remarkable improvements that help with stability. Pro audio/video isn’t the easiest thing in the world. It starts to get a bit touchy when there are too many features, apps, drivers, etc. But W7 seems to be more forgiving; it heals better than Vista or XP – doesn’t crash like them either. And when there is an issue, its got some tools, like Complete PC Backup, that help us get the user quickly back to a point where they’re making music and video again.

Noel Borthwick, on his off hours, is actually a musician. I’ve been following his experience with his own home computer setup, and he’s a happy camper.

I recently built a new DAW for my studio which runs SONAR 8.5 on an Intel Core I7 950 with Windows 7 Professional X64. (See http://www.noelborthwick.com/minidump/2009/12/new-daw/ for specs) I can categorically say that the SONAR/Core I7/Windows 7 combination is a match made in heaven for DAW users! I easily have way more bandwidth than I would ever need for the next several years on this rig. On my largest projects which would previously max out the CPU or drop out (an older dual CPU Windows 2003 based machine), I am now able to run at 128 sample buffers with a MOTU 828 MK2, at 24bit/96KHz with under 20% CPU utilization in SONAR!

Noel has also been listening to users, he says:

The response to Windows 7 and SONAR has been overwhelmingly positive. Here are a few threads talking about the great results that our users are having with SONAR and Windows 7.

http://forum.cakewalk.com/tm.aspx?m=1769661&mpage=1&key=?

http://forum.cakewalk.com/tm.aspx?&m=1774267&high=windows+7&mpage=1

http://forum.cakewalk.com/tm.aspx?m=1734916&high=windows+7

http://forum.cakewalk.com/tm.aspx?&m=1713663&high=windows+7&mpage=1

http://forum.cakewalk.com/tm.aspx?&m=1601783&high=windows+7&mpage=1

Rain also confirms that, as always with PCs in general, it’s the combination of hardware that can be an issue and is the focus of their optimizations. “Part of the challenge is getting around the consumer-centric features,” says Kevin. “For instance, HDMI and other high def audio features often interfere with pro audio drivers and interfaces. It’s a bit of a challenge at times but Microsoft and our other tech partners have been helpful.”

Should You Run 64-bit for Music Apps?

Not to be confused with 64-bit audio – a representation of the length of digital samples and their corresponding dynamic range – 64-bit computing is what enables access to greater amounts of memory, and provides a corresponding computational boost in performance on the same hardware. On Windows, unlike the Mac, you must choose when you install the OS whether you opt for the 32-bit or 64-bit version. (You can configure a multiple-boot operation, but each boot entry must be one or the other.)

If you’re configuring a new machine, or upgrading from XP and Vista, it may be an optimal time to try 64-bit, since you’ll be evaluating compatibility and updating drivers anyway. So, which should you choose?

Kevin offers a whole-hearted endorsement of 64-bit, but with some ideas on why 32-bit still has some place.

My biggest disappointment when W7 was released is that we couldn’t put the 64-bit version on every Rain computer that left the factory. With due respect to the pro audio industry, some software engineers are chronically behind the curve when it comes to releasing new versions and drivers. However, all that is changing now. These days, I’m in a much better mood since Pro Tools released a 64-bit compatible update and our customers can choose from a wider range of plug-ins and virtual instruments. Kudos to Cubase and SONAR for doing their homework early on that one.

On the other hand, the folks over on the video side learned a long time ago that more memory would make their lives easier. The last system we sent to the US Olympic Committee had 24GB of memory installed which made Adobe Premiere sit up and bark like a dog. We’re just now updating our Element video editing workstation to 12-core and, as with before, you can match that with 48GB of memory. It’s a beautiful thing.

That said, there are still a lot of people out there attached to their legacy gear. Maybe you’re updating your computer and your budget doesn’t allow you to replace all your software and hardware at the same time. Maybe you’re in love with a certain plug-in that just refuses to play nice with 64-bit. For those people, we do everything we can to help them protect their initial investment. But if possible we do recommend getting the most up-to-date version you can, load 64-bit and take advantage of all its benefits.

As a side note, though some Rain computers ship from our dealers (Best Buy, Amazon, B&H, etc) with 32-bit, we have a program in place to help the user update to 64-bit at no additional cost once they get their computer home.

Noel notes that 64-bit support is vastly improved over the past – and this coming from one of the first software vendors to embrace 64-bit Windows in any industry, let alone in music. (SONAR first supported 64-bit way back in the XP x64 days.)

Any new CPU you can buy these days is capable of running 64-bit Windows. As a result of this proliferation driver support for X64 is a lot better now than it was a few years ago. In this environment it makes the most sense to install the 64-bit version of Windows 7. With a 64-bit OS you get the best of both worlds. You get the advantage of expanded memory as well as the ability to run 32-bit applications. 32-bit applications on a 64-bit OS run fine and in some situations might even show better performance than when running under a 32-bit OS.

In other words, if you’re using any music hosts (or video editing software) with native 64-bit support – just one – going 64-bit is a no-brainer so long as you’ve got a 64-bit computer like those based on the Core 2 Duo CPU. But what if you don’t have any 64-bit software? My standing advice had been to stick with 32-bit, but Noel actually disagrees – and I have to admit, I see his point. Noel writes:

I would argue that even if you don’t have any apps that currently take advantage of X64 [Windows 7 64-bit] it still has advantages to go with [64-bit] for the upgrade options. You can always add more memory to the system or later introduce native 64-bit apps, something you cannot do if you have a 32-bit OS without reinstalling Windows and starting from scratch.

So, is there anything that should keep you on 32-bit (aside from owning an older computer with a 32-bit-only CPU?) What about ReWire?

You don’t lose ReWire by running on a 64-bit OS. You can still run a 32-bit version of the application on a 64-bit OS and have ReWire access. The only reason I can think of that might deter someone from a 64-bit OS today is if they had some legacy hardware that didn’t have 64-bit drivers. I.e., you cannot run 32-bit drivers on a 64-bit OS, since those have to be native.

At least you can make that decision based on your music host, not your music plug-ins. A key feature of a modern DAW like SONAR is, even though it runs natively in 64-bit, it doesn’t require that you give up your 32-bit plug-ins. That’s a very big deal, because a lot of plug-ins – even paid ones, let alone freeware oddities – aren’t yet 64-bit. For its part, Cakewalk has been updating 32-bit support.

In SONAR 8.5 we addressed many user-reported VST compatibility issues with Bitbridge. Additionally, Bitbridge XR now breaks the memory barrier for 32-bit VSTs allowing you to run as many 32-bit VSTs as you want in SONAR X64. You can use up to 2GB of memory PER 32-bit VST and run multiple BitBridge servers allowing up to 128 GB of memory for your 32-bit plug-in. With Windows 7 and SONAR 8.5, more and more users are making the leap to X64 systems running systems with 12 GB of memory or more to run multiple memory hungry plug-ins in their sessions.

That’s anecdotal evidence, however. Here are some hard numbers. Aside from the benefits of expanded memory access – useful if you use big sample libraries and the like – 64-bit can have some real-world, quantifiable, verifiable performance benefits. Noel writes:

Here are some external studies/benchmarks that compare X64 performance against X86 on the same hardware.

http://www.noelborthwick.com/minidump/2009/12/a-case-for-64-bit-windows/

Disabling Power Management to Improve Multi-Core Performance

Most of the usual optimizations apply to Windows 7 that applied to previous versions. You’re best off disabling resource-consuming background applications like antivirus software, keeping drivers up-to-date, working with good quality audio interfaces, and the like. We do have a couple of specific pieces of advice for Windows 7, however.

One such detail, while it’s unlikely to impact everyone, is that disabling some power management on multi-core systems can improve performance. Noel explains, complete with instructions:

There has been some controversy about the new core parking feature in Windows 7 which was introduced for more “green” power management. On quad core and higher systems, some users have reported that core parking can cause audio glitches. It could be system specific since I haven’t personally experienced this issue on my own DAW which is pretty much running a vanilla Windows 7 install with a Core I7 (8 cores). In any case even though there is no user interface in Windows 7 to enable/disable core parking, fortunately there is an documented way to disable it in the Microsoft performance tuning guidelines. Look for “Core Parking” in this document http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/Perf-tun-srv-R2.docx

To summarize:

To turn off core parking, set the minimum cores parked to 100 percent by using the following commands:

Powercfg -setacvalueindex scheme_current sub_processor bc5038f7-23e0-4960-96da-33abaf5935ec 100 Powercfg -setactive scheme_current

Smarter File Management

With Windows generally working better out of the box, though, here’s a quick tip that can help make it more usable when you’re actually working on projects. Noel has become a big fan of Libraries (and yes, you’ll find access to them in SONAR’s file dialog):

Win 7 has support for a very useful feature called Libraries, which can be a very handy way to keep track of data scattered around your hard drives. Unfortunately Libraries do not directly support folders on networked locations. On attempting to add such a folder to a library you get an error message telling you the location is not indexed. Apparently libraries rely on folders being indexed. This shortcoming greatly reduces the usefulness of libraries for users who store folders in networked locations.

Fortunately, I came across a workaround to the libraries problem here which uses symbolic links to get around this limitation: http://hubpages.com/hub/Adding-a-Network-Directory-to-a-Library-without-Indexing-in-Windows-7

More Resources

Keyboard Magazine has my full comparison of Windows 7 and Snow Leopard online:
New Decade, New OS What Matters to Musicians in Mac OS X Snow Leopard and Windows 7, by Peter Kirn

I’ve been writing “geeky as we wanna be” looks at Windows for some time – and rightfully so, I think; musicians push operating systems hard. I only wish the larger tech community paid greater attention to what we do, because we’re often best able to torture test any OS, Mac, Windows, Linux, or mobile.

Here’s some of our past coverage of Windows on CDM:
Obsessive Windows 7 Under-the-Hood Guide for Music; Can You Finally Dump XP?

Vista Tweak: Use the Audio Profile Cakewalk’s CTO Uses

And if you’re looking for some tips to get the most out of Windows:
Tips: Fix Windows Explorer, Be Happy

12 Free and Cheap Must-Have Music Utilities for Windows

10 Free Non-Musical Windows Software Every Musician Should Use

For a look at a 64-bit-native DAW, check out my review of SONAR 8.5.2:
SONAR 8.5.2 Hands On: Tradition, Meet Tempting Treats

Addendum: Finding 64-bit Crashes

This is an extremely obscure issue, so if you’re not interested in gory details, stop reading now. But because we like gory, technical details, I’ve decided to add it. It’s not a reliability problem with 64-bit Windows — far from it; you won’t actually see it until you encounter a crash, and even then, it’s useful only to the people troubleshooting. But it does demonstrate the power of getting to the bottom of an issue, and there is a fix. (So, Mac users, I don’t want to hear any “see, this is why I switched to a Mac.” You can get into weird, technical things if you dig deep enough in any OS, period. Shield any innocent eyes.)

Noel adds a description of troubleshooting 64-bit Windows crashes as follows:

How to make your apps crash gracefully on 64-bit Windows
OK this is admittedly a weird topic Why would anyone actually want their app to crash you may ask? To answer that question we need to have some background about why applications crash.
An application crashes when it performs an unexpected operation or encounters what is called an “exception condition”. Exceptions include unwanted operations like writing to invalid memory locations, divide by zero errors, page faults, etc. Programs can end up with exceptions like this for a variety of reasons – bugs in the host code itself or even due to bugs in loaded plugin DLL’s which share the same memory and address space as the host application. Normally when an error like this occurs, Windows will display the familiar error message “This Program Has Performed an Illegal Operation and Will Be Shut Down” and the program will close. Some applications like SONAR handle such errors more gracefully and will even try and intercept these exception and attempt to allow the user to save their work before exiting the program. Additionally on Windows you can choose to save what is called a Minidump containing “post mortem” debugging info that is very useful to developers to find out why the program crashed.

Recently we began noticing a pattern where we were receiving Minidump’s from crashes on from 64 bit Windows systems X64 where the dumps contained useless or apparently invalid information about the crash. This made it very hard for us to diagnose such issues. I was even able to reproduce this by writing a simple test application that forced a crash. In one case I found that the crash was reported in a completely different location and in another the application behaved as if the exception didn’t occur! This is actually very bad since when damage is done to the app the best scenario is to actually shut down the application or you risk data corruption or worse. So you really WANT your app to crash when something like this happens. I logged a bug with Microsoft about this with a test application. I recently heard back from their developer support about this issue. It’s an interesting problem that Microsoft is aware of and have issued a hotfix for.
Here is a link to a Microsoft blog post describing this problem in gory detail if you want to read more about it.
http://blog.paulbetts.org/index.php/2010/07/20/the-case-of-the-disappearing-onload-exception-user-mode-callback-exceptions-in-x64/
And here is the link to the hotfix if you want it now. This hotfix will also be rolled into Windows 7 SP1. I hope that this is not required in the final version but currently the fix requires you to set a value in the registry to enable it.

http://support.microsoft.com/kb/976038

I’m a big believer in open platforms, computer platforms, and the power to customize stuff. Unfortunately, there’s a simple reality: developers’ work is sometimes a bit like the proverbial bull in the china shop. (Code SMASH!)

In short: a lot of times when Windows’ file managemer Explorer is hanging, it’s not Microsoft’s fault. Misbehaved shell extensions – often installed without your permission by other tools you’ve installed – are often responsible.

If you’re like me, you’re willing to put in a little bit of effort if it saves you time down the road. For me, a few tweaks to Explorer resolve some of Windows’ biggest annoyances and make it workable, productive, and enjoyable for music making. (Greetings, FL Studio and SONAR and Reaper and Windows-only plug-ins!)

At the end of last year, I wrote up a story on troubleshooting Explorer for Rain Recording, the custom music and visual PC makers. (Rain takes care of a lot of the other Windows annoyances right out of the box, but shell extensions are added by software you might install after you get one of their boxes.) It’s not really a music story, but I think if you can solve computer annoyances, you can get on with music making – and I still believe computers are far more interesting, on balance, than outboard gear alone. Explorer oddities are not among those reasons, so I:

• Nuke bad shell extensions
• Customize the context menu so that, instead of a terrifying, moldy wasteland, it becomes a productive tool
• Stop network bottlenecks from hanging the system while it looks for disconnected file servers

Troubleshooting Windows Explorer [Rain Recording Pro]

I’m interested to hear how you work, though, and I’m sure there are tips I’ve missed.

Previously:
10 Free Non-Musical Windows Software Every Musician Should Use
12 Free and Cheap Must-Have Music Utilities for Windows

By the way, to revisit a previous story, I’m still not entirely happy with any antivirus software. Antivir is quite lightweight, but posts ads for buying the full version every time it updates. I still long for a simple, lightweight tool that doesn’t nag you and can be switched off (updates and resident protection) whenever you want. I also have to question whether viruses are the threat they once were – meaning, with other protections, what you may want is something a lot more modest.

Rain Recording make audio-ready notebooks – that is, they’re pre-tested to function well with audio software, with Windows tweaks, driver selection, and configuration all chosen and tested for music and visual production, and no crapware installed. They’re one of a handful of music-friendly vendors that does that (see also: PCAudioLabs, etc.). Given that the PC music making experience can range from awesome to awful depending on which hardware and (particularly) drivers you’re on, that’s no small matter.

Rain has always styled themselves a premium brand. But the latest Diablo really does go to extremes spec-wise. It’ll cost you – base price starts at US$4000, though that’s not as high-end as these sort of desktop specs commanded more recently. Intel and AMD/ATI really are economizing, even at the high end. But cost aside, this machine really maxes out components. You have to admire the results:

• Quad CPUs: up to 2.53GHz Intel Core 2 Quad 12MB/1066 MHz “Montevina” Centrino 2 — the most powerful brain you can put in a laptop right now
• Up to 8 GB DDR3 RAM (and if you boot a 64-bit operating system like Vista x64 or – cough – Linux, you can use all of it)
• ATI Radeon MR HD3870/512M DDR3 RAM — just about the most powerful GPU (and some people do prefer ATI to NVIDIA), giving you up to two discrete GPUs
• 17″ display at 1920×1200
• Optional dual 320GB 7200RPM SATA drives with 16MB cache
• 1x eSATA, 3X USB2, 3xFireWire (yeah, you read that right – one onboard FireWire, plus two more using a bundled, TI chipset PCI ExpressCard that pops into that slot, also standard on the lower-cost LiveBook)
• 1 x HDMI, 1 x VGA, card reader, headphone out, mic in, gigabit RJ45 Ethernet, fingerprint scanner

The key specs, of course, are the quad CPU, that ATI GPU, and the maxed-out-res 17″ display. Given those specs, the weight actually isn’t all that bad – 8 lbs. with the 12-cell battery (which you’re going to want, as this machine is likely to suck up electricity in a hurry).

You can put audio on a dedicated chipset (the TI, which isn’t currently available from Apple). You can run two drives in RAID-0, or opt for solid-state drives (which have been improving in performance and value at a pretty impressive rate). And the ATI chipset means this is a pretty powerful visualist / visual production workstation – that also happens to be faster than a lot of high-end gaming laptops, for your off-hour enjoyment..

This is usually the point where someone says, “but do I need all that power to –”

No. You don’t. This is a bit like buying a souped-up supercar — and likely to be about as fuel-efficient. You might “need” this if you want to play Crysis between Pro Tools sessions. (I’ll let you bend the definition of “need” there.) That’s not to say you won’t get a lot of performance out of this, though, and it’s nice to know you have this option if you want it. The GPU only really impacts visuals at the moment, but with the push to do more processing on the GPU, that could change soon even for audio.

Actually, maybe the reason Rain keeps misspelling the GPU as “discreet” is that you can “discreetly” buy one of these and hope your significant other / the IRS / your conscience doesn’t notice you just bought a killer gaming rig as your (ahem) pro audio machine.

For mere mortals, I like the $1999-base-price LiveBook from Rain. It actually gives you a fair amount of this performance, all of the same I/O specs, and compares favorably on specs against Apple’s rival (including offering some serious FireWire and expansion the Apple lacks). And, incidentally, it isn’t a bad gaming machine, either, in case you want to join some of the CDMers the next time they fire up Left 4 Dead.

I do find all of this interesting, though, on two points. One, if any had doubts that you could buy a pre-configured PC and know that it’ll work reliably on audio tasks, Rain ought to put those doubts to rest. I’ve tested the previous Diablo and LiveBook, and out of the box they were ideal audio machines – no tweaks required. It’s absolutely possible to build or buy a mainstream PC that does that, but the luxury of knowing someone at the other end has actually tried running Ableton Live and SONAR sure is nice. (Heck, that’s not necessarily true of Apple – as people found out the hard way during some buggy early releases of Leopard, happily since fixed.)

This also demonstrates that said PC vendors don’t have to fall behind the “enthusiast” custom builders who cater to gamers – if you want to push the envelope on your laptop for audio and visuals and not just games, you can do that, too.

I certainly know not everyone can — or should — spend $4 grand and up on this particular machine. But just like that supercar, it’s sort of nice to know it’s there. And hopefully it can start to serve as a wake-up all that there are communities pushing their PC to the bleeding edge who aren’t primarily gamers.

Diablo Product Page [Rain Recording]

Diablos don’t hang around long, but I do hope to get my hands on a current-generation Rain soon; stay tuned.

Speaking of Rain Recording, Rain is about the only vendor I’ve found that offers a 2-port FireWire ExpressCard known to work well with audio interfaces. Now, your mileage may vary depending on the chipset in your laptop, but based on what I’ve been hearing, this looks like a good option. I’ve also seen a cheap (US$30) card floating around some random Internet vendors; it’s so cheap, I’m probably going to buy one just to see if it works. I’ll report back.

2 Port FireWire Express Card (formerly ADS Tech PYRO1394a) [Rain Recording]

I get nothing out of this, for the record; Rain actually hopes you’ll get this card with one of their laptops, but I’m just as curious to hear how it works on other machines. Of course, this would be a nice add-on not only for PCs, but also potentially for MacBook Pro users wanting dedicated FW400 ports and the TI controller – theoretically, at least. Let us know what happens if you take the plunge.

If you’ve had experience with different chipsets and ExpressCard slots on Mac or PC, we’d love to hear it. And I hope to offer my own tests soon.

Updated: The StarTech EC13942 also shares the TI chipset and is available from a number of vendors if that’s a vendor you prefer. It’s the only one endorsed by PreSonus aside from this former ADS Tech card that Rain sells — and may give you better results with other, non-PreSonus hardware, based on reports I’ve read. See PreSonus’ official word on the matter:

Presonus Hardware Compatibility: Approved Chipsets [PDF]

One of the things that attracts me to computers: choice. So it’s worth noting that you do have choices when looking to laptops, PCs included. (This sounds like those lame “We know you have a choice in your travel plans” announcements you get on airplanes. Unlike those choices, though, these are genuinely different – thankfully.)

So let’s cut straight to the chase: there is a choice between Mac and PC, and there are choices on PC that keep it competitive (to say nothing of Linux). If you’re looking for a rig that runs PC-only tools like FL Studio, and you want more hardware choice to get there without being locked into a Mac, Boot Camp, and an extra Windows license, you have options.

Rain Recording has just introduced a revised pro laptop offering. You may have seen the announcement around, but I did get to talk to them while they were developing this, so I want to offer my own, semi-biased reflections. Rain is a custom system builder focused on music and audio applications. They and a handful of vendors like them do test their configurations with actual audio software, which isn’t generally the case with bigger PC laptop makers. And they offer music and audio-specific support, beyond even what Apple can offer.

Now, that said, I have to say I haven’t actually been that blown away by what custom builders have been able to do in the laptop space. The problem is, builders don’t have the kinds of options with laptops that they do with desktops; traditionally, you’ve needed huge manufacturing scale to get many choices. Even a lot of big brands get someone else to make their machines, so custom builders really face an uphill battle with limited barebones systems. Rain and others have put together some interesting systems, but at a price premium and generally lagging some of the hardware options on the mainstream laptops. For that reason, many PC users have chosen to stick it out with “commodity” machines and try to navigate to the ones that do music well.

The current LiveBook, though, is the first that I think really makes a custom builder competitive – and it’s the first I’ve started to covet for my own desk. It’s pricier than some mass-market machines out there, but it is competitive, and with far more of a guarantee for audio performance and reliability.

• Processors are now available up to 3.06GHz on the Centrino 2 “Montevina” – so it’s about as current as you can get architecturally
• Prices start at US$1999 – and that’s already a pretty fully-loaded machine
• The body is all-aluminum and offers a laser-etched case
• The GPU is no slouch: NVIDIA 9600M GT 512M standard, with a healthy 1680×1050 resolution on the 15.4” monitor (which I think is about perfect – any higher is hard to see, any lower cuts down on real estate)
• Lots of ports: three FireWire 400 ports (with the standard ExpressCard plugged in), one eSATA, a card reader, HDMI and VGA out, and two USB 2.0 ports
• Fast, audio-ready drives: up to 320GB 7200RPM (there’s also now a solid-state option, but I prefer conventional hard drives for their price/performance/capacity ratio)

This issue of specs has already started a debate, even among Mac users. And that’s the world we live in: PC buyers are considering Macs, and at least a handful of Mac users are seriously considering PCs. (At the very least, it’s not uncommon to find people with both.)

From the angry thread about FireWire missing in the (non-Pro) MacBooks, one MacRumors reader points to this very Rain LiveBook. Here’s what I’d put in the pros column:

• eSATA is very useful for high-speed storage (you could add it to the MacBook Pro, admittedly)
• The Rain has a TI chipset for its ExpressCard-provided FireWire, which has been more stable for audio performance – even on Mac OS
• Rain has up to 8 GB RAM, and with 64-bit Windows you can use it
• Blu-ray is an option
• You get a dedicated numeric keypad, which is a big boon for shortcuts – think Sibelius on the road, for instance (the notation editor relies on the numeric keypad for quick input)
• For some, Mac OS is the big draw – but for others, Windows is, depending I think largely on the apps you want to run if not everything you use is cross-platform

Don’t get me wrong: I think the Apple machines stay really competitive. The I/O gripes aside, the new machines are pretty remarkable. And you lose a lot going to Windows from Mac OS – Core Audio and built-in inter-app and over-network MIDI, for instance. On the other hand, I’m perfectly happy running FL Studio, SynthMaker, SONAR, Vegas, and Sound Forge on my Windows laptop and not having to use Boot Camp on a Mac to get there, and with solid ASIO drivers, I can get terrific performance from Windows. I don’t personally agree with the conventional wisdom that makes people just “default” to either choice – I think the choices are interesting.

Specs aside, Rain really does test every configuration with audio software, and they think about the impact of specific drivers and components. That’s not so much of an issue on the Mac, but part of the variability of quality on the PC has absolutely been about certain configurations and driver issues causing problems. You can get audio software pre-installed from Rain, you can call Rain about audio questions, and they’ll even install Windows XP for you, if you like. (I’ve been to New Jersey and seen Rain’s facility and talked to their testers. Another vendor offering similar services is California-based PCAudioLabs – they’re also worth checking out; I’ve heard nothing but good things from people using machines from both makers, which says something, too.)

This comes back to the question of what your ideal configuration would be. If I had my dream machine on this LiveBook, I’d have a couple more USB2 ports on the LiveBook, and DVI or mini-DisplayPort plus TV out for video. But it is a nice-looking system. Rain will certainly be hearing my feedback, and they do offer a fair number of custom options.

Interestingly, ASUS and Intel have teamed up to do a site where they get communities voting on what they want from a laptop, called WePC.com. It’s the opposite of Apple’s design process – though I suppose, arguably, it could result in The Homer Effect. (Episode of the Simpsons in which Homer designs a car and gets something … well, overdesigned. But Homer didn’t know anything about cars. Odds are, as a computer musician, you actually do know what you want and need.) Anyway, just so we’re heard, do go vote for audio stuff.

The bottom line for me: I don’t think we always benefit from someone else choosing what we need.

It’s really not worth debating which laptop choice is better, because there’s not an answer to that question. Laptops – even Macs – are bundles of literally thousands of detailed hardware decisions, and I’ve never seen two users doing exactly the same thing with their machines. That means it’s almost impossible to get a machine that’s absolutely perfect, anyway; it’s more about finding the right compromise. And OS arguments tend to devolve into meaningless debates. The actual internals of what makes operating systems work is so technical and involved, it would take a lot more than a few lines to talk about with any accuracy.

But it’s not about which is better; it’s which is better for you. So, instead, I’ll ask: got a laptop you love, Mac or PC? In the market for a new machine, economic downturn be damned? Which one are you thinking? And what would your perfect machine look like – within the realm of possibility?

Disclosure: I recently bought a cheap ASUS (pronounced ah-SOOS) laptop to replace a sudden failure of a machine. (I got an M51Sn-C1; more on that later.) I own a MacBook which I use pretty heavily, too. I’m writing stories for Rain. Heck, I just generally like computers – and I’ve got some gripes for every OS and hardware maker out there. So, like you, I’m biased about everything because I live and create on these machines – more hours than I sleep, I think.