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

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.

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

It appears that network changes in Mac OS 10.5.7 could adversely impact some hardware, specifically the Euphonix EuCon line of controllers. Here is information sent to customers today – thanks to reader Oliver Lucas for spotting this.

Please note that the new Mac OS update released yesterday, Version 10.5.7, breaks support for the feature in EuControl that automatically detects what control surfaces are attached to your network.

Euphonix is working on a fix – please DO NOT update your Mac OS until we release a software update that addresses the issue, as your MC Mix/MC Control will not be seen by your Mac.

For those users who have already updated to Version 10.5.7, you can roll back your Mac OS to the previous version if you are using Time Machine.

Update: this is now fixed.

There are no other apparent audio issues with 10.5.7 that I can see. (Visualists may be pleased about some NVIDIA driver improvements.)

My sense is this is most likely limited to the EuCon, which connects via Ethernet. It sounds specific enough that even other networked music hardware, like the Lemur, may be immune – I’m posting this partly in hopes, though, that Mac users can report back and let us know.

Here are the network changes:

• Improves network performance when connected to certain Ethernet switches that have Flow Control enabled.
• Improves stability for network home directories hosted by Mac OS X Server v10.4.
• Improves Finder search results for network volumes that may not support Spotlight searching, such as Mac OS X Server v10.4, Time Capsule, and third-party AFP servers.
• Includes several improvements to Directory Service and Client Management.

I’ve said it before, but I’ll say it again: I think this happens too often on Mac OS. It seems like Apple could do more to make it easier for customers to roll back an upgrade, and more to communicate to developers what changes may be.

That’s not simply a criticism. I think Apple excels at producing an exceptionally high-quality operating system, and the expectations users have for desktop reliability set a higher bar than the norm for Linux or Windows. They also run an aggressive release schedule, one that often gets improvements and fixes into user hands sooner. But then, music users are especially sensitive, and I think the situation would be even better if developer communication were improved and rollbacks were possible even without Time Machine.

Anyway, Apple (or Microsoft, or even to some extent Linux) you can’t control. What you can control with any upgrade is to make sure you have an image of your system prior to the upgrade and that you thoroughly test hardware on which you rely immediately so you can roll back. That’s always true on any OS, period. (Apple, to their credit, says just as much in their support document.)

More information is always appreciated.

Is your MacBook Pro a rightie?

Something’s going on with the one or two left-hand USB ports on all MacBook Pros. I’ve heard some issues with hard disks, and now some problems with audio. (Controllers are evidently just fine.) The solution: use the right-hand USB port for audio instead.

Updated: Reader Adam suggests that this is probably due to a difference in power delivered to the respective ports. USB audio requires more power, and so odds are you’re under-delivering on the left-hand ports. I’m inclined to think that this is exactly what’s going on – unless someone knows something else. (Easy way to test: try plugging in the power adapter. Note that this can be an issue with FireWire, too.)

In fact, even if for some reason M-Audio has found another reason behind this, Andy Ihnatko noted the issue with different USB ports and power variation way back in 2008. It affects non-Pro MacBooks, and I expect likely many PCs, too.

The MacBook. All USB Ports Are Not Equal [Wired Gadget Lab]

M-Audio (now Avid) has gone as far as to tell its customers officially to avoid the use of that port for audio entirely. Native Instruments forum users have evidently had similar discussions. Via matt_bot on Twitter:

The use of USB Audio Devices on the Left-Hand USB Port Is Not Recommended.  This applies to ALL MacBook Pro Models (Core Duo and Core 2 Duo).

•    The 15" MacBook Pro models have 1 USB port on the left side, and one USB port on the right side.
•    The 17" MacBook Pro models have 2 USB ports on the left side, and one USB port on the right side.

Due to the current USB configuration of the 15" MacBook Pro under OS X, use of USB audio devices is supported on the right-hand USB port only.  Use of such devices on the left-hand USB port(s) is not advised because it may cause audio interrupts and/or dropped samples.  However, the use of an iLok on the left-hand port has been qualified and is fully supported.

Due to the current USB configuration of the 17" MacBook Pro under OS X, use of USB audio devices is only supported on the right-hand USB port, and the left-hand USB port farthest from the screen.  Use of such devices on the left-hand USB port closest to the screen is not advised because it may cause audio interrupts and/or dropped samples.  However, the use of an iLok on the left-hand port has been qualified and is fully supported.

These USB port recommendations are specific to USB Audio devices only (such as the FastTrack USB or Audiophile USB).  USB Keyboard and Control Surface products do not have a recommended USB port at this time.

MacBook Pro recommended USB port(s)

That’s got to be a tough technical advisory to issue, like having to tell your users they should turn around in their chair three times counter-clockwise and shout “Mimmymabby” before recording. But I’ve heard indications that devices other than M-Audio’s are seeing symptoms, so I’m inclined to believe there may be something to this.

Now, before you use this to assume this means FireWire is better than USB or PCs are better than Macs or veganism is better for your love life or the end times are upon us, the whole point is what’s causing the issue and why. (Correction: I’m satisfied enough with Adam – and Andy Ihnatko’s – explanation above that I think there’s not much mystery here! So quit with conspiracy folks and trashing vendors you don’t like, folks. Technology doesn’t need superstition; it needs users hungry to know what’s actually going on.)

Of course, that raises a question: why are some USB ports not entirely up to spec on power? My hope would be that USB is USB and you don’t have power variations between ports, but then, I live in a fantasy world of naive hope. (Can anyone comment on PC laptops and power on different ports? I imagine some would have exactly the same issue.)

One theory for the power discrepancy: John von Seggern claims via Twitter that the issue could be the iSight video camera, which does indeed use the USB video bus. (I would think it shouldn’t draw power when switched off, but perhaps that has caused some other change in the configuration.)

Further, we have reports that not only the iSight, but also Bluetooth and other power-consuming peripherals are on the same bus, as well. (That means turning off Bluetooth might be a good idea if you don’t already.) And we have at least one PC with the same issue. This will definitely be something to research with computers, as it’d be pretty desirable to get machines that, erm, don’t do this to their USB ports.

And someone’s having the opposite port work or not work? Now I’m really confused. (I guess we could simplify all of this to say if you’re having problems with USB audio, try either connecting your AC adapter or switching USB ports.)

Amidst all of the USB audio hating, I have to say, it is possible to get good performance out of USB audio interfaces. On the other hand, removing FireWire from MacBooks seems again like a poor choice.

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.

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]