I love the sound bugs make when you squish them under a solution.

AlexP, whose blog is also a great source for multitouch and the Sony PS3 Eye Camera and Windows drivers we used in the recent hackday, has been diagnosing his MacBook under Windows Vista. Hardware problems are often the source of sound blips on computers. I’ve talked previously about using the DPC Latency Checker to find this issue.

The good news: Alexander has found the problem (the Broadcom Wireless Adapter in some Apple MacBooks) and a solution (switching off Windows’ automatic wireless network search when you don’t need it). I actually wonder if a similar problem was culpable in early problems with network WiFi on Mac OS X Leopard. Whatever is going on, check out the fix here if you’re encountering this problem. And let us know if you’re seeing this on machines other than just the MacBook revision F; I’d imagine any PC with a similar wireless adapter might have the issue:

MacBook Rev. F Audio Skipping in Vista Analysis and Solution – Part 2

And yes, hardware/driver problems may frequently manifest as what Windows terms DPCs – basically, a symptom of hardware usage that can interfere with reliable audio performance. I’m curious whether WiFi connections specifically may be a cause in other cases. The problem is almost certainly not limited to computers from Apple – especially since, in this case, the MacBook is just behaving like any PC laptop with similar specs.

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.)

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.

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!)

If you haven’t been following Max 5 updates, the folks at Cycling ‘74 have been aggressively bug squashing. The changelog for 5.0.6 alone is exhaustive. (Via @rekkerd on Twitter, of rekkerd.org.)

Updated: Also new in Max 5, it’s now possible as of 5.0.6 to properly save your patches to a version control repository. Don’t know what that is? Now’s a perfect time to find out — it means it’ll be easier to track changes you make to your own patches, and easier to collaborate with other people. And it’s free. From adamj, on comments:

RE: the diff’ing issue I was talking about above. Timothy Place (one of the Max developers) shared this helpful tidbit:

“Since the change log is a mile long, I’ll point out an obscure new power-user feature in Max 5.0.6.

You can send a new message to Max like this (or put it in an init file):
;max sortpatcherdictonsave 1

This makes it so that the JSON files that are use by Max for saving patches will keep the dictionary in the same order (alphabetized) every time you save. If you are keeping your patches in version control (e.g. SVN, GIT, CVS, etc.) then this should make your diffs a lot more usable.”

See: Version Control and Sharing for Patching: Keep Those Max, Pd Patches in Order with Git

And in other Max news, Expo74 will be a full-blown Max conference in April in San Francisco. You still have a few days to lock in the US$295 intro price (through 3/1). On the menu:

• C74-taught workshops for users: live looping, 3D, Max for Live, new timing objects, etc.
• Workshops for developers: C programming and the Max external API
• Special guest speakers, including Robert Henke — but also Miller Puckette, the creator of the original Max and developer of Cycling ’74’s open-source rival Pd.
• An afternoon on teaching Max
• A “Science Fair” for sharing projects
• Field trips
• A “Relationship Manager” – a sort of conference concierge – plus access to the C74 folks, a bit like the Apple Worldwide Developer Conference

Expo74

It’s good stuff. And the price seems a very reasonable deal for a conference.

You know, it also reminds me that some of the events around the open-source tools could be friendlier than they are. And we like science fairs. I’m not sure that I’ll be able to make it out to California in April (I’ll be there in March for the Game Developer Conference), but eager to hear how this goes.

But speaking of open source, don’t want to spend April at an event for a proprietary tool? Prefer the East Coast to the West Coast? Like code better than patching? Like tools that begin with the letter “S” better than the letter “M”? Want tools that make you think of supermassive black holes? Oh, April in North America has you covered regardless of what you like. One moment while I write up another post…