Max for Live Beta is Here; Final Version November 23

Max For Live Sneak Peak from max4live on Vimeo.

Suddenly, I have an image of American Ableton hackers patching on their MacBook over Thanksgiving turkey.

After a long, long wait, a public beta of Max for Live is available. The software incorporates the full version of Max/MSP/Jitter – complete with visual output, video processing, and 3D capabilities – with the Live host. Max patches operate with all their usual capabilities as devices inside Live. User interface elements are available to give Max patches conventional Ableton device interfaces, and there are even pre-built elements for useful functions like frequency displays and MIDI patterns. Via the Live API, Max for Live patches are also able to control most elements of the Live interface.

Because of Max’s networking capabilities, Max for Live devices can also be used to route OpenSoundControl data into Live. That isn’t necessarily with the same ease as you might route MIDI, and there’s still no native support in the Live interface, but it is a step forward.

Our friend Michael at max4live.info has been busy documenting the new software. His overview video is at top, and for OSC coverage, see his tutorial [part 1 | part 2].

Updated: Pricing has now been announced.
Max for Live is not included with Live 8 or even (perhaps surprisingly) Live Suite. It will be a US$299 / EUR249 download, available separately, on top of the cost of Live 8 or Live Suite 8. If you already own Max, you’ll have a set of crossgrades available:
1. You own Live. You can add Max for Live for US$99.
2. You don’t own Live, and want just Live. You can get that and Max for Live for US$449.
3. You don’t own Live, and want the whole Suite. Suite plus Max for Live crossgrade, US$699.

Total cost:
Max owners without Live: US$449-699
Live owners without Max: US$299 + cost of the upgrade to Live 8
Max + Live owners: US$99 + cost of the upgrade to Live 8

I think this could arguably be worth the investment, but given the discontinuation of support for developing VST, RTAS, and AU plug-ins in Max – a feature that was formerly free – I expect some resistance. Also, as previously announced, there is no known Max for Live “runtime,” meaning Max patch developers don’t really have a distribution outlet for work made in Max for Live, other than other Max for Live users.

Sign up for the public beta on Ableton’s site, and you’ll be able to grab the downloads (details below). You must be an Ableton Live 8 owner, though you don’t need to own Max 5:
http://www.ableton.com/maxforlive/beta

read more

Eigenharp Details: MIDI, High-Res Protocol, and Open Source Plans for the Space Bassoon

The Pico model may lack the impressive array of keys on the flagship Alpha, but when it ships next month it’ll cost well under a grand. And even the Pico promises high-resolution touch, velocity-sensitive keys that you can “bend” as well as press, and high-resolution breath input.

The “space bassoon” Eigenharp seems to have landed from another planet. Today, I’ve got good news: it’s bringing alien gifts with it. By next year, both the software and the high-performance protocol the instrument uses will be open source. Taken together with other advancements in the open source community and with protocols like OSC, that could mean we’re at the vanguard of a golden age for more open, more intelligent, more expressive digital instruments.

Genuinely new music controllers made available commercially don’t come along very often. So this week’s news of a strange but wonderful-looking instrument shaped like a bassoon with customizable key controls turned many heads. With high-resolution, high-frequency data and reliance on the computer for everything from sound generation to mapping the keys to different tunings, the computer connection matters. Eigenharp’s chairman, John Lambert, sets the record straight for CDM on the software, the way it talks to your computer and other gear, and how open the tools and protocol will be.

I’ll be talking more with John next week, but I want to bring you this news now. Part of blogging means that you don’t hold back – you share that first reaction and then learn more. I’m pleased to say I was dead wrong on the Eigenharp. What looked on the spec sheet like MIDI-only communication and proprietary software turns out to be just the opposite. Sometimes, being wrong is great. Here are all the details:

read more

Wild Musical Inventions from Berlin Hackday

iloveacid

Nodes of musical events, arrayed onto virtual tracks, in Jakob Penca’s iLoveAcid sequencer.

Take a weekend, and make something: that’s the challenge behind the Music Hack Day, which joins a growing phenomenon of events built around collective creation. (CDM held its own tangible interface hackday online, which I definitely hope to follow up soon!) Initiated by Dave Haynes of music sharing service Soundcloud, the Hack Day has already hit London. Many of the events were Web app-based and focused on consumption rather than creation of music, but we also saw a chordal synth plug-in and beer bottle percussion instrument.

The Berlin Hack Day, which wound up earlier today, offers still more projects focused on the creation side of music hacking. Having Ableton and Native Instruments as sponsors likely helped the mood. And as you’d expect from one of the world capitals of creative hacking, Berliners don’t disappoint.

Among the projects: a beautiful, elegant 3D sequencer, a fun bird-and-sky multitouch soundmaker with multitouch trackpad input, and a robotic xylophone controlled by monome. Someone even worked out a way to turn NI’s Maschine into a rhythm game, complete with Street Fighter sounds.

I’ve got some of my favorite projects here, but see also an eyewitness report (in English and Italian) at Audio News Room:
Just back from Music Hack Day Berlin
… and keep your eye on the wiki:
Berlin Hack Submissions

xylobot run by monome from robb on Vimeo.

Monomist Rob Böhnke and Ramsey Arnaoot created one of my favorite hackday projects so far: a monome-controlled robotic xylophone. The ingredients: one monome grid controller, one Java application for step sequencing to the output, one Arduino open source controller board, and one terrific xylophone “robot” made of an array of servos that strike the bars of the instrument. Oh, and some hot glue and wood, of course.

read more

Updated Lemur Touchscreen Display Coming

It’s still anyone’s guess exactly what fruit parent technology maker Stantum may soon ship, but the JazzMutant Lemur touchscreen is getting a component update soon. Nat Lecaude points to a quiet MySpace post from JazzMutant with the details of a coming manufacturing change.

“…the next batch of Lemur will feature the latest generation of our multi-touch technology: better optical performances, higher precision, greater accuracy and responsiveness. It will be clearer and have brighter colors. We plan on launching the new Lemur in early October, and of course we will keep you updated as we get closer to launch date. We once again thank you for your patience, and look forward to sharing the excitement early October!”

It’s actually quite remarkable to me that JazzMutant remains alone in this market – and with Stantum focused on the mass market, that could be the case in the future, too. The issue is that doing multi-touch well still costs some money. There are basic implementations on computers that are cheaper, but that restricts you to a few computer models, because slapping multitouch overlays on displays remains pricey. So HP can get a few computers to the mass market, but not without cutting some corners and not even on that company’s full range. The iPhone has brilliant multi-touch control, but a mobile form factor makes this much easier.

I’ve got some videos demonstrating what’s possible with the Lemur coming soon, as well as some notes on how the software has evolved since I first saw it in its initial release. Even if you don’t want or can’t afford a Lemur, it’s a fascinating demonstration of interaction design and OSC, with lessons (inspiring and tough alike) for other interfaces.

Photo by Rainer Knobloch for CDM.

Music Tech Pronunciation Guide

Pronunciation of some common music tech terms has been a source of debate. Generally, though, there’s only one right answer. I had hoped to kick off a pronunciation guide yesterday or today, but now I really can’t resist – not with none other than Tegan & Sara getting together to debate the right way to say Moog.

Don’t get me wrong. I love cows, and the sound “moo.” I suggest if you have something you want to name Moo, you should, like your own MooVerb max patch or something. However, here goes, a few of my favorites:

Moog: Rhymes with “brogue” or “rogue,” not the sound a cow makes. Don’t say “Moooooog” unless you want to get funny looks from synth nerds, or if you’re teaching synthesis to livestock in a dairy.

Monome: The community-based, (partly, at least) open-source controller rhymes with “MA gnome,” not the Spanish-sounding “Ma gnome ME.” You should not be able to use it in a couplet with paper mache. Get it? Two syllables. Sure, this pronunciation varies, but the two-syllable version is what the device’s co-creators call it.

OSC: Pronounce the letters of the open communications protocol, as in “O.S.C. / oh ess see”, not “osk” – though that would have been kind of cool. Think, “Rah, rah, rah, Give me an O! Give me an S! Give me a C! What’s that spell? Better than MIDI! Time-based messages, higher resolution, transport-independent high-speed networked communication with auto-discovery, gooooooooooOOOOO O.S.C.!” (People sometimes say this site is geeky. I have no idea what gives them that impression.)

And for now, O.S.C. stands for Open Sound Control, even though in one spot on the JazzMutant website it’s called “Open-Source Control.” Just get ready for this to change – because OSC really isn’t specific to sound, it may need a new name, like Open System Control. (A recent paper suggests dropping the “sound” in the name.)

MIDI: Rhymes with G. Gordon Liddy, or P. Diddy, or Tweetiebird saying “Piddy.” And, actually, it occurs to me I’ve never heard anyone mispronounce this. Fascinating – an acronym that’s actually intuitive. Oh, but “C.C.” stands for “Control Change,” NOT “continuous controllers” — look at the CC specs; most aren’t continuous. There. I got to be anal about something anyway. Updated: consensus is actually that “mee-dee” is a mispronunciation for native-English speakers, but likely makes more since than “mi-dee” in other languages — particularly if you speak French. So, in other words, it’s an acronym, and makes the most sense to pronounce in the natural way you would in your native tongue. (For English speakers, who knows what vowel sound is appropriate given how screwy our language is, but the creators of MIDI all say middy.)

Maschine: Native Instruments’ drum machine software and controller is German-engineered, so say “muh SHEEN uh,” three syllables, as if you grew up in Berlin. Now, granted, Maschine’s own promotional videos — outsourced to the US — anglicize this to “machine” / “muh SHEEN”, but the engineers and product folks who built the thing use the German pronunciation and think you should, too. And, anyway, it sounds cooler, just as I have to admit a currywurst is tastier than a Nathan’s dog.

I’m sure this is only a small selection of potential mispronunciations. Other candidates? We’ll have to release a full pronunciation guide soon.