Apple’s "point" releases — those seemingly-harmless updates you get automatically in Software Update — do sometimes break stuff. I tend to ignore the updates until I’ve had a chance to confirm they’re okay. Case in point: it looks like 10.5.2 can result in glitchy audio on laptops.

Native Instruments has an official statement out on the problem, but according to them, this issue can affect software from other vendors, as well:

User feedback and internal testing indicates that recent changes introduced by Apple in Mac OS X 10.5.2 can cause audio dropouts and similar problems on Macbook/Macbook Pro computers. This issue is not limited to NI software in particular, but applies to performance-criticial music software in general.
Therefore, Native Instruments currently cannot guarantee the proper operation of its products under Mac OS X 10.5.2. If possible, users should refrain from upgrading beyond Mac OS X 10.5.1 until further information about this issue becomes available.

Now, I will say this: I am frustrated with Apple’s OS upgrade approach — and I think on any OS, media support is the most vulnerable area.

If we’ve learned one thing on this site, it’s this: if it’s a computer, big or small, someone’s going to find a way to make music. The iPod / iPhone, with their Mac OS-derived software guts and a multi-touch interface, are no exception — with or without Apple’s blessing. Here’s a look at what people are doing, including some apps you can download right now, and where this might go musically, whether it’s just a couple of fun toys or trying to make that pretty pocket device an instrument.

Background

There’s no question what makes the iPod Touch and iPhone significant: they are tiny, palm-sized Macs, running all the stuff that makes a Mac a Mac — Cocoa, of course, but even music-specific stuff like Core Audio and Audio Units. (For more details, have a look at the WWDC session highlights spotted by Palm Sounds, all of interest to audio specifically. It could easily be mistaken for desktop development. The Unity 3D game engine is on its way, too.) And even if you’re not planning on picking up mobile Apple hardware, this says something about the rapidly-advancing direction of mobile computing. There was a lot of talk about mobile convergence in the 90s and early years of this decade, but now it’s here.

Of course, there are strings attached. Apple was in no rush to get an official SDK and firmware out to developers, relenting only this year. And it strikes me as I see iPhones on the go that the coolest stuff is happening using "jailbreaked" phones — phones specifically hacked to get around Apple’s requirements. Even when Apple goes official, that’s likely to continue: Apple has placed some arguably onerous restrictions on development. Software has to be Apple-approved and sold via iTunes, and basic capabilities like multitasking are a no-no. Someone’s just called? Great. Your app just quit. (Bizarrely, even extremely low-end phones are willing to multitask, but not Apple’s far-superior hardware.) Whatever arguments you may make for Apple’s approach, my guess is the hard-core iPhone/Touch owner will remain outlaws to get the full capability out of their device.

Also, despite some common elements, the implementations of APIs on the mobile devices are not as complete as on desktop Mac OS. Chad from miniMusic tells PalmSounds that some features currently available in Core Audio on the desktop are missing on mobile — at least for now.

Then there’s the fact that the major Apple strength is Cocoa and Mac-based development — meaning I remain curious about what the Windows and Linux camps will do in this space, particularly Linux. Those folks do have a major, uphill battle to match Apple’s achievement here in terms of software. One would think, though, that Linux should have a bit of an edge because its comparative modularity, whereas Mac OS X was designed solely as a desktop OS — though mobile development is hard, either way.

For Mac-based development, though, iPhone and iPod Touch are here now (always a major advantage in technology). Its full-fledged Mac roots have led to the fanciful image at right and some heated discussion on CDM’s forums earlier this spring. But let’s have a look and what’s here now for the iThings, like MooCowMusic’s Band app (pictured, top).

Everything has an “API” these days, but what that means in practice is often not so exciting. You can make little widgets for Facebook, or post recent Twitter messages, or do other simple developer tricks. Echo Nest’s “Musical Brain” API is more far-reaching: it’s an API for music. All music online. The first of a series of developer tools, “Analyze” is designed to describe music the way you hear it, figuring out tempo, beats, time signature, song sections, timbre, key, and even musical patterns. More developer tools will follow.

Twelve years in development, the Musical Brain is a bit like a digital music blogger. It’s been crawling the Web while you sleep, reading blog posts, listening to music to extract musically-meaningful attributes, and even predicting music trends. It’s like almost like a robotic, algorithmic Pitchfork. (And I’m serious — it may be April Fools’ Day, but this is real. That’s what the “brain” claims to do, backed by research at UC Berkeley, Columbia, and MIT.)

What does all of this mean? The Musical Brain may not be replacing your friendly local music blog any time soon, but what it can do is infuse some musical intelligence into applications like music visualization. The Matmos album at top used the Analyze algorithm to map the timbral profiles of songs on an upcoming album; that graph was then rendered by an artist in watercolor, translating the digital into traditional paint media.

The Analyze API could also enable everything from Web music apps and mash-ups to live audiovisual performance tools, or even smarter music games. That’s the reason co-creators Brian Whitman and Tristan Jehan, both with PhDs from the MIT Media Lab, chose to open up development to a broad audience. I got to speak to Brian a bit about the project.

“Sure, the OLPC project is supposed to do wonderful things for children of the world, but what has it done for me, lately?” Well, if you fancy yourself one of the Earth’s children, the OLPC organization has assembled 8.5 gigabytes of sample content that’s free and Creative Commons-licensed — free to acquire, and free to use.

Jacob Joaquin, who runs the terrific thumbuki blog and the Csound Blog and is part ofthe team developing Csound for the OLPC’s XO laptop, shares the news via Dr. Richard Boulanger at Berklee. (See the press release as a zipped .doc.)

Plenty of people contributed top-notch sound: the Berklee College of Music, Csound developers around the world, electronica celebrity BT (himself a former Berklee and Boulanger student, among other alums), M-Audio and Digidesign, and the Open Path Music Group.

They’re donated under a Creative Commons Attribution license, so you can “freely create, compose, mix, remix, share, distribute and redistribute these samples and use them for any purpose as long as you clearly attribute the source.” That means anyone, anywhere can make use of this library — no OLPC required.

http://wiki.laptop.org/go/Sound_samples

http://wiki.laptop.org/go/Talk:Sound_samples

Csound, OLPC Style

Whether you like the OLPC laptop itself or not, there’s plenty going on with the project. There’s the immediate impact of the hardware and software, yes — and plenty of opportunity to praise or criticize its utility there (perhaps the mark of a good, ambitious project). But there’s also the secondary impact. The OLPC has captured imaginations in terms of what future computers might be, and what they might mean to more of the population of the planet. More importantly, perhaps, it’s building a family of open source, Linux-based (and cross platform technology-based) tools, which could ultimately outlive the hardware platform. I have my own doubts about the OLPC itself, but the ideas for open sound making are about more than just that hardware. (For instance, just testing Processing, Arduino and Java on this kind of mobile platform can improve that software.)

The sample library is only part of the story; software tools is another part. Powered by Csound, the OLPC team wants to put sound synthesis and music production in the hands of kids — we’re talking serious digital synthesis here, not just GarageBand-style looping. That goal could ultimately go well beyond just the OLPC.

Csound is a free and open source development tool for sound design, synthesis, and signal processing, with a lineage that goes back to original developer Barry Vercoe and in turn descended from the first digital synthesis tools created by Max Mathews. It is the audio/music development system for the OLPC project, with integration with Python (though I’ve heard we should also see additional Java development).

Those geeky details aside, you’ll see in many of the reviews of the OLPC writers mentioning unusual and fun music toys. Those journalists are stumbling upon some of the projects below, and the process is just getting started.

Jacob had shared some brief looks at what he’s working on on his OLPC, but here’s the full overview from Dr. Boulanger, because there’s quite a lot happening:

It’s Flash 909, and Amiga Flash.

Code wizard Andre Michelle has already made a name hacking audio capabilities into Adobe Flash and ActionScript 3. We got to see his work in the form of real-time audio effects processing in the GarageBand-like online sample-and-compose interface for Splice:

Interview: How Splice.com Has Taken Music Real Audio Processing to the Web

Well, there’s more, well into the “Things Adobe Wouldn’t Normally Expect People to Do With Flash” category. There’s 8BitBoy (warning: link autoplays music), a Flash-based player for Amiga MOD tracker tunes. There’s a 909 emulation (cutely named FL-909). There’s open ActionScript 3 source called popforge [@ Google Code] with all the Flash-hacking tricks needed to do audio.

Now, the most tantalizing bit yet: Andre has a new music environment coming, and to tease its arrival, he’s put up a little application with Roland emulations and stompboxes — and it’s all part of the Rich Internet Application of the Future:

We like to push the outer envelope of music technology geekdom. But what if you’re also an obsessed web geek? Then you start playing the data encoded in a Website design like nytimes.com as a musical instrument.

A new patching environment called Lily, inspired by tools like Max/MSP, works its magic using JavaScript inside a browser. So turning your browser into a music tool becomes more practical. And Lily supports the network-savvy OpenSoundControl (motto: “it’s not MIDI!”), so you can hook up an OSC controller like the Monome and jam with Firefox and the New York Times.

Finally found a use for the NY Times from Bill Orcutt on Vimeo.

How does it work? Get prepared for some Web technospeak, kids!

When the patch starts, the browser enters a DOM inspection mode and mousing over a DOM element highlights the node. Clicking on a node writes the element’s data (its innerHTML value if it’s a text element or the binary data if it’s an image) as a sound file and the file is then loaded in a quicktime player in the patch. The sounds can then be triggered using OSC messages.

Hey, where’d everyone go?

If DOM models don’t exactly get your pulse racing, here’s a strange and elegant physics-based sequencer hooked up to Reaktor. Fans of Processing, that environment is also capable of similar stuff; this is even modeled on the Processing-compatible traer physics library.

SVG Midi Sequencer from Bill Orcutt on Vimeo.

Ready to get going with this yourself? Lily is now in public beta, ready to run for free on Mac, Windows, or Linux. Browser not included.

Lily Public Beta 1

Gobs more examples and documentation on the blog

Previously: Browser Beatboxes and the Rebirth of Max-Like Patching

Wormhole2 is a powerful, cross-platform (Windows + Mac) VST plug-in capable of transmitting audio between computers over networks. It allows effects chain routing between networked computers, boasts low-latency performance on LANs, and even works over WiFi or Firewire. But Wormhole2’s niche audience kept it from catching on more widely, and we hadn’t heard much from it lately, leaving some users worried Wormhole had fallen into a black hole.

plasq, the wonderful people who brought us Skitch and Comic Life, have been giving their audio tools new lives rather than orphaning them. We’ve already seen plasq’s live performance-savvy instrument and effects host Rax show up as an Audiofile Engineering product, and AE in turn recently promised in comments that great things were coming for Rax.

Now, we have some great news for Wormhole2: it’s gone open source:

Wormhole2 @ Google Code

Product Page and Features (still up at press time)

Discussion at plasq.com Forum

End users can just download AU (Mac) and VST (Windows) binaries, plus a PDF manual. It’s even a Universal Binary for Intel Macs.

Developers: because VST isn’t an open-source format, you have to download Steinberg’s VST SDK to use it, but plasq will actually go the trouble of sending you the files once you agree to Steinberg’s license agreement. (AU isn’t either, but Apple ships all the developer tools you need with the OS.)

I’m really hopeful someone will build something cool with this. You’ll need something else to route MIDI (though the Mac does that over networks out of the box, cough, Windows). But there are powerful audio-over-network options here which would be hard to work out on your own. It’s unclear how useful Wormhole2 will be to the existing, open source JACK audio project, which is also capable of routing audio between apps and (via netjack) networked computers. JACK uses a client/server model as opposed to Wormhole’s plug-in approach. But for end users, having both tools available free is a very good thing, and the price tag is an extra incentive to be brave and see if these tools can help power up your rig.