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

At the bottom of the page, you’ll have a direct link to download Live 8.1 (the official current build of Live is 8.0.9 otherwise), and a link to Cycling’s site to download Max. (Note: the Max link worked this morning, then promptly disappeared, so it’s possible they’re uploading an updated build is now back up.)

There are full instructions there. I was able to simply click a button and become a beta tester; hopefully you have the same experience. You’ll need to install two pieces of software, both Ableton Live 8.1 on the Live side and Max 5.1.

For the Python-based Live API, and the MIDI and OSC interfaces based on it, this should also come as good news. Live 8.1 should theoretically represent a more stable, feature-complete, fully documented version of the Live API under the hood in Live. That means even without Max for Live, it may be possible to, say, route an OSC input into Live as easily as a MIDI control surface.

If you’d like to join in with other people working on hacking Ableton Live and ask questions, try out our Noisepages group, which should now be functioning properly with a forum, wire, and networking features. More to come with this, with Max for Live, with OSC, with other tools, with… yeah, I’m glad I own a coffee maker.

http://noisepages.com/groups/ableton-hackers

The beauty of using touch for controllers is flexibility. Sure, you give up tactile feedback – but you can also quickly make your own layouts, make touch controllers an ideal complement to your existing hardware gear (the stuff with physical knobs and faders and pads).

For that reason, we’re all eagerly anticipating an upcoming version of the awesome OSC-based iPhone/iPod touch controller, TouchOSC.

http://hexler.net/software/touchosc

The included layouts are already fantastic, with rotaries and virtual buttons and multi-faders and toggles and X/Y pads. But custom control would be even better. Creator hexler writes CDM with the latest:

The long-awaited update to TouchOSC that will allow for custom layouts has just been submitted for review to Apple,
so I hope that as soon as next week it will be available as a free update to all users on the App Store.

Together with this release (1.3) there will be a free editor application to visually design and upload layouts to the device. You can take a look at the last beta version I published if you want, there’s both Windows and OS X versions available, but I will also prepare a Linux version as soon as possible, of course without the new version of TouchOSC this is but a preview of things to come:

http://dev.hexler.net/touchosc/touchosc-editor-0.7-osx.zip
http://dev.hexler.net/touchosc/touchosc-editor-0.7-win32.zip
http://dev.hexler.net/touchosc/touchosc-default-layouts.zip

And nicely enough, the editor is built in cross-platform Java, which I think makes a whole lot of sense. (Go Java, Python, etc., rather than getting stuck in hard-to-port platform-specific stuff like Cocoa.)

Thanks, hexler! I don’t have a video of the new features yet, so instead here’s a nice novelty – the beginnings of a creation using the free SuperCollider (which runs OSC natively) in combination with TouchOSC to make a custom step sequencer. Should fuel other ideas, too:

Fritzcrate Project / lusidLearn Early Demo from Michael Schieben on Vimeo.

Knobs and faders can be rigid. Fancy multitouch devices can be expensive. But for the cost of a webcam and some spare materials, you can build computer interfaces with objects around the house, thanks to the power of open source software.

In just one day, a group of artists in the CDM community, from Austria and Germany to New York to Australia, got quite a lot working with tangible interfaces. At top, Michael Schieben and Christophe Stoll experimented with using soda bottles to control software like Future Audio Workshop’s lovely Circle. (Ableton Live works, too – as does any MIDI software.) As Precious Forever, these guys are responsible for some of the best UIs in music software, from FAW to recent Native Instruments designs, so it’s lovely to see them experimenting with this idea.

As you add more people to the mix, you get ideas you might otherwise never have imagined, from a game involving blocks of the Tokyo skyline to an interface built into floor toms.

We also got a lot of real-world data on what works, what needs work, and what causes trouble for beginners, which we’ll be documenting. (Adam and Martin from the Trackmate and reacTIVision projects, respectively, were both tuned in to see progress and provided lots of help – and are also collecting that data to improve their own documentation and libraries.) More commentary on all these side benefits, as well as a discussion with visitors from Argentina on the scene around the world, at Create Digital Motion.

Musical Resources

We also got some really helpful tips for working with the free, powerful, tri-platform synthesis tool SuperCollider:
Charles Martin wrote up an easy SC test script for receiving Trackmate messages (and also had the clever idea of using a floor tom)

And for connecting Trackmate to MIDI and working with Processing, lots of tips are available on Michael Schieben’s noisepages blog:
http://fritzcrate.noisepages.com/

Get Involved

More documentation:
Tangible Interface Hackday: The Projects (So Far)
http://hackday.noisepages.com/

http://trackmate.sourceforge.net/
http://reactivision.sourceforge.net/

So, what’s next? You can join discussion and brainstorming for how to proceed, and how to get in on another hackday (formal or ongoing), even if you missed the first. Stop by the Tangible and Multi-Touch Interface group on noisepages:
Tangible + Multi-Touch noisepages Group

Our noisepages community is still in “alpha” state, but it’s usable – we’ve just fixed avatar uploading, which was the biggest problem. We’ll have more features, functionality, and improvements down the line, as well as more extensive documentation for how to get started. But if you’re a bleeding edge sort of person, join up free and give us some advice on what you’d like out of it.

I look forward to more work on these projects. Stay tuned for more, including some additional documentation (I’m developing some stuff around my own project).

Automap on other devices – and an iPhone as a remote control for your Live set? Our friend Ben Rogerson at MusicRadar have caught up with the chaps at Novation at a London trade show to have a look at Automap for iPhone. This app hasn’t yet hit the App Store yet – Hispasonic and the Ableton Forums got the jump on the story last month. But it looks appealing.

It seems to auto-detect the computer to which it’s connecting – as it should, folks, look up Zeroconf. (implemented on iPhone as “Bonjour”) And you can learn in both directions – so you can interactively choose parameters on the iPhone and decide what you want to control. It also sends MIDI to Live for clip triggering, though you’ll notice that some features on the APC40, like clip status and the ability to move through blocks of clips, aren’t possible here. Because Automap wraps around VST and AU automation parameters, you also get high-resolution control of plug-in parameters.

This should also open up possibilities for other Automap-supported apps, not just Live; I’ll be able to test this once the app comes out. No official word on availability or pricing other than soon and cheap. Before people start complaining about the tiny iPhone screen — yes, absolutely. But there’s a nice blank spot on the Novation controllers on which you could put your iPhone or iPod touch. Think about it: you can add an intelligent multi-touchscreen to your existing hardware, use your conventional gear for physical control, but keep the Apple gadgetry as an additional remote (now fairly cheap with no contract for iPod touch). You can even wander around the room during sound check while still controlling your set.

Update: I should note, as I just got asked on Twitter, most Wi-Fi adapters allow you to create your own Wi-Fi network. So you don’t need Wi-Fi in a venue. You’d just create your own network on your PC or Mac laptop, and connect via that – the iPhone and iPod touch both support connecting to these networks. (Note that not all devices do: the Android-powered TMobile G1, for instance, has a chip that apparently doesn’t support them, and I have an 802.11b/g USB adapter that won’t create them. But mostly, this is an easy matter.)

Cool as this is, and elegant as the work Novation appears to have done, I can’t help but notice this is still something of a kludge. The iPhone communicates natively over TCP/IP with the computer. That’s what this app is using – but then it needs a Rosetta Stone and another set of software on the computer just to untangle the archaic protocols music software uses (plug-in automation, MIDI, and more oddness heaped atop of MIDI). There’s absolutely no reason that music software couldn’t be intelligent enough to support networking protocols so that all software and devices can easily communicate. That wouldn’t put Novation out of business, either – on the contrary, it would allow them to do their jobs and this very app could be more productive. Instead of MIDI CC numbers, imagine if you could refer to clips by scene and position number, or even by clip name. Imagine if the iPhone displayed clip parameters and changed when clips were launched. Imagine no more drivers or software to install: someone who bought Novation hardware with OSC support could bring it to a friend’s place and work on a session without that friend installing Automap software.

(singing) You may say I’m a dreamer, but … (sorry, cough) actually this is all possible right now.

I’m all for solutions that work, and Automap (and M-Audio’s HyperControl) both have great capabilities now. But OpenSoundControl is also something you can implement now (provided hosts like Live will support it), and we’ll be talking more about what it can do over the summer to make it more practical and less abstract.

So, you’ve been looking at that Akai APC40. And it’s appealing. It’s got lots of lights and a huge array of buttons for triggering samples or video or what have you, and plenty of knobs and faders.

Now the APC40 has some serious “indie” competition, though, in the form of Livid’s Ohm64. Let’s compare:

APC40:

• Proprietary connection to Ableton Live
• A proprietary handshake that ensures only a real APC is being used with Live
• Fixed MIDI assignments – no MIDI assignment editor
• MIDI only
• No MIDI out jacks, so you can’t use it with outboard gear
• No bus power
• 40 buttons
• Made in some factory somewhere we’ve never seen

Livid Ohm64:

• Open source editor, partially open source firmware, open source patches to connect to whatever you want
• Custom MIDI assignments, for use with whatever you want
• MIDI for now, but the chipset supports open source solutions for OpenSoundControl (OSC) in the near future – and even DMX (for lighting) is a possibility
• USB and standard MIDI jacks so you can sequence outboard gear
• Bus power
• 64 trigger buttons in a more logical 8×8 array
• “Made in the USA by humans” – with a beautifully-crafted body
• Free Cell DNA video software included

Both the APC and Ohm are class-compliant, so at least neither needs drivers to work over USB for MIDI on Mac, Windows, and Linux.

Sure, the APC is plug-and-play with Live. But just as lots of non-programmers use open source browsers like Firefox, the whole point is that the Ohm could wind up being more plug and play with more tools thanks to its more open approach.

Most important is the programmability of the Ohm64. You can make your own custom light interactions – or, if you’re not into that sort of programming, count on what may be a growing community of open source musicians and visualists doing it for you.

In fact, Livid is so committed to customization that in addition to the natural, blue, and red finishes, you can order it unfinished and stain or paint it whatever color you like.

The Ohm64 is also priced at just US$599, meaning it doesn’t cost much more than the APC40. And with future OSC support, hardware MIDI support, bus power so you don’t have to carry a dongle, fully programmable visual feedback and assignments, and open source editing software, the APC has some real explaining to do about what its long-term payoff may be.

The editor is currently built in Max/MSP with some interesting possibilities coming up in Max for Live, but I’m also interested in working on some editing and performance tools in fully open source environments. Stay tuned.

Now, mind, this isn’t a review – I’ll get my hands on the Ohm64 next week here in New York, and I’ve only had a brief encounter with the APC. But if I were a betting man, I have to say, the contest here isn’t looking like it’s in the APC’s favor.

Available now.

Livid Ohm64

http://www.lividindustry.com/culture/ blog with more videos

Updated: I should note, one issue is definitely that, in order to maintain bus power, there are some compromises. You don’t get quite as much interaction from the lights as you do on the Akai APC – I do like the APC’s lovely LED rings around its encoders. You can interactively dim the lights on the knobs on the Ohm, though, which would work nearly as well. More once I get my hands on the Ohm, and theoretically, I should have an APC for testing at some point, too, assuming I didn’t just make Akai angry. (Uh…. competition is good. Blogs are all about opinions. Don’t hurt me.)

By the way, if you aren’t convinced and think you can do better, Livid is also distributing the brains of this device – the MIDIDIY – so you can build your own creations. Other such solutions exist, but the MIDIDIY is distinguished in its ability to support a lot more contacts for doing this sort of more complex device.

http://www.lividinstruments.com/hardware_mididiy.php

Ed.: Plogue Bidule is an unusual animal: this affordable patching tool resists conventional ways of doing things, down to its hatred of the number “1.0.” But Plogue has an underground following inside the already-underground world of modular patching tools for creative music. I’ve invited Primus Luta, aka David Dobson, to give us insight into this tool – including a new release that will be big news to the people who rely on Plogue to make their productions and live performances tick. -PK

Today if you go over to the Plogue site you will see the announcement for the latest release of Plogue Bidule. In addition to a number of bug fixes, there are some amazing updates in this latest release. On the eye candy side of things, Bidule finally gets a waveform viewer module — the WaveViewer shown in the image above. There’s also a new Audio Buffer module for visualizing waveforms. These are great additions to the Bidule arsenal and also a good indication of more visual goodness to come.

In its ever-growing commitment to fully support OSC [OpenSoundControl], a new tool has been added for monitoring OSC communication. The OSC Monitor behaves like many third-party options, showing not only the OSC messages sent by and to Bidule, but also picking up any additional messages being transmitted, as well. Ed.: A general-purpose monitoring tool sounds like a great idea! A great resource when trying to get multiple OSC-enabled devices or pieces of software communicating with each other.

Perhaps the biggest update of all in this version is the introduction of Multi-Core Processing, supporting up to 8 Cores. Previous versions of Bidule only allowed for processing on two cores, but now the MP Assign command lets you not only utilize up to 8 cores, but also select which processors you’d like to use. As a bonus, there’s also a new DSP Adapter function which allows you to run a limited set of modules at a buffer size of 1 sample.

All an all, it is a very welcome update. As with all publicly-released versions, this one comes with a time-sensitive trial period, so that new users can explore Bidule over the next three months without purchase. Simply make your way to the Plogue site to download this version today. If you’re looking for encouragement, also starting today, I’ve launched the first tutorial in a series which will be utilizing instruments that I’ve developed in Bidule for the Heads Project as examples. The series will be starting from the most basic concepts and progressing toward the more complex over the next months. If you’ve ever wanted to get your feet wet in Bidule now would be the time.

Lastly, I had the extreme pleasure of having a conversation with Sebastien Beaulieu, co-founder and lead Bidule developer over at Plogue. He gave me some great insight into the origins of Bidule, the business and development model of Plogue, and some ideas of what we can expect in the future. You can read the full interview here on CDM.

Want to interact with your computer musically using physical objects and other fancy-schmancy, science-fiction-y interfaces? Don’t want to rely on Microsoft or wait until 2019? You’re in luck. It’s like Christmas for DIYers and interactive futurists.

Enter LusidOSC, a set of protocols, libraries, and useful code, and Trackmate, a clever and cheap-to-build system for tangible interfaces. Together, you’ve just got a bunch of tools to help you start playing with blocks — erm, experiencing new spatial interfaces.

• LusidOSC, the library maps “spatial input devices” – really, any tangible devices or sensors in the real world – to applications, like live music or live visuals. It uses the network-savvy OpenSoundControl protocol. The library is available now for Processing, with Java, Python, Flash, and C++ in the works.
• LusidOSC, the apps/code: a set of Processing utilities to get you started includes a basic example app, command launcher, playlist mixer, and a MIDI sequencer. You can build on these for your own Processing apps.
• Your own input device: Tags? Sensors? Markers? Regions? Fingertips? If it’s in physical space, you can map it via LusidOSC. Or, if you want a place to start, try:
• Trackmate: A project of MIT’s Tangible Media Group, Trackmate lets you affix tags to any objects you want and use them as an interface.

LusidOSC is just the protocol; it’s physical applications like Trackmate that get really interesting. In these economically-challenged times, Trackmate gives you tangible interfaces for next to nothing. All you need is a computer (Mac, Windows, or Linux), and a camera (even a webcam will do). Print out randomly-generated tags in the free and open source software, stick them on stuff you want to use, and go to town.

You can make your own Trackmate surfaces out of hardwood or plexiglass for as little as $40 in parts. There’s even a Processing-based simulator app so you can experiment without the physical objects. (Good for troubleshooting on the bus or plane, I imagine.)

Trackmate is just one project, though; LusidOSC promises to support other interface ideas, too.

LusidOSC at Sourceforge, the work of “many research institutions and companies.” (Which, I wonder?)
Trackmate at Sourceforge, a project of the MIT Media Lab Tangible Media Group

Alternatives: TUIO, the protocol used in the Bjork-endorsed Reactable project marches forward, as well. And as both projects are open source, there could be some cross-pollination. I hear a revised TUIO is coming, and in the meantime, LusidOSC acts as a gateway to TUIO.

Ready for some musical genetic engineering?

Much of the sound of electronic music today grows out of the use – and abuse – of specific designs. The electronica beats bred in discos and techno, Detroit and Berlin have a direct lineage to analog step sequencers and the rigid precision of Roland’s early electronic devices. These designs create limitations to embrace and to oppose – just as music notation or theoretical convention did for composers for centuries.

Okay, that’s a lofty way to put it — the question here is, how do you re-engineer music, even an ounce at a time? If you’re a composer a few centuries ago, you make subtle changes to your craft, working inside a convention, and write that down. (Just as with electronic music, there is a layer of separation – only then, it was a piece of paper.) If you’re an electronic artist today, you can likewise change what you’re able to control, and how, playing live. The differences at first may be imperceptible, but just like learning an instrument, the long-term payoff can be huge.

I asked for examples of what people are doing with the Lemur multi-touch touchscreen controller and its recently updated V2 software. This isn’t just about the Lemur – it illustrates what’s possible when the musical device and the controller can flow freely out of a musician’s imagination. That could apply to hardware or software designs well beyond the Lemur.

Mikael Björk of Sweden responded with a terrific example, a “dynamic” sequencer available to all Lemur users via JazzMutant. The open-ended screen layout of the Lemur has allowed the creator to provide all kinds of unusual control over morphing beats, with your fingertips manipulating simulated physics as beats twist around you. It’s not just electronica and sampling and DJing, either – he also has an incredible clip working with a very talented vocalist. It sounds markedly different from the more conventional, Loopstation-style loop performance.

DyNAmic is a sophisticated step sequencer managed by a Max patch, and tightly connected to a Live rack. The Live rack consisting of two Simpler devices containing basic sine waves for low and high percussions, a Simpler containing noise for your hi-hats, and one containing a square wave for your bass sounds. In addition, each Simpler feeds an Autofilter and Redux for effects modulation, all of this being controlled from your Lemur of course.

Template created by Mikaël Björk aka Lo-Fi Massahkah.
http://www.lofimassahkah.net

What he says in a separate post on his blog sums up a lot of what I have to say about sequencers and samplers, too:

Sequencing. Sequencing. Sequencing.

You’d think that that’s all I’m about. Perhaps. Sequencers are fun when you can’t really play an instrument. They might also be fun if you CAN play an instrument. I like my new sequencer – and I hope you’ll like it too.

See: Hip to be Square

The upcoming release of Max for Live should mean that Live can work more seamlessly with the Lemur and the control configuration — more on that soon. But this doesn’t have to even be about Live; I imagine we’ll see other setups moving this direction, too.

And having an open music controller means that, pricey as the Lemur is, you get added value from this kind of artist contribution. (See also: monome, on CDM or the monome project site.) You can use this sequencer layout as is — use it in a different way musically — or modify it, or create your own. The whole patch and extensive how-tos are right on JazzMutant’s site:

JazzMutant Workshop: DyNAmic

So, cool as that is, I’m sure many of you were expecting the glitchy beat modulations that result. Here’s a related project that moves in a very different direction.

Schack & Wetterberg Live looping from Lo-Fi Massahkah on Vimeo.

Esben Schack and Andreas Wetterberg doing a set on Café Zusammen in Copenhagen. Esben on vocals and guitar, Andreas on Live (looping) and Lemur.

And for more of this stuff, you can follow the Vimeo feed:
http://www.vimeo.com/user454089

Not much to add – when the tech is working right, your traditional musicianship (if you’re lucky enough to have it) can come out. And while the occasional touchscreen tap may not seem as dynamic by comparison, I think the way to think of the Lemur is as a compositional device – the vocalist is the real “player,” in a conventional sense, whereas the Lemur is acting as a composer — remixer, however you want to think of it — in real-time.

My respect for the Lemur has really grown as it has matured; the folks at JazzMutant have addressed some of my design complaints. Its cost is, like most boutique instruments that aren’t made in huge quantities, a premium – no argument there. Likewise, you can sacrifice some of that unique design and get a cheap commodity device. In the end, I think there’s a value in both. To me, the more important thing is what people are doing musically. So I’ll be sure to follow both – and hopefully share some how-to people for our Lemur owners and DIY touchscreen users (or other controllers) alike. Even if you just have a box with a few knobs on it, it is possible to move in some new directions.

Got more examples? We’d love to see them.

Before the iPhone, before HP computers and Windows 7 touch features and Apple trackpad gestures, the Jazz Mutant Lemur multi-touch interface was ahead of its time. Today, it’s still unique, in that it’s one of the few commercially-available devices to support OpenSoundControl, it’s a luxuriously-large multi-touch screen, and it has exceptional precision and low latency with its tracking. Of course, it has also been subject to two primary complaints: one, that the software options for creating onscreen interfaces is two simple, and two, that it costs too much.

Well, the Lemur and its more conventional DAW-controlling Dexter sibling address each of those. The Lemur has gotten a significant software upgrade, and both have gotten a steep price cut.

First, Lemur V2 is the biggest set of improvements since the Lemur’s unveiling. New in the upgraded firmware:

• Tabs for containers
• Breakpoint object for envelopes
• Alias controllers to save memory and (your) time
• Control the mouse cursor or keyboard shortcuts directly (that’s actually a huge deal right there)
• Pinch, rotate, trace gestures
• Pop-up menu object
• New JazzEditor, scripting powers, and instant Ableton Live reactivity – yep, doing stuff even the new Akai APC can’t.

The only bad news is, even with price drops, these devices aren’t cheap, though arguably they can make up for that with longevity. The Dexter has undergone a permanent price drop to a much more competitive US$1519. The Lemur has temporarily dropped to US$1769 for a 60-day promotion. No official word yet on what happens after that offer expires mid-March; stay tuned.

I do think this makes a pretty significant adjustment on value. I’m a big fan of the iPhone/iPod touch apps, but the input area is extremely small; there’s no real comparison.

Lemur V2
Jazz Mutant

And even if you decide not to get a Lemur yourself or can’t afford them, they remain a compelling example of what’s possible in the future of music hardware – and how powerful OSC can be. Look for a hands-on with Lemur V2 and more on OSC in other applications (many completely free) over the coming months.

To close out, here’s a nice, if simple, video demo of a Max/MSP step sequencer controller with the Lemur. What’s lovely about this is that it shows how building both software and hardware interface from the ground up can really give you control over how you’re playing. (Meaning, even if you hate this, you can go create something for youself that’s exactly what you love.)

this is a sequencer i programmed in max using the lemur as a control interface. it sends midi info to whatever program you use. i also forgot to mention that each track can have independent timings, so varitions can span longer than just 1 bar of music.

lemur users can download it off the jazzmutant website. user name – Andrew Graham

Got Lemur creations of your own? We’d love to see them. (I really appreciated seeing the amazing work Bryant Place was doing with LemurV2 and Ableton Live while I was out in LA.)

Many people are asking about what Max for Live can do. That’s a short answer: everything Max/MSP/Jitter can, plus some new stuff to make it work with Ableton Live. It might be better called “Max in Live.” Max for Live has all the objects that Max/MSP and Jitter have – all of them. Right now, I’m gathering a big part of the testing Cycling ‘74 is doing is to try to make anything not work, but so far, it sounds as though everything does. That means Max for Live is an environment for JavaScript and Java. It means you could have Processing sketches, wrapped in Max patches, running in Live.

And it also means you get Jitter, which gives you video playback, processing, and output, plus 3D visuals. You’ll apparently be able to open a window for output, just as in Jitter. So you could have Live sets that trigger video clips, all from within the same tool – or, if that sounds unwieldy on one machine, have a Max patch that communicates with any visual app you like on another machine.

You can’t open Max patches directly, but so long as you own Max 5, you can adapt them to Max for Live into a device.

This also means that whether or not Live 8 supports OSC (it looks as though it doesn’t), you will be able to add that support however you like via Max for Live.

On top of this, you’ll get a collection of new objects that allow Max for Live to use UI elements from Live, interface with the program as Devices, and listen to and control events in the Live interface (like manipulating clips, Devices, warp markers, and whatever else they choose to support). It’s this interface area that’s really new, and that I hope to cover more soon.

The only catch to this is you have to make an investment in software before you get started. If you want to run Max for Live, you need to buy Live 8 and buy Max for Live as an add-on. (Ableton has said it’ll be a separate product, but no word yet on pricing.) If you already own Max 5, you’ll still need to buy Max for Live (though again, no word on discounts). And you will still need to own the standalone Max if you want to use your patches without starting Live.

For more discussion, there’s a thread on the Cycling ‘74 forum:

"Max for Live"?

Jeremy Bernstein of Cycling ‘74 says it best here:

Max for Live is, well, a superset of Max. :) MaxMSPJitter + special features for Live integration
If you want to create a Max Device from a Max patch, you can currently copy and paste the main patcher into an empty device. We’ll probably offer a simple converter at some point, as well.

Right. What he said.

What Might it Mean for Open Source?

You can see that this is good news for:

• Max and patching (a huge boost to DIY software)
• OSC (the open communications protocol, supported – indirectly – for the first time)
• monome (because all those patches can be adapted for Live, which was a popular app to use anyway)

It’s not such fantastic news for the open source world or competing tools, because this is a very proprietary and vendor-specific solution. That’s not a criticism, just an observation – I know fantastic people and friends who are supported by the business model that’s here. But it is worth noting, because I believe healthy software ecosystems incorporate both free and commercial models, and fully open and fully “integrated” (which are sometimes more closed) solutions. There’s no question where this lies. You’ll need the full version of Max to use these patches with even another host – and you’re likely to miss some of the specific solutions here.

That said, I think it’s still an opportunity for open source alternatives to differentiate themselves, and for the two to coexist harmoniously. For starters, open source software will have an easier in when it comes to talking to Live, if there’s a friendly set of Max for Live patches that help communicate with other tools. Also, open source software can be two things this solution is not – lightweight, and free. It’s also an opportunity for open source hardware to interface with this solution (again, see: monome, which I still think has some elegance things like the APC40 lack).

In fact, there’s so much power by the time you put together Live and Max and all your plug-ins (too … much … POWER!!)  that I could see some people finding it refreshing performing with just a simple Processing sketch and turning everything else off.

I might even go so far to say that, by association, Max’s open-source cousin Pd could benefit from this. (I don’t see Pd working in Live any time soon, though.) I do hope that Max patchers release at least some of their work as open source patches for others to use. Flash is a great example of a proprietary tool that has generated fantastic open source tools around it. That means you get Adobe’s support and quality level, but you can still share code – and clearly, the Max world can do some of the same things.

These are ultimately all tools. I’m pretty excited about developments in the open source world, and I believe that most people will use a combination of free and commercial tools. 2009 should be a great year for both, which means you’ll gravitate toward using the right tool for the job, and for your budget. For those who can’t afford all these glitzy new toys, you won’t exactly be suffering. (Next week, I’m going to try to put together a virtual, open-source “NAMM” rounding up some of those developments.)

If you asked me to wish for everything I’d want to come together, for the kinds of things we advocate on CDM, I couldn’t do much better than we’re doing already – and we’re only part of the way through January.