Even before Max for Live was available, hackers had found a way of interacting with “secret” APIs inside Live for custom control, allowing them to customize Live’s behavior and make it work more seamlessly with hardware. That included providing something Ableton themselves had not: real, native control of Live via OSC, for more control than MIDI alone can provide. I was assured such hacks would continue to work, and sure enough, they have. Here’s how to get started.

You may wonder, of course, why even bother now that Max for Live is available? Max for Live is a powerful environment for creating instruments, effects, sequencers, and other devices within Ableton Live, and via its access to the Live API, it can even be a tool for customizing how Live works. But it adds an additional layer of abstraction, it is somewhat limited in how much it can manipulate interaction with hardware, and anyone wanting to use your creations will need to own Max for Live and not just Ableton Live. And not only that, but some people will simply prefer scripting in a language like Python to working with visual patching. (There’s still reason to consider M4L, too; see the full link to its “API” for Live, below. But we do have multiple options)

So, with that out of the way, here are the current solutions:

Make your own MIDI remote scripts.

Hanz Petrov has written an intensive introduction to creating your own MIDI remote scripts in Python, using the new Framework classes:

Introduction to the Framework Classes
http://remotescripts.blogspot.com/

Use OSC, via the Live OSC API Hack (or MIDI)

Ableton doesn’t have native support for OSC — unfortunate, given that’s now a feature of major visual applications (Resolume, VDMX, GrandVJ, Modul8, and others). But while we keep bugging Ableton for OSC to be on equal footing with MIDI, you can make use of a special Python hack that provides an OSC API to Live.

If the above scripting seems intimidating – and I can certainly see why it might be – the LiveOSC API is refreshingly simple. Because you can simply send OSC messages directly, controlling Live with tools like iPhone apps or Processing sketches or even hardware could become comparatively simple – and yes, simpler than working in Max for Live. If you only have MIDI, there’s even a MIDI API, too. Here’s where to start:

Complete documentation of the LiveAPI project [assembla]

http://monome.q3f.org/wiki/LiveOSC

Why it’s nice: you can send something as simple as /live/play/clip (track, clip) and trigger a clip. That’s even more direct than the usual MIDI interface.

Most importantly, this now works with Live 8.1. See the video below for an example of this in action:

mlrV4live tutorial (&casio madness) from StevieRaySean on Vimeo.

Check out his Arduinome build documentation, too. (Arduinome is an authorized clone of the monome using readily-available parts.)

The Max for Live way: Live Object Model

Complete LOM documentation at Cycling ‘74

And yes, it makes my head spin a little, too. (Or perhaps the word is “oscillate.”)

Max4Live.info (Michael Chenetz) has done a great job of making this a bit more manageable. In the video below, he explains how to use the interaction between Max for Live and Live; there’s also a tutorial on sending messages to a control surface like the Launchpad. But note that some of this can actually more complex, and more hardware-specific (APC/Launchpad-only) than the hacks above. It’s a case in which the hacked version actually works a little better than (cough) the official version.

Max For Live Paths, Objects, and Observers from Michael Chenetz on Vimeo.

My own challenge for myself: just make the Launchpad intelligently control device parameters, something it currently doesn’t do. I’ll let you know how it goes.

Thoughts on the merits of these different approaches? Projects you’ve made using one or another? We’d love to see them.

Didgeridoo from bar|none on Vimeo.

You can’t quite dance to it, but bar|none has a beautifully-shot video of a strange, invented instrument constructed with some of the technologies we saw last week. As noted then, new support for OSC in the powerful Kyma sound system means the ability to control imagined instruments in more sophisticated, higher-resolution ways. Just days later, bar|none responded to my post with one of his first experiments. It’s just the beginning of his work, so judge it accordingly – think of the first emanations of a newly-created musical instrument – but it’s a reminder that far-out ideas are possible when you combine custom soundmakers with expressive control.

The controller is Jeff Snyder’s Manta, a touch-sensitive controller with velocity sensitivity and a 6×8 array of hexagons. Jeff showed off his instrument at Handmade Music Monday night here in New York; I hope to follow up with a closer look at the Manta soon. Notably, the Manta is not an OSC device; it’s an HID USB device, just as a typical mouse or keyboard is. HID, the standard drivers for which are included in every desktop OS, also supports high-resolution data, so it’s a second alternative to MIDI for input.

My first Kyma X patch for the Pacarana. Kyma is unreal and let’s you do almost anything in Sound Design. I took a concept of a didgeridoo patch on my modular and built it back in Kyma but with even more expression. This is still a work in progress.

The touchplate is a Snyderphonics MANTA. I spent some time coding some algorithms in MAX to enhance the performance control of the patch using velocity, aftertouch and polyphonic aftertouch + controls using OSC to Kyma.

The Manta is a fantastically wonderful controller. It shows it’s [sic] flexibility and feel here.

The patch is microtonal meaning pitches are in divisions of the western concept of half and whole tones.

Since that video, he’s been trying more sonic ideas:

Been messing with this sound and here’s a version where the didgeri is resonating as if it were a metalic vibrating tube as well. This is just trying to see the kind of sounds I can get out of the patch.

soundcloud.com/barnone/karplusdigeri

This makes me wish I could afford this setup, but if, like me, you’re on a tighter budget, the ideas here could easily be applied to other rigs. Keep the experiments coming!

Updated: bar|none aka Chris Lloyd shares his camera of choice: it’s a Canon 7D with a 50mm 1.4 lens for the “Bokeh blur effect,” a tip from stretta.

The Didgeridoo is one of the human race’s great triumphs in instrument design, simple but capable of producing profound sound – thanks, indigenous Australians. Kyle Evans sends us his project to extend the instrument with powerful digitally-augmented sound-making capabilities. The ingredients:

• Bluetooth wireless data transmission, connecting to a wireless mic
• Additional controls, including pots, push buttons, and toggles. (One limitation of the original relative to other blown instruments is its lack of any kind of keys or finger holes – an issue if you want to play with more than one note or modify the sound with something other than your mouth.)
• Max/MSP-patched synthesis and signal processing, analyzing the input and making lots of wonderful sounds

As he describes it:

I created this instrument to experiment in the combination of the organic sound qualities of a didgeridoo with the advanced signal processing capabilities of modern computer programming and sound synthesis. This custom built didgeridoo features externally mounted modules that allow the performer to process and manipulate the sound of the instrument in real time. All control data is transmitted wirelessly via blue tooth and is controlling several audio processes created in a custom-built software environment. If you have any questions about the instrument please feel free to ask.

Truly inspiring work, Kyle!

See also: Perry Cook’s DigiDoo. I’m familiar with the instrument, but couldn’t find any good documentation online; if someone has any (or, if Perry is out there reading), send it our way. The more digital digeridoos, the merrier!

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.

From ribbons to multi-touch, musicians are looking for expressive controllers, ones that allow continuous control for performance.

Oh, yeah, and it’s like totally super-cool on the original Star Trek when people run their hands over the Transporter controls and the blinky lights move. I mean, like still super-cool, even in 2008. (Hint: try to look completely chilled out like Spock when you do it.)

So, one of the things I noticed when the Monome was first introduced was, excellent as that open controller is, you’ve got buttons and no continuous controls. Ever wished another nice square box could sit next to it and give you multiple touch controllers? Good news: Stribe is here.

The Stribe is an 8-channel multi-touch controller for music or video software. 1024 individually-addressable LEDs provide animated visual feedback.

The low-resolution (16 x 64) LED display is controlled in real time by either firmware or host software, or both. MIDI or OSC communication to compatible hardware and software is achieved via patches written in Max/MSP.
Touchstrips down the center of each channel trigger events in the software and the firmware, which drive the display, creating a haptic feedback loop. Each of these eight “channels” has two 64-led-tall columns, e.g. a left and a right.

The Stribe can act as a touch controlled meter bridge, or as an interactive, animated16 x 64 led display. Oriented horizontally, the Stribe can more intuitively interface with step-sequencer type applications, or allow direct manipulation of granular synthesis sampling, or allow the user to perform “scratch” like gestures

or…?

Stribe

Via NYC Resistor Microcontroller Group (thanks, phineus!), also posted with typical insane speed by Matrixsynth

Phineus created the Stribe (see more on his blog) after being inspired by the Monome, and uses his Monome and Stribe side by side. Whereas the Monome is typically procured as pre-built hardware or kit, Stribe is a DIY project (donations welcome). The basic components are pretty simple: standard lights and touch sensors. You can find all the specs and software, plus a new forum, on the Stribe site above.

I’ll be making one, that’s for sure. Too cool. And I think some improvements could be made in the case design, as well. It’ll be interesting to see where people take this.

What’s this new Max about, and why was it such a big deal at the AES trade show? To really understand, let’s turn to gaming for a moment. When Nintendo described their vision for the Wii, they talked about appealing to three groups of customers:

• The “hard-core” gamer; that is, their existing audience, of course
• “Lapsed” gamers: people who had done some gaming at some point but lost interest
• Entirely new gamers, across a variety of demographics

History will have to be the judge of Nintendo’s slim white box and controller-wagging interface, but I heard some similar development goals at the AES audio show this weekend. Nowhere was this more apparent than Cycling ’74’s upcoming Max 5. Substitute the word “patcher” for the word “gamer”, and you’ve got a snapshot of the new Max.

After all, whether you’ve touched Max before or not, you’ve likely got some needs in at least one of these categories. Beginners are easily intimidated by the “visual programming” metaphors of a blank-slate, modular tool like Max. Many others get through a couple of patches, often in a school course, but wind up having difficulty getting beyond that first work later on. And even advanced users (maybe especially advanced users) are always looking for ways of working faster.

The build I saw of Max wasn’t entirely complete, but I will say it’s tremendously promising. I talked to many for whom the chance to see Max 5 was the highlight of the entire AES show. It’s a tool you really need to see in action, so be sure to check out Cycling’s just-posted videos of the program:

A First Look at Max 5 [Cycling '74]

This is not the all-words, no-pictures manifesto we saw recently: now you actually get to see the tool in action. Highlights:

• The interface zooms, scales, and snaps: I knew this was coming, but I was really pleased at how Max-like this is. It still looks like Max, but it’s more usable.
• There’s a patcher inspector: The inspector lets you easily adjust attributes without mucking about with typing things into an object box or sending messages to an object, which was always very confusing. You don’t see much of this in the video, but trust me, this is huge, especially for more-complex Jitter objects. And while this is shades of Quartz Composer, it works much better than the clunky UI implementation in that tool.
• Finding the object you need is much easier: There’s a pretty visual browser which will be a lot of fun, but there’s also auto-complete when you type in a name. (Programmers will recognize that functionality from IDEs like Eclipse; Mac users, think QuickSilver fast-typing goodness.)
• There’s a nifty new file browser: Drawing from iTunes and Ableton Live, this makes it really easy to get access to files in the file system — no more manually entering paths. The bad news is, it sounds as though this may not initially be usable in your own patches, for, say, making a video navigator for a VJ app or sample loader for an instrument; hopefully, that’ll either sneak into the final build or be available soon after. (The Cycling page does mention integration of the database that powers this browser with JavaScript, though, so advanced users may have some new options.)



A new file browser takes cues from iTunes and Ableton Live.
• Debugging and feedback and help everywhere: The old way of working with Max was pretty slow. Add an object. Click the object’s help to figure out what it does. Look up its help page. Go find the tutorial reference in which it’s introduced. Add a print object to watch what data is coming out of it. Go back and try to see why it’s not working. Now, there’s feedback everywhere: pop-up hints for each inlet and outlet, integrated help, the ability to mouse over objects and see what data is moving through them (including Jitter matrices, apparently), and even better-organized data feedback in the Max window. The integrated help is much richer, too, though it wasn’t quite ready for demo when I saw it; I expect we’ll find out more about this soon.
• Presentation mode for performance, and the end to messy patches: This is really the feature that could make you jump for the new Max. Presentation mode lets you select elements in your patch and add them to a performance interface, so that in addition to locking a patch, you can build a custom interface as an additional layer. Let me translate that: you’ll never have to stare at a giant, messy patch while you’re trying to perform again. Now, Reaktor has had something like that for years, but again, the implementation is really Max-like and unique. When you go to presentation mode, you can drag objects where you want them. Switch back to editing mode, and they remain connected to the rest of your patch and automatically move back to their edited locations. (If that didn’t make sense, go watch the video, and expect to see more examples of this soon!)

There are still lots of questions, of course: there’s no solid release date or pricing plan, and we haven’t yet heard what Cycling is cooking up with its new partner Ableton, or how that fits into Max 5. Jitter will be supported with this new release, though, like the internals in Max/MSP, it doesn’t sound like there will be any earth-shaking changes immediately. (I.e., it won’t be Jitter 2.0.) Then again, Jitter patchers should benefit just as much as MSP heads from all these other features, so I wouldn’t underestimate the potential there.

I think there’s no question this will step up the game for custom-patched music and multimedia software. Max isn’t the only game in town by any means, though it is arguably the most extensive tool (especially if you’re counting number of objects). I can’t wait to get my hands on the new Max and share the patching experience, and I’m equally interested to see what happens with the next version of a more specialized tool like Reaktor. As always, stay tuned.

Ableton has an interesting teaser up on its website today:

A new strategic partnership between Ableton and Cycling ‘74 promises exciting developments on the horizon for digital media creators, producers, and performers. Ableton CEO and cofounder Gerhard Behles and Cycling ‘74 CEO David Zicarelli are pleased to announce this unique alliance between the two dynamic and innovative audio/video software companies.

Cycling ‘74 and Ableton to Codevelop New Products

The announcement for now is mostly like a mutual love letter between the two developers. But maybe that’s appropriate: Live wouldn’t be Live without Max/MSP’s long history of real-time, computer-based performance. Many Live users are also Max users, combining Live’s pre-built live performance capabilities with Max’s modularity. And because Max/MSP is built as a prototyping environment, many Live features have been sketched in Max before being developed into Live. I’ve gotten to look over the shoulder of Ableton developer Robert Henke (monolake) at some of his prototyping patches. Operator, for instance, lived as a subtractive/FM Max/MSP patch before being built into Live. That makes perfect sense: traditional development is slow and inflexible. By sketching in a visual patching environment like Max first, you can freely experiment with features, design, and interface.

So, wouldn’t it be great if Ableton and Cycling ‘74 could cooperate more formally, having been friendly with one another in the past? Absolutely. And, while that moment is not now, I look forward to getting information on … um … whatever they’re doing … whenever they do it. (For some reason, I have an image of a deep, basement laboratory in Berlin, filled with 40″ plasma screens covered in inscrutable Max patches, clouds of granular drones echoing through the room, steaming beakers full of bubbling red liquids, and Robert Henke, David Zicarelli, and Gerhard Behles in lab coats laughing maniacally. Careful with the particle accelerator, please, Robert.)

I’ve confirmed with Ableton what this announcement is not (before they get flooded with questions):

1. It’s not a product announcement (yet). There’s no announcement of a product or a timeframe. Yes, there is something coming — but there aren’t any imminent details. (Hey, this stuff takes time to develop.)
2. It’s not a merger or acquisition. There will be no Ableton ‘74 or Cyclington. Or Ablax/MiveSP/Jitterton. No one is buying anyone. Cycling ‘74 and Ableton are not becoming “A Division of Avid.”
3. Live was never “developed in Max/MSP.” Live was (and is) often prototyped in Max. You can also prototype applications in PowerPoint or Flash. Developing an application is a different matter altogether. Starting with Live 1.0, Live became a separate, compiled application. But as for other cooperation, we’ll just have to wait.

Also, as a Max/MSP nerd, I have to point out that the way they’ve patched Ableton and Cycling ‘74 together in the graphic is likely to cause stack overflows as it’s a loop. (Sorry, couldn’t resist.)

More details on the deal:
Cycling ‘74 Founder Talks Ableton Collaboration, Max 5

Well let’s have a look at the required aspects of a CDM article: Electronic Music? Check. Samples? Check. Lasers? Check. Midi? Check. Arduino? Check. Laptop? Check. Max/MSP? Check.

Yep, I think we can squeeze it in somewhere.

Masaoka was then able to play the instrument in its natural, acoustic state, use the gestural data supplied by motion sensors to generate and process sounds electronically, or do both at the same time. Toward the end of the Monster Koto’s life cycle, Masaoka installed laser arrays above and below the instrument’s body.

The Laser Koto was born when she decided to get rid of everything but the lasers.

Check out the rest of the article.

Other forum questions currently looking for answers include: Is buying Logic Pro 7 a bad idea? Is the Sonny Bono law going to go away? Can you capture live imagery from a Canon Powershot to G4 Powerbook? Does Zebranlogic make great looking effects boxen? Can people give Breathe advice on how to start making electronic music?

Russian DJ Artyom has built his own DJ audio hardware out of wood and electronics, complete with dual cassette playback boxes. The cassettes feature pitch control (fine and coarse), pitch bands, a motor off switch, and more, and he’s custom-built mixers, cross-faders, and EQ.

Then, he hooks these boxes up to his PC and relaxes — wait, no he doesn’t. His PC is packed with custom DJ patches built in Max/MSP.

Full hardware and software details at Artyom’s site, including downloadable Max patches, in English (see also Russian content — I’m sure someone out there speaks Russian):

Self-made DJ equipment
Max/MSP DJ Stuff

Via the rich electronic music blog, Filter27: How to DJ with an old cassette tapes

See also: KDE-Head photo on flickr with specs

Updated: Doh! Tom at Music thing beat me to this in 2005. Slight CDM lag there. ;) Nonetheless, maybe somebody will have a look at those Max patches and get some new ideas.

Man, these lazy newbie DJs, embracing a new-fangled playback medium like cassettes and Max/MSP patches. They’re nowhere near as authentic as the oldskool DJs playing … erm … CDs … at weddings. ;)

Another gorgeous shot of his brilliant hardware-building work after the jump (so you don’t have to wait through glacial load times):

1. New Universal Binaries: Mode, Hipno, and UpMix are all Intel-native. But the big news is that Pluggo, the long-beloved C74 plug-in library, is available — meaning you should also be able to turn your Max compositions into Intel-native plug-ins.
2. Max/MSP 4.6.2 / Jitter 1.6.2: Max 4.6/Jitter 1.6 had already brought Intel Mac support, so other than some bugfixes for Mac users, the big news here is for the Windows side: the new features in Max 4.6 and (most significantly) Jitter 1.6 are now available to Windows users. I’m hoping this also means native uyvy video support, but I’ll save that discussion for Create Digital Motion.

If you’re on an old version of 4.5.x, it’s well worth upgrading. Cycling has put in some subtle but significant improvements over the last few “point” releases, and they’re free for anyone who owns Jitter 1.5 / Max 4.5. Cycling also wins points for providing Intel Native support absolutely free of charge; this is one of the only major application developers I can think of that did that with a flagship application.

I’m currently teaching MSP at Brooklyn College, and we get into the first meat of synthesis this week. I have to say, while I admire Pd, I’m happy to have Max so that we can take advantage of a friendlier interface and far more detailed documentation. The two products, however, commercial and open source, continue to benefit from the other’s existence, and I’m even seeing more people running both on the same machine. Mostly I need people to start trailing me with an espresso machine so I can keep up with all the software I’m using.