Max 6 in Public Beta; For Home-brewing Music Tools Graphically, Perhaps the Biggest Single Update Yet

Just because a music tool fills your screen with tools and options doesn’t necessarily make it easier to realize your ideas. From the beginning, the appeal of Max – as with other tools that let you roll your own musical tools from a set of pre-built building blocks – has been the blank canvas.

Max 6 would appear to aim to make the gap between your ideas and those tools still narrower, and to make the results more sonically-pleasing. The reveal: it could also change how you work with patches in performance and production. I was surprised when early teasers failed to impress some users, perhaps owing to scant information. Now, Max 6 is available in public beta, and the details are far clearer. Even if Max 5 was the biggest user interface overhaul in many years, Max 6 appears to be the biggest leap in actual functionality.

It’s what I’d describe as a kitchen-sink approach, adding to every aspect of the tool, so there’s almost certain to be some things here you won’t use. What could appeal to new users, though, are I think two major changes.

More visual patching feedback and discoverability. First, building upon what we saw in Max 5, Max’s approach is to provide as much visual information as possible about what you’re doing. It’s probably the polar opposite of what we saw earlier this week in something like the live-coding environment Overtone: Max’s UI is actively involved with you as you patch. There are visual tools for finding the objects you want, then visual feedback to tell you what those objects do, plus an always-visible reference bar and rewritten help. This more-active UI should make Max more accessible to people who like this sort of visual reference as they work. No approach will appeal to everyone – some people will find all that UI a bit more than they like – but Max’s developers appear to be exploiting as much as they can with interactive visual patching.

Multiple patches at once. New objects for filters and data, a 64-bit audio engine, and low-level programming are all well and good. But the change that may more profoundly impact users and workflow is be the way Max 6 handles multiple patches. Max – and by extension Pd – have in the past made each patch operate independently. Sound may stop when you open a patch, and there’s no easy or fully reliable way to use multiple patches at once. (Compare, for example, SuperCollider, which uses a server/client model that lacks this limitation.) That changes with Max 6: you can now operate multiple patches at the same time, mix them together with independent volume, mute, and solo controls, and open and close them without interrupting your audio flow. (At least one reader notes via Twitter that you can open more than one patch at once – I’d just say this makes it better, with more reliable sound and essential mixing capabilities.) Update: since I mentioned Pd, Seppo notes that the pd~ object provides similar functionality in regards to multiple patches and multi-core operation. This has been an ongoing discussion in the libpd group, so I think we’ll revisit that separately!

One upshot of this change: some users have turned to Ableton Live just to host multiple patches. For users whose live performance set involves Ableton, that’s a good thing. But it could be overkill if all you want to do is bring up a few nifty patches and play with them. Now, I think we’ll start to see more people onstage with only Max again. (Check back in a few months to see if I’m right.)

Here’s an overview of what’s new:

• Discoverability: A “wheel” makes the mysterious functions of different objects immediately visible; Object Explorer makes them easier to find, and new help and reference sidebar keep documentation close at hand.

• 64-bit audio engine

• Open multiple patches, solo and mute them, open and close them without stopping audio, mix audio between them with independent volume, and take advantage of multiple processors with multiple patches.

• Low level building blocks: You don’t get new synth objects, but you could build them yourself. New low-level data-crunching goodness work with MSP audio, Jitter Matrix, and OpenGL textures

• More JavaScript: An overhauled JavaScript engine makes JS scripting faster and more flexible, and there’s a proper text editor with syntax highlighting (though, of course, you may still prefer your own).

• New visuals: Vector graphics and “HTML5 Canvas-like” UI scripting (though to me it’s a shame this isn’t just the HTML5 Canvas). There are also massively-expanded Jitter powers, but those are best left to our sister site Create Digital Motion.

• Filters: New filter-visualizing tools for audio filter construction and manipulation.

• Dictionary data type and associated objects let you describe information in a more structured way (all kinds of potential here from control to composition)

• Projects now let you organize data, media, and scripts in the manner more associated with conventional development environments

• What about Ableton? No news on that front, but I expect more soon. Max for Live users will at the very least get the advantages above, since Max for Live is really Max inside Live.

Looking over all that Max does, I have to say, I’m really amazed. I wonder if computer musicians ever pause to consider how fortunate we are. Even if this isn’t the tool for you, its availability – compounded by the availability of a range of other tools – is itself worth reflection.

Max is a program that shouldn’t exist, doing a number of things it shouldn’t do, for a user base that shouldn’t exist, doing things they shouldn’t be doing.

It doesn’t make sense that you could maintain a commercial project for this kind of audience, that you’d wind up with something this mature and powerful that had a continuous lineage stretching back to the 1980s. It doesn’t make sense that musicians would embrace such a tool and produce invention. The only explanation is sheer love.

Then, even as Max reaches new heights, some of the alternatives you have for making your own music tools are simultaneously growing by leaps and bounds. They provide very different approaches to music making (compare Overtone and SuperCollider, or Pd and libpd, or AudioMulch, or new Web audio tools). There really aren’t many fields that have this kind of choice, free and commercial, in their medium. In science and engineering, there’s private and public funding, producing some amazing tools but nothing with this kind of meeting of power and accesibility. There’s just something about music.

The fact that Cycling ‘74 can maintain a business model – just as open source projects maintain volunteer contributions – is a testament to sheer passion and love for music, and a commitment to perpetually re-imagining how that music is made from an atomic level up. There was a wonderful piece on C creator and UNIX co-creator Dennis Ritchie, whom I remembered yesterday, that observed that what he did was to do what others said couldn’t be done. From Max itself to what people make with it, I think that fits nicely.

So, have a look at the public beta, and let us know what you think. The release of Max 6 has caused more people to ask what this means for Pd and other tools, or even whether to patch things from scratch at all, but I’ll leave that question to a bit later. (I do have my own opinion about which tool fits which circumstance and user, but that’s best left to a separate discussion.) For now, you can try Max yourself and see what the fuss is about. If it doesn’t fit your means of music-making, know that you have a wide array of other options – pre-built to low-level code to old-fashioned tape-and-mic approaches, and everything in between. Go out and listen and see what you discover.

http://cycling74.com/downloads/max-6-public-beta/

Montreal-based Damian Taylor, music director and engineer for Björk, is the subject of an epic interview on cycling74.com, spanning music, life in Montreal, working with Björk and what makes her special, and what patching in Max/MSP can mean compositionally and creatively.

Damian has some especially nice reflections on what having an open-ended music environment can mean.

If you’re a musician or composer, Max is an amazing tool that will really open up a completely different way of thinking about music. If you’ve been working on sequencers, looking at time lines, working on tape, or reading off musical scores, then without really realizing it you start looking at music in this very linear way and your brain gets formed into a lot of similar patterns.

But the Max environment provides this whole alternate way of thinking, a whole different flow. Suddenly your own ways of thinking about time and harmony and melodies and everything, expands completely. Music kind of changes shape, you see it from this whole different side. So it’s really, really, really, worth putting in the effort!

It’s a great and well-deserved endorsement for Max, but I think it’s deeper than than any one tool — this way of thinking could also be applied to tools like Pd, AudioMulch (saw a great workshop on that last week), Reaktor, or code-based languages like Csound and SuperCollider. Or, for that matter, I think this notion of thinking in non-linear ways can even be applied to playing your acoustic instrument. It really gets at the heart of how to unlock creativity, I think.

In case you’re afraid of Max or other languages, Damian has some advice there, as well:

If you’ve never done any code or computer language programming before, there are a lot of times where you just have to try to absorb things without really knowing what the hell they are for. And I mean that in the nicest possible way!

I just slowly worked my way through all the tutorials, largely without understanding what the hell I was doing, but just absorbing what was going on, trying to follow every step that was presented. And yeah, it really was a case of locking myself in a room. If there was another noise anywhere, I just couldn’t do it. It took really intense concentration; just trying to absorb what was going on and follow a tutorial from start to finish.

But then at some point I figured I needed to speed things up, so I got in touch with Harvestworks, in New York, who I actually was aware of through an interview on the Cycling ’74 web site. I got tutoring from Matthew Ostrowski — and it was amazing, a complete revelation.

But best of all, for folks using Max/MSP, Damian gives you a leg up, with his nice Woodpecker tool available as a free download for MIDI sequencing.

Woodpecker creates fast 16th note midi sequences from your keyboard input. It’s designed to allow you to bring this very electronic feel into a live ensemble, free of set tempos and click tracks. There are options to allow you to vary the feel of the sequence, play triplets, and explore various arpeggiation styles.

(Nice use of Topspin for a Max patch download! Clever!)

Here’s some music for Damian, as well:
Damian Taylor by MissManagement

damiantaylor.com
bjork.com

And absolutely read the full interview – it even has a nice shot of the Max rig in there:
An Interview with Damian Taylor [cycling74.com]

Full disclosure: this terrific interview is by Marsha Vdovin, who’s also CDM’s business development manager. Thanks for the great work on this, Marsha; I enjoyed reading it, anyway!

Cycling ’74 this week has announced an upcoming new version of its Max software, the DIY patching software for multimedia, from live sound and music to visuals. It looks as though more details will be available in the fall, but we at least get a glimpse of the goals for Max 6, as well as a new pricing scheme, and more information is likely at the NYC Expo ’74 conference. Max (and now Max for Live, too) is certainly at the heart of a lot of the projects we talk about here on CDM, so we’ll be watching.

Cycling ’74 founder and leader David Zicarelli describes greater “accessibility” as the goal for the new release, both in terms of “obtaining and learning” the software. That means documentation and tutorials and the Website go alongside new features in the software and new pricing. The other two goals: “quality” and “performance.”

In short, here’s how Cycling says Max 6 will evolve:

• Improved performance, particularly via “code generation,” which sounds a bit like a just-in-time compilation optimization scheme for higher-performance patches. (This won’t be included free with Max 6, but as an add-on, however.)
• A gen~ low-level signal-processing objects, for coding your own 64-bit DSP objects with greater performance than in patches.
• The Mozilla JavaScript engine is integrated for greater performance (JS was always a bit of a performance bottleneck in Max, so this is potentially pretty huge), as well as the ability to use 2D HTML5 graphics code with Max.
• Better sound quality, including a new cycle~ wavetable, resampling filters, crossfading between versions of a patch, and a new audio mix engine.
• Workflow improvements, including enhancements to how help and documentation is displayed.
• Project management.
• Improved OpenGL animation and rendering tools. (I’ll write soon about what we know about Jitter changes separately on Create Digital Motion.)

Pricing schemes have changed, too.

US$399 ($199 upgrade from v5) gets you Max, MSP, and Jitter; no need to buy Jitter as a separate add-on. (Apparently those code compilation features will run you extra, though whether that’s $5 or $500, I have no idea yet.)

Subscriptions for students now run 12 months instead of 9. There are new volume discounts for academia, also based on subscriptions, too.

The place to find out more is likely to be the Expo ’74 conference.
Expo ’74

In Brooklyn October 14-16 (coming to the East Coast after its first, West Coast installment), Expo ’74 will be a series of hands-on events. The US$295 early bird pricing ends July 15 (Friday); it’s $395 thereafter.

There’s no word yet on the implications for Max for Live, but it seems safe to assume the new release will be accompanied by an updated Max for Live edition, too.

So, what does this mean for Max 5? Via Cycling ’74 comments, Joshua Kit Clayton explains backwards compatibility:

Max 6 is essentially backward compatible with Max 5. There have been some small changes which might cause issues in extreme edge cases. For example, on Macintosh, we’ve changed from using Carbon Event Model to a Cocoa Event Model, so if an object uses its own internal Carbon or Cocoa Event Loop, they may need to make some changes since the application has changed the primary event model of the application. There may be some minor visual differences. However, the vast majority of third party objects which work in Max 5 will work in Max 6 without alteration. If third party MSP externals wish to make use of 64bit resolution audio signals, they will need to be updated, but they will still work at 32bit resolution if they remain unchanged.

Don’t worry. While there are many great changes to the application, we’re not going FCP X here

For now, you can read David’s comments from yesterday. And if you buy Max 5 starting now, Max 6 will be free.

Announcing Max 6

As Max for Live matures, Ableton is working to convince more people to try this open-ended tool – and creations built for it – as a way of extending the experience of using Live for performance and production.

For years, music software has focused on trying to do everything you need, to be a solution to problems you haven’t even considered yet. But recently, we’ve seen a move to software that considers customization and extension a core feature – not just the province of the hard-core hacker or DIYer, but something basic to the tool. FL Studio, Renoise, Reaper, Kontakt, and Ableton Live, to name a few, each incorporate tools that allow scripting, customization, and custom instruments, effects, sequencers, and other tools. (Each does it in very different ways, I might add.) In place of from-scratch construction, these tools build on the capabilities of the software in which they’re hosted.

And even if you don’t personally decide to take on scripting or patching, that means you can take advantage of unique contraptions made by other users. These creations aren’t just hacking for hacking’s sake: they meet specific musical needs, and make tools more practical and expressive. Like knowing the reeds on a wind instrument or tuning on a guitar, they’re part of how musicians are able to make their instrument their own.

Of course, unlike a new effect or workflow tweak, getting your users to embrace an open-ended tool takes time, and it may not be for everyone. We’ve been following recent efforts by Ableton to respond to feedback from their user community. While these fall short of the ability to distribute patches to all Ableton Live users – something I and others have advocated – they do make Max for Live more affordable and patches built for it more accessible.

CDM talked to Ableton’s Daniel Büttner in February about some of the changes on the developer side, both in terms of improvements to the tools and guidelines to make patches better:
Ableton Delivers Max for Live Improvements and Guidelines, Responds to Feedback; Full Details

In the last couple of weeks, Ableton has made offerings to the user side.

Max for Live Sale: First, right now you can get Max for Live for less. In the month of April, Max for Live is free with a purchase of Ableton Suite 8 or upgrades to Suite from the Lite and Intro versions. If you have Live 1-8 or Suite 7 and upgrade to 8, unfortunately, Max for Live isn’t free – but it is half off. I’d like to see more aggressive, permanent pricing from Ableton if they want widespread adoption of the tool – it seems to me that offering a “Suite” without this key component is complex for users to understand and makes budgeting for Live needlessly difficult. But that’s my prerogative as a critic and writer, just as it’s their prerogative to determine that what I’m saying doesn’t make sense for their business. In the meantime, I can certainly recommend the Suite purchase if you’re getting Live new or upgrading from an intro edition.

Updated: Current Suite owners qualify for a 30% coupon which they should have received via email, says David from Ableton via comments.

If you’re considering Max for Live but aren’t sure if it’s for you, there’s also a 30-day free trial – always a good bet.

Featuring Max for Live patches: More interesting than the pricing stuff is the fact that you can get some truly spectacular patches for Max for Live, and Ableton is doing more to highlight the work of some of the most talented, creative artists working with the tool.

As readers have repeatedly observed, maxforlive.com is a terrific resource for Max for Live lovers and those wanting fun patches to play with. It now includes a Featured Devices page curated by Ableton’s sound team, with some really great, free stuff.

Ableton has also added both new basic devices – including some oft-requested options, like an LFO – and featured artist creations, too.

Max for Live Highlights from Artists

Artist endorsements can be a mixed bag – they sometimes feel forced, an attempt to get some fame to rub off on a product. Not so here: as with, say, some of the recent gems on the Reaktor side from the likes of Tim Exile, the featured artists working with Max for Live really are pushing the technology and the medium.

Robert Henke, aside from being an Ableton co-founder and conceptually steering a lot of their direction, has one of the best recent Max for Live creations. Monolake helped establish the granular sound on the electronic palette in the 90s, so it’s little surprise that a Henke-designed granular device is a terrific instrument. See the video at top – it’s one of the best reasons yet to try Max for Live.

Kapture by Liine is an eminently-practical entry, sucking all of the parameters in a Live set into snapshots and allowing you to morph through them. I’ve been testing this paired with their iOS app on an iPad, and it’s terrific; I’ll finally talk about it once I’ve wrapped my head around some good examples.

And, I should say, it’s thoroughly enjoyable seeing Richie Hawtin back as Plastikman – the work he’s doing on the tour is exactly the sort of audiovisual electronic performance I hope we see more of from artists famous and unknown alike.

There’s also a House-style beat generator by Alexkid (video, above), and of course the obligatory APC step sequencer (though check out more step sequencers below).

This isn’t just about pure electronic dance music, though. Henrik Schwarz has a new edition of a device that fits notes to a musical scale, as relevant to jazz artists working with electronic instruments as electronica artists. Katsuhiro Chiba makes some classic retro-80s synths that could appeal to keyboardists in a wide variety of genres. I love seeing versions of the Yamaha TX81Z or simple, analog-style Sep2.

The most welcome offering, though, may be the addition of new LFOs, which allow synth-style modulation of any Live devices. Manuel Poletti has a powerful LFO collection with plenty of options for assigning modulation wherever you like. (See our previous, unintentionally-controversial, coverage of LFO modulation in Live, and more examples on the maxforlive.com site.)

Find the artist devices, descriptions, and downloads at the main Ableton Max for Live site:
http://www.ableton.com/maxforlive

New, Essential Devices

Max for Live itself has added 21 devices that give the tool a more complete set of basic building blocks for patchers. That’s good news, in that it means a lot less reinvention – and because the value of Max for Live itself goes way up.

New in the release this spring are LFOs, envelope followers (for using an audio signal to modulate parameters), randomizers, and multichannel routing devices.

Indeed, my only concern here is that many of us hoped to see some of these capabilities in “native” Ableton Live devices, rather than Max for Live patches. An LFO to many users is an essential built-in module that would benefit the software, as it has been in some rival tools, comparable to tools like chord and pitch manipulation for MIDI included in Live.

I don’t know that the LFO per se is necessarily fundamental to Live. But I do hope that Ableton continues to develop native devices for the Live environment. Max for Live could serve a useful purpose here – as a testing bed and prototyping tool, as it has been intended – and aid in determining which tools really do need to be included with Live itself.

More (updated info) on the included devices:
What Comes with Max for Live

And Don’t Forget…

Even with all these Ableton-provided goodies on their site, it’s worth visiting community sites like the unofficial maxforlive.com.

There are some gems at maxforlive.com, including the featured page:
http://maxforlive.com/featured/

– some of those, in turn, chosen by Ableton. Pictures of some of my favorites:

Let us know how you’re using Max for Live, if you find it fits into your workflow or if you focus on the core Ableton software instead. And certainly, if you’re a Max for Live patch developer or user and want to show off your favorites (including your own), we’d love to hear from you.

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…

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.

It’s been a long, long wait, but it’s now official: Ableton and Cycling ‘74 have collaborated on Max for Live, which integrates Max/MSP with Ableton Live. There’s tons of information on the Cycling ‘74 site, and I’ll be doing some follow-up interviews for CDM soon with more details, but here’s the overview.

What is Max for Live?

Max is an add-on product for Ableton Live 8, which will be announced in a press conference shortly. Note that it isn’t just Max or just Live – it’s a separate, add-on product. No pricing information yet; availability later in 2009.

What Will You Be Able to Build?

• Step sequencers
• Instruments
• Effects
• Stuff to control Live
• New hardware integration features, with your own instrument / effect / sequencer creations, and with Live itself – think, build your own hardware mappings

What I’ve heard is that via native controls, you’ll be able to control anything you can control in Live with a mouse, down to moving warp markers around. That’s obviously huge, but expect the specifics of these details (and eventually, how to do it) on this site over the coming days and months. I’m also eager to find out if it’ll be possible to use Max for Live with OSC inside Live.

How Integrated is It?

• Native Live API controls: Max now gets a native API for controlling Live, with live.object, live.path, live.observer objects. This is actually arguably the most important part, because it means you could in fact use Max to control Live in place of the Python-based Live API. That raises a bunch of questions and unfortunately, this is the part of Max for Live about which we know the least, but you know this site will be all over the details as soon as we can get hold of them. (The only bad side of this that I can see is that it may mean fewer options for Live users who want to use their own development tools instead of Max, but I’ll investigate.)
• Preview mode: This lets you edit in Max while devices continue processing audio/MIDI as if running inside Live. It updates in-place in Live’s device view. That’s been possible previously using things like Native Instruments’ Reaktor plug-in or the combination of FL Studio and Synthmaker, but it’s certainly new to the Max environment.
• UI controls: You can create Ableton-style interface controls for your patches. This is really extraordinary: you build a patch as normal, and what Max 5 calls its Presentation Mode now looks like an Ableton-standard UI in the program, with full support for color schemes. You even get descriptive text in Info View when you mouse over something, just like the official Ableton stuff.
• Multiple undo: Undo in Live applies to Devices created with Max for Live.
• Tempo sync, sample-accurate automation: I need to get the details of this, but normally syncing tempo is a major pain using MIDI, ReWire, or even plug-ins – this appears to allow more direct integration.
• A step sequencer object: Previous efforts like SynthMaker in FL have made it pretty easy to build instruments and effects, and it’s certainly possible to build sequencers in tools like Reaktor or Pd. But what’s unique about Max in Live is that it provides a sequencer with a Live-style interface that integrates with tempo.
• File/preset integration: This is where it gets really awesome – juggling Reaktor patches, for instance, can be a pain.
• Web collaboration: Ableton Live 8 adds web collaboration options, which extends to Max devices. 

What Devices Are Included?

So far, you get a nice set of Devices to use with Max for Live:

• Step Sequencer, with four 16-note sequences, shift, random, MIDI control
• Loop Shifter, with automated mapping and playback, for Max-style looping
• An extension for the new Akai APC40 that turns it into a step-sequencer editor for Live MIDI clips

Now, note, on that last item, you don’t necessarily need to run out and buy Live 8 and Max for Live and a new APC (though there are worse things to happen to someone). The new features should open up new controller integration features and custom software-controller creations for all kinds of hardware. For instance, the monome (site | cdm tag) should greatly benefit from the features in Max for Live. It’s already got a rabid community of Max patchers behind it, and there’s no reason you couldn’t do something wild with Live, Max for Live, and the monome – including additional features you can hack into the monome, like tilt sensors/accelerometers/IR range finders. (Yum.)

And in fact, the monome community is already on it without the aid of Max for Live: Pages, built in Java, is an elaborate app for automating access to some of Live’s power. You can imagine that the availability of Max for Live should mean even more of this sort of thing.

Where to Read Up

I’ll update this as more information comes through, but here’s what to get where:

David’s Tools for Creating Devices in Live is probably the most important read, as it shows how the integration works – already juicy, though we need to find out more about those native controls for actually manipulating Live

David Zicarelli’s "Perspective on Integrating Max and Live" talks about the genesis of the project and what it means to existing Max users

If anyone stops by NAMM booth 6314, we’d love some other perspectives.

What this stuff means:

Max for Live is best understood as Max/MSP/Jitter in Live. Here’s a full explanation, with more details to come on exactly how they integrate:

Max For Live is Max In Live: MSP, Jitter, OSC, and All; The Open Source Side?

And yes, I will be following up on open source alternatives, because they have their own strengths and weaknesses.

Ableton founder and CEO Gerhard Behles explains to Akai in an interview released this morning:

Owners of the APC40 who also own Max for Live can change the way the APC40 controls Live, and completely customize their experience. This means things like step sequencers and drum rack support and other things that only feel right with hardware will now be available for people who own these two great products. The boundaries of what you can do with complete customization and hundreds of LEDs are infinite.

I’m guessing at this point you might like to know what "Max for Live" is. Suffice to say, Cycling ‘74 said that they’d show their collaboration with Ableton at the NAMM show, and there’s an Ableton press conference later today.

My main question on this: how much control do you have? Is there anything special about the APC40, or is what Gerhard really saying that you can make your own weird step sequencers with whatever hardware you want using Max for Live? (For that matter, there’s no reason you can’t do this right now using Reaktor or Pd or a number of other tools that also work with Live.) My sense is actually that this is different, but in terms of what objects are specifically in there that enable it, we’re still waiting to find out (and may actually have more of those specifics after NAMM).

If you’re looking for pitch- and speed-independent warping and other sonic effects, and Max 5 is your modular patching tool of choice, a new tool is now available to add to your arsenal. elastic~ is an object similar that allows high-quality audio warping. The developer claims it uses the “same algorhythm as software giants Cubase, Ableton Live, and Kontakt.” I’m personally still quite happy with granular tools in software like Reaktor — and have recently gotten interested in exploring implementations in the free and open source SuperCollider, but of course there are great advantages to working in Max, and the implementation here seems unusually elegant and easy to use.

The developer writes:

With elastic~ it’s easy to tempo match loops together (either to each other or a global tempo); create a sampler that doesn’t change the speed of your sample as you change pitch; correct out of tune samples; create harmonizers; and just generally loop and bend and warp and stretch and……

elastic~ Product Page

The software is the creation of Simon Adcock and Joe Jarlett.

Product price is GBP20 — though thanks to the US Dollar surging against the Sterling, that’s not so bad. If you grab this and make stuff with it, let us know. Got an external you prefer, or other tool (a la SuperCollider) for audio warping, let us know that, too. (Warping audio is a personal and intimate process. I can’t imagine you’d share it with just any tool.)

Update: The engine in question is Elastique — quite nice, in fact, to have this “ported” effectively to Max/MSP! (And check out how many places it’s used — fascinating.)

Cycling ’74 have updated Max 5′s pricing and streamlined a bit in the new release. (That means Max for MIDI and basic data crunching, MSP for audio, synthesis, and signal processing, and Jitter for video, 3D, and advanced data processing.) Since this impacts a number of our readers, it’s worth going over this.

Updated: The story now reflects a clarification from Cycling ’74 over which Jitter objects work in Max/MSP.

New academic pricing:

• US$250 per student
• US$59 for a 9-month authorization
• US$109.45 for a permanent upgrade from Max/MSP 4

Student discounts

See also education and teacher discounts; 1-4 licenses for either K-12/higher ed faculty or your institution are now US$475.20 for the full Max/MSP/Jitter

Academic pricing is now only for Max + MSP + Jitter — none of the tiered pricing from before for just Max/MSP, etc. And if you bought after October 1, the new version is free. Plus, if you own an academic license that didn’t include Jitter, you get it now with your upgrade.

I recommended the 9-month license for my students ($39 of it gets subtracted from your final order) when I was teaching Max at Brooklyn College, and people were really happy with it.

New full pricing

• US$699 for the full Max 5
• US$495 for Max/MSP + a limited, unsupported set of Jitter objects (see below)
• US$199 upgrade

Pricing details and Max 5 overview

Note that Max 5 at this time doesn’t yet include the ability to export patches as plug-ins via Pluggo. ReWire, etc., still work, but if your main application for Max is building plug-ins for other hosts, you may want to hold off.

This came up in comments, so I’ll say it again — we’re not covering Max because I think it’s the only alternative. On the contrary, Reaktor and Pd are also each cross-platform patching environments with their own unique strengths, to say nothing of other synth environments (ChucK, Csound, SuperCollider). Each of those can work in academic settings, as well. But there’s no question Max 5 is big news on this scene, a major update to the tool that first popularized visual patching as music software

How much Jitter do you get in Max/MSP?

Cycling ’74 revised their site; while Max/MSP does now include a limited set of Jitter objects, they’re officially unsupported if you haven’t bought Jitter. In other words, you can use them — and this means developers working on patches can share those patches with people who don’t have Jitter within the limited subset — you just don’t get support from C74. I think if you want to use Jitter objects, you should just buy Jitter, but this is still good to know (particularly for teaching environments, I might add). Here’s the list:

jit.alphablend
jit.fill
jit.fpsgui
jit.iter
jit.matrix
jit.op
jit.pack
jit.peek~
jit.poke~
jit.pwindow
jit.qt.movie
jit.spill
jit.unpack
jit.xfade

… Note this doesn’t include the important networking objects, so it’s just FYI.