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

I got to spend yesterday working with the Launchpad; see the video above which I think should help you get a sense of scale and what it looks like. (Also on YouTube) We have additional videos from other sources below.

It’s only been public for less than 24 hours, but as we did with the APC40, I think it’s time for a superguide answering questions about the Novation Launchpad controller.

The Launchpad and the way it works reveals a lot about how controllers work with Ableton Live. You may be surprised to learn a lot of this doesn’t require a special controller and doesn’t require Max for Live – it’s standard Ableton stuff that works with MIDI. (Remember MIDI?) And I think some of these answers could be worth a read if you have interest in hardware control hacking in general.

There have been a lot of questions from myself and readers, so I’ve done my best to get answers. Realize, a lot of this information is developing and is based on my limited understanding, so it’s all subject to change. I’ll update this guide over the next couple of days if I get any corrections.

Side note: What about interoperability? I intend to talk more about OSC and the Live API (and each separately) in coming weeks. I think it’s impossible to judge the full picture of how Live can interoperate with other tools, though, until there’s some more information, so stay tuned on that.

Basic Questions

Q. What do you get with Live 8 Launchpad Edition, the bundled software?

New to Ableton Live, and wondering if you can get anything done with the “lite” Launchpad Edition bundled with the hardware. The short answer is, yes you can. The included edition has restrictions, but it’s still a reasonably capable version if you’re new to Live and want to experiment.

Ableton Live 8 Launchpad Edition vs. Live 8

The Launchpad Edition even comes with 1 GB of Loopmasters loops to get you started.

Most importantly, ReWire support for Master and Slave (Host and Client) is included. That means if you have an existing host and just want to play with Live’s non-linear clip launching features, you can stick with that host, using Live alongside software like Reaper and Reason. You may want to consider upgrading, though, as some cool features like the use of Racks and the ability to slice instruments, plus the “Complex” warp mode, are missing.

Q. What the heck is going on in the crazy Novation video demo? How do I do that myself?

There isn’t any Max patch or other voodoo in the video demo from Novation. It’s all just a standard Ableton Live set, and the fact that the Launchpad responds to MIDI messages as well as sending them (something useful if you’re scripting the Launchpad in software other than Ableton, too).

Matt Derbyshire of Novation put together the video. Matt’s an interesting guy musically when not working for Novation, too – he’s part of a DJ Shadow cover band, for one. He shares with CDM how he went about this:

It’s actually a very simple session.

1) There are four clips only for drums in the drumrack channel

2) Each clip is pre-recorded but EMPTY at 1 bar length

3) These four clips are the first four clips in session mode but for convenience I also learned these to to User 1 mode bottom four left buttons.  Basically setting this up removes the need to rush back to session mode to drop out of record

4) Obviously quantize is on ‘cos my playing ain’t that great.

LED feedback

In User 1 mode the bottom left button turns on/off LED feedback.

The important thing I want from the video is to show that I personally do not think the lack of velocity sensitivity stops drums being played. In fact, to the contrary, I think in creative electronic music it helps to even out the playing.

The still-simpler explanation:

So long as you use the User Mode to play, enable LED feedback, and route MIDI from Live back to the Launchpad, you can get interactive light modes, as seen on the monome and Tenori-On.

Q. Okay, the Launchpad can assign control to continuous values. But it’s got buttons. How do you get eight buttons to replace a fader?

Actually, thanks to an Ableton feature that works with any MIDI controller (not just Novation or Akai), this is quite easy to do. You can assign any range on your controller by holding it down.

From Novation’s Matt Derbyshire:

Step 1: Choose the slider/knob you want (i.e. cross fader)

Step 2: Select USER 1 or 2 mode on launchpad

Step 3: Select MIDI learn mode in Ableton

Step 4: Select the thing you want to control (ie crossfader)

Step 5: Select the range of buttons on launchpad

Note that this also works for playing clips.

Now, obviously, if you control something like a volume fader with a set of buttons, you won’t get continuous values. And unfortunately neither Ableton nor Novation has designed any sort of interpolation between button values (though DIYers could find a way to do that). But I’m kind of finding the angular changes in buttons to be fun to play with. If I want a knob or fader, I’ll use a knob or fader.

Q. What can you do with these User Modes?

There are two User pages. User 1 sends basic note values – minus any velocity sensitivity, just on/off. User 2 sends control changes. User 1 by default will play any active MIDI inputs listening to channel 1. In Ableton Live, User 2 only sends control changes once you’ve mapped it using the MIDI Map, to avoid accidentally triggering notes when trying to control something else. (See also the special behavior with Max for Live below.) Of course, in software other than Live, you’ll set up whatever layout you want.

You can’t rearrange the organization of pitches on User 1 because there’s no real editor for the device; everything is hard-wired. On the other hand, you can always make this adjustment in software, as in a Rack in Live.

Advanced Live Use

Q. How will Max for Live integration work?

Max for Live will use the User 2 page. The good news here is, Max by default will listen only to User 2 while the other modes get routed to Live.

Q. Can you control Devices dynamically using the Launchpad?

No. Unfortunately, while there are pages for mixer settings and a generic way to transmit MIDI control changes, you can’t click a device and have a page on the Launchpad automatically make its eight columns control eight parameters / macros. That’s actually a feature enabled by the simple scripts available for the Korg nano series here on CDM (see my post explaining how this works, follow-up script from reader Raymond).

Of course, because this feature is supported by the Korg with our scripts and it’s very, very compact, the nanoKONTROL and Launchpad could make a great, cheap combo. And if you have Novation’s ReMOTE, Nocturn, and the like, you can alternatively use them – so, for instance, a keyboardist could stick the Launchpad atop a keyboard.

Q. Can you edit MIDI assignments? Is there a MIDI template editor, in other words?

No. All the MIDI assignments are hard-wired. The good news is, everything appears to send MIDI, though I still need to investigate how that works outside Live. The bad news is, as with the APC40, a lot of functionality is organized around Live.

That would be my one potential criticism, which is that we’re moving away from hardware that’s useful everywhere to hardware that’s useful only in one program. But I want more time to see how the Launchpad performs outside Live before I pass judgment on the Launchpad in particular, especially as I don’t even have the final software yet.

I still like editors, though, Novation, if you’re listening.

Q. What if you still have Live 7?

Update – official word: Ableton’s Baptiste Grange tells CDM:

On Nov 1 we’ll release two updates: Live 8.0.7 and Live 7.0.17. These will both support Launchpad.

So, Live 6 and earlier would need to upgrade, but not Live 7.

Hacking

Q. Will we get the full MIDI implementation and protocol for creating custom patches or custom setups with our own software? Will that be true outside of Live, too?

Novation confirms that they plan to release the full MIDI implementation and communication protocol for the Launchpad at launch. That’s something that was missing on the APC40, leaving us all to figure it out ourselves, so I’m looking forward to seeing that documentation. Part of the reason to use MIDI is to have a spec that everyone can read so power users can do what they want.

Q. Can you control the lights using MIDI?

Yep. This should be in the full documentation, too, but here’s a sneak peak. Bjorn from the awesome Covert Operators sent me the velocity assignments, which I’ll be using to hack my Launchpad setup:

Velocity 0 = Off
Velocity 1 = light red
Velocity 2 = medium red
Velocity 3 = full red
Velocity 16 = light green
Velocity 32 = medium green
Velocity 48 = full green
Velocity 17 = light amber
Velocity 34 = medium amber
Velocity 55 = full amber
Velocity 18 = light orange (Lighter > red / darker > amber)
Velocity 35 = medium orange (Lighter > red / darker > amber)
Velocity 31 = full orange (Lighter > red / darker > amber)

The Competition, and the monome

Q. How does this compare to the Akai APC40 / controller XX / the monome as far as Live integration?

The most important point here is that you can easily mix and match. You can even have multiple control surfaces active, operating dynamically, at the same time, as well as multiple MIDI inputs for instruments. Also, most of the features of the Launchpad are available to all controllers. Novation is emphasizing the mix-and-match functionality of the Launchpad. Basically, the feeling is, there is no one control scheme that works for everyone.

The Launchpad is quite similar to the APC40. The clip functions are nearly identical, if in a slightly different (8×8) layout – you get the red onscreen rectangle, the red/green/amber LED indicators, scene launching, the ability to page through clips, and so on.

Basically, the major difference with the APC40 is trading functionality for size and price. The APC40 has the ability to map to Devices automatically, as does Novation’s own ReMOTE series; the Launchpad does not. The APC40 also has encoders, faders, a crossfader, and a number of shortcuts. On the other hand, you can get a lot of the APC40’s functionality in other hardware, meaning the Launchpad can combine nicely with other gear you already have.

One significant edge the Launchpad has over the APC40, though, is that the Launchpad is set up to play drum racks.

The monome is also capable of nearly everything you see the Launchpad doing, with the exception of the clip selection rectangle (though I find that a bit hard to see, personally). In fact, the pages on the Launchpad are clearly inspired (directly or indirectly) by Pages, a GPL-licensed, fully-free, Java-based tool for monome which even appeared in action on David Letterman with Imogen Heap.

You certainly have other options that provide dynamic, automatic control mappings, including the M-Audio Axiom Pro series, the Korg kontrol and nano series, Novation’s ReMOTE line, the Faderfox series, and various others. You can see the built-in scripts available on the Control Surface menu, and anything that supports MIDI can be adapted for additional functionality.

I expect that with the release of Max for Live, scripting custom control for other controllers should be more powerful, even if you don’t have Max for Live installed. Stay tuned in the coming weeks as I’ll be trying to get more complete information on this.

The Live API improvements should be especially benefit the monome project. And remember, the monome isn’t standing still. Because it’s open, it’s conceivable clever users could hack new features.

Q. Can I run monome software on it? OSC?

Yes and – no.

The Launchpad uses MIDI, not OpenSoundControl (OSC). That means you have to translate incoming, sometimes arbitrary MIDI numbers to useful information, and that the Launchpad can’t natively interpret messages in the way the OSC-native monome can. However, as noted in our APC40 hacking superguide, it is possible to use an emulator to translate between MIDI and OSC. That should also be possible with the Launchpad. One challenge is the extra buttons around the grid. I’m going to have to write some Java MIDI code that can map to an arbitrary array of buttons, huh?

Q. Does the Launchpad violate monome’s license and design? How is the monome licensed? How “open” is the Launchpad?

I don’t want to – and cannot – speak for the monome project. However, while the Launchpad is unmistakably similar to the 8×8 grid of pads on the monome, it is not a “clone.” It’s only superficially similar to the monome. Cloning isn’t necessarily healthy for design, but a certain amount of copying can be. Without the spread of keyboard layouts, for instance, we wouldn’t have any of the keyboard instruments we have today – and, indeed, before the standardization on the fortepiano, a lot of keyboard instruments were strange copies of one another. In modern design, the monome is itself indebted to the pad layouts on early drum samplers.

I mention the word “clone” because the Arduinome is an clone of the monome which is distributed non-commercially as a result. It actually duplicates major portions of the design, PCB, and protocol, which is not remotely true of the Launchpad. Because their intention was cloning (for the purpose of ready availability of parts), the creators of the Arduinome consulted with the monome project.

For the record, the monome’s software is released under an open source license, and it uses fully-documented, open protocols, including OSC. The hardware is not technically open source, but it is open to the extent that specifications for the hardware, PCB, and firmware are provided for customization and modification, and the construction of custom housing. You are restricted from using the hardware design to make your own commercial hardware, which means the monome doesn’t fit some more restrictive definitions of what qualifies as open hardware. But it does offer some components that are truly open source, and it affords a great degree of real-world openness for its users.

None of the “openess” of the monome is true of the Launchpad, which operates under more traditional and proprietary models. You can’t easily physically open the Launchpad case (and I expect you’d void your warranty if you did). It uses MIDI, an open protocol, but has a proprietary mechanism for interacting with Ableton Live (at least so far as I can tell). It uses USB, but does not support class-compliant operation – you must install your own drivers, which means you can’t use it with some devices (like Linux netbooks). And the process and operation of the Launchpad are not available or documented. That’s not to discourage the Launchpad, and you still have plenty of power via its MIDI implementation to keep you busy. But that does differentiate it from open hardware like the monome and the newer Livid Ohm64, and it’s worth considering how this difference impacts the ways you want to use the hardware. That issue is much bigger than any one piece of gear, and it’s one I hope we can cover in more depth.

More Videos

MusicRadar did their own hands-on:

Actually, judging by the LEDs, I think they were also working from a prototype and not the final production run. But you will also notice they have an L-shaped USB cord, which I believe is what the final unit will have. (And, heck, that’d be a useful thing to have around here, I may have to pick up some.)

Novation TV also has their own set of videos:

http://www.youtube.com/user/NovationTV

And DJ Tech Tools got a hands-on, too.

Getting handy with the $60 KORG Nano Series controllers and Ableton Live keeps getting more sophisticated. I did a "quick hack" using the text-based MIDI Remote Scripts with the nano as an example, and provided a download. Next, Raymond Weitekamp modified those scripts and added a monome for a full-blown Live performance. But now James Waterworth aka Myralfur takes the whole idea to the next level, with a fully custom set of scripts with control of additional channels, more control over tracks, and most importantly, interactive scene triggers.

I’ve built a custom python script for the nanoKontrol based on the hacked python scripts for the Axiom controller decompyled from live 7. It adds the ability to switch up to controlling channels 9-16 by changing midi channel (or changing up to scene 2 on the nanokontrol, which I had sending out on midi channel 2 instead of 1). It also has track on/off, solo/cue, panning, and also has the bottom row of buttons triggering clips on the relevant track, with forward and reverse skipping up and down scenes, and the loop button triggering the selected scene.

Best of all, you really don’t need to know – ahem – what you’re doing with scripting to make this work. Just follow the instructions below, and you’re ready to play – so you can get back to your set.

Now, James has polished off the script and fixed compatibility with Ableton Live 8, and this is ready for public testing. Give it a go and let us know what you think. I’ll work on a permanent home for all of this stuff, but for now, let’s just use comments for any issues. For some insane sounds, be sure to check out Myralfur’s music and DJ mixes on Soundcloud, too! He’s working on a rig that also incorporates a Sony PlayStation 3 controller.

nanoKONTROLMyr

A midi remote script for use with Ableton Live 8 and the Korg nanoKontrol.

Set-Up

1. Download and Unzip the file.

2. Move the nanoKONTROLMyr folder to the MidiRemoteScript folder within your Ableton Live application folder.

3. Open your Korg nano series editor and load the presets within the NanoKontrol Presets folder, over-writing your previous settings.

4. Select nanoKONTROLMyr as a control surface in the midi pane of the preferences window.

Mappings

Banks

Bank 1 controls tracks 1 – 8

Bank 2 controls tracks 9 – 16

Bank 3 maps the encoders to the selected device and provides functions for moving tracks and devices.

Bank 4 is free for mapping to whatever you like, sending on midi channel 4.

Global

The Ninth Slider is Always mapped to Master Volume, regardless of bank or midi channel.

The Ninth Encoder is Always mapped to Cue Volume, regardless of bank or midi channel.

Transport

Transport functions only work when receiving midi cc numbers on channel 16.

Different functions are called when in session view and arranger view for some of the buttons. The Loop button acts as a Shift to allow more functions to be called with the other transport buttons.

Loop = Shift

Play = Play (Scene Launch when Shift held)

Stop = Stop (Stop All Clips when Shift held)

Record = Record (Overdub On/Off when Shift held)

Session Specific

Rewind = Scene Up (Scene Up by 5 when Shift held)

Forward = Scene Down (Scene Down by 5 when Shift held)

Arranger Specific

Rewind = Cue Position Left

Forward = Cue Position Right

Encoders

The Encoders map to the Pans of the tracks. When sent on different midi channel numbers they map to different tracks. Channel 1 maps to tracks 1 – 8 and Channel 2 maps to 9 – 16 etc.

When sent on midi channel 16 they map to the selected device. This works in conjunction with the pads and buttons sending on channel 16 which provide functions for moving track and controlling devices.

Sliders

The Sliders map to the Volumes of the tracks. The tracks they are mapped to changes with the midi channel they are sent on. Channel 1 maps to tracks 1 – 8 and Channel 2 maps to 9 – 16 etc.

There is as yet no function for when they are sent on channel 16.

Top Row of Buttons

The buttons on the top row turn Tracks On/Off. The Ninth Button on the row acts as a Shift and when this is held the other buttons Record Arm the tracks. They function the same as the sliders and encoders in that they map to tracks depending on the midi channel.

However, when sent on midi channel 16 the buttons select and view tracks 1 – 8 mapping the encoders above to the first device in that track.

Bottom Row of Bottons/Pads

The buttons, or pads, on the bottom row Trigger Clips. The Ninth Button on the row acts as a Shift and when this is held the other buttons Stop the relevant clips. They function the same as the sliders, encoders and top row of buttons in that they map to tracks depending on the midi channel.

However, when sent on midi channel 16 the buttons provide various functions for controlling devices.

Button 10 = Track Left

Button 11 = Track Right

Button 12 = Device Left

Button 13 = Device Right

Button 14 = Bank 1

Button 15 = Bank 2

Button 16 = Device On/Off

Button 17 = Clip View/Device View

Download:

nanoKONTROLMyr.zip

Reminder: we’re meeting Saturday in Manhattan’s Meatpacking District to chill out, hear some music, and share strange and wonderful and hacked hardware controllers for Ableton Live as part of DubSpot’s Live Sessions tour. If you’re in the NYC area, you won’t want to miss out on music-controlling ironing boards, handheld controllers, and folks like RJ Valeo (Isomer Transition) above.

Full details
Facebook event

But if you’re not in New York, DubSpot and CDM are working together to make sure the weekend gets videoed, and we’re doing some work online.

Friday afternoon I’m chatting and answering questions as I work with the Live API to hack in OSC support for Live, and build a simple app for Google’s Android phone (which can be ported to other platforms, as well).
irc://irc.freenode.net/cdmblogs

Join the Noisepages Ableton Live hacker group for bleeding-edge discussion of some of these topics, too:
http://noisepages.com/groups/ableton-hackers
(I’ll be doing some link dumps with resources later today)

And Sunday, I’ll be giving a workshop about some controller secrets, with more to come online. (Sign up with promo code CDM for a discount if you happen to be registering at DubSpot; otherwise, hang out here.)

Novation’s Automap is coming to the iPhone – meaning a handheld device can provide interactive visual and textual feedback about what you’re manipulating in, say, an Ableton Live set.

Our friends at Hispasonic (Spanish-language) bring us the news. (Thanks, Xavier!) Photo credit: the new blog SaM’s burrow:

Novation Automap for iPhone in beta stage (first screen captures)

That gives you a closer look. I’m not even going to try to wonder what happened to Novation’s NDA. (We seem to be getting mostly “D.”) But, Novation, if you’re out there, trust me – buzz already suggests this is a good leak for you.

On the Ableton forums, some naysayers wonder why you’d want to run a Live set from an iPhone. The answer is, naturally, you wouldn’t – I think they’re missing the point. There are two larger issues here. One is, having a handheld device means there’s just another intelligent way to control your music set. It might be something you prop atop your keyboard or drum pad controller as a small dashboard, or that you carry with you so you can hear the sound in a venue during sound check. The other message is, interactive control with actual labels on parameters is the future for a lot of devices, not just the iPhone. That’s in stark contrast to the primitive way in which MIDI refers to everything in terms of (typically) meaningless numbers.

In fact, there are some promising other attempts to more easily see and manipulate clips away from your laptop screen, on devices like the Lemur. Thanks to the Live API (on which Max for Live’s control of Live is also based), it’s possible to finally get a full, controllable view of your clips. My only criticism would be that we still lack a single, open standard for this stuff. If Ableton Live supported OpenSoundControl (OSC) natively, it’d open all sorts of applications – without the hacking currently required. But that’s a topic for another day, and not just directed at Ableton.

Here’s the full text of this announcement from the Ableton forums. Stay tuned; hopefully we’ll hear official news soon.

Thank you for expressing your interest in the iPhone/iPod touch Application – we now have the first version ready for testing. Please follow the instructions below:

Installation:

*Please note, currently only compatible with Mac OS 10.5x (Leopard)*

The application allows you to use your device (iPhone/iPod touch) as a wireless Automap hardware controller over a WiFi network

Therefore first of all, your Mac which you use to run Automap, and your iPhone/iPod touch must be on the same network.

Once you have done this, you then need to do the following:

1) Download and install the latest Beta release (3.1b3) of Automap here: http://beta.novationmusic.com/automap/

2) Mount the attached volume “Automap_iPhone-1.0b1.dmg”, which contains two seperate files – “Automap_Testing.mobileprovision” and “Automap.app”

4) Open iTunes, drag the file “Automap_Testing.mobileprovision” onto the iTunes icon in the dock (you only need to do this once)

5) Drag the file “Automap.app” into your iTunes Library, you should now see “Automap” listed in your Applications within iTunes

6) Sync your iPhone/iPod making sure that “Automap” is checked in the Applications tab

Once this is done, launch Automap on your Mac, and launch the Automap application on your iPhone/iPod, you should see your Mac running Automap in the list of available servers.

Select the appropriate server, and begin controlling!

If you experience issues connecting to Automap, you may need to disable any Firewalls you have running (if using Airport you might want to set up a dedicated wireless network).

A few known issues so far:

+ Issue with HUI Pan control
+ Default HUI mapping/layout has not yet been created
+ Some web links are yet to be implemented

We have not included any user documentation as we are interested in your user experience with the Application alone.

http://forum.ableton.com/viewtopic.php?f=1&t=115761

Price: US$499 / EUR499 / street US$399
Availability: April/May (also about the same time you’ll see Live 8 – Max for Live coming later this year)

APC 40 FAQs, features and questions [Ableton Forum]

Since they were frequently asked around these parts, I want to single out these answers:

In one of the NAMM videos, somebody at AKAI proudly mentions a secret handshake between Live and the APC. But other reports seem to indicate that this unit just sends out MIDI. Does the device or Live send anything other than MIDI signals?

The APC Sends simple midi messages, and most of the banking and Session View control is handled internally in Live. Connecting another controller and selecting the APC40 preset will not work, even if that controller sends the same MIDI messages.

Will this secret handshake prevent us from turning a Monome + BCR into an APC?

Yes.

Will it be possible to use the APC with Live 7 out of the box with default mapping intact, or will I have to purchase live 8 to use the APC.

We’ll have a point release update for Live 7 with support for the APC40 in Live’s preferences, Live 8 will work with the APC40 when it is released.

So, you won’t be able to turn a monome into an APC – well, unless someone figures out a way to emulate the secret handshake. I’m guessing you curl your pinkies, then do a fist bump …

Of course, there are plenty of other interesting ways of integrating a monome with Live, some of which aren’t possible out of the box with the APC, and more should be possible with Max for Live (and other tools).

Photos/screens: Bryant Place. Used by permission. (Click for larger versions.)

Side note: for a look at live touch interfaces with Native Instruments’ Reaktor, see our story for our NI minisite. To really understand how touch is impacting live playing, I think it’s helpful to see what’s going on with different software platforms.

Multi-touch, Lemur, and Going Live

Part of the appeal of Ableton Live is that it behaves as a hybrid between arrangement software and musical instrument. Early versions even carried the tagline “Sequencing Instrument,” but that sums up the problem: instruments generally aren’t sequencers, and visa versa. To “play” your sequencer live is challenging enough, but added to that is the fundamental mouse-pointer interface that’s been in the marketplace for over twenty years. To really control live, you need more direct access.

The Lemur multi-touch hardware promised just such control when unveiled. In an early review, I saw this as promising but cautioned that the custom software the Lemur runs was overly rigid. Since then, firmware updates have gradually added more custom features.

On a recent trip to Los Angeles, I got to watch as Bryant showed off a set of templates he’s been developing that exploit these features for deeper, more interactive control of Ableton Live. Bryant’s session was brief enough that you could blink and miss it, but an awed crowd of assembled Live gurus revealed that he’d showed something really special. It’s a dream multi-touch setup. He’s using the new v2 firmware for Lemur, which we see in a screenshot from Jazz Mutant has also been used in their own template for Live. Not all the features come from v2 firmware, but those tabs make a big difference, and I can imagine continuing to go hog-wild with envelopes and such.

The basic idea: set up effects for live performance and make them readily accessible from the futuristic-looking, multi-touch, colored Lemur control surface. With a few compact screens, and interface elements that respond dynamically to what’s happening in software, it’s possible to use touch gestures to control elaborate effects arrangements in ways that would be very different than the results you could get from conventional knobs and faders.

Have a look at the pictures to really get a feel for what this means. I asked Bryant to describe to us a little more about how it all works. He cautions he’s “more of an engineer than a writer.” (Add “Damnit, Jim” to the beginning of that line, Star Trek fans.) But he actually has quite a lot to say, and you can feel free to ask some follow-up questions in comments.

Behind the Scenes with Bryant

My Live set is designed to take complete songs (preferably electronic dance music), and remix and affect the sound in such a way what I can take an original mix and completely transform its sound and rhythm.

I’m using only Live’s [internal] effects for the following reasons: stability, [efficient use of] CPU resources, tempo changes. I am thinking of adding some Sugar Bytes and possibly Audio Damage – we’ll see. [Ed.: Yes, I have to at least observe that third-party plug-ins are often as stable and sometimes more CPU-efficient – depending on the specific application.]

Some notes and tips, as I have learned building this project:

• Using the Lemur to control Live, which I can then do very quickly and naturally, has allowed me to discover the nature and quirks behind some of Live’s effects.
• Live and is amazing at changing tempo – especially evident when there are quantized auto-filters.
• Changing tempo while holding [instances of] Beat Repeat can cause some problems with the groove as Beat Repeat uses a good amount of audio buffer.
• Playing fast songs (for example, 135 bpm) at a slow tempo (e.g., 75 bpm) usually sounds weird. This can be somewhat enhanced by the following procedure: use two of the exact same audio clip, one using the "beats" algorithm and one using "complex." Together, they have a much better texture than you’d get using just one.

The signal flow and layout:

• Four Audio Tracks: I have four audio tracks for clips. Two A and Two B – I use the crossfader to fade between set A and B.  A1,A2,   B1,B2: These four tracks are "sends only"
• Seven Sends, with Pre-Configured Routing: I have seven sends.  A1,A2, are sent to sends: A Hi, B Mid, C, Low (the seventh send is simply a DRY track "G"). B1, B2, are sent to the hi mid lo sends D E F
• Effects Inserts: Sends Set A (ABC) and Sends Set B (DEF) contain independent auto-filters, multi-band compression tuned to their specific frequencies and auto pan.
• Effects in performance: The effects are controlled by the Lemur in a very magical way. :) (I spent a lot of time tuning the MIDI mapping)  This allows me to create a separate groove from the original song [using the resulting effects] – AND one that is frequency-independent.  (I had to compensate some things due to buffer limitations and CPU [utilization] for my MacBook Pro.)
• Returns, and More Effects: Next I take the sends and route them back to specific audio tracks.  I route A Hi to X Hi also D Hi to X Hi, and so on. This is where I add band-independent instances of [Ableton’s] Beat Repeat and Simple Delay. (By the way, these delays are far deeper than they seem on the surface.) I have full control of them using the Lemur – you can see the delay units in the images.  Lastly, I use a multi-ball object to control Hi, Mid, Lo. Chorusing tuned to their respective frequencies.  (When used correctly and with taste – the effect is mind-blowing)
• Recording: Lastly, I have my FIRE track which I use as a pre-Master (Xhi Xmid Xlow are sent to FIRE) – so I can record my performances.  I also use some mastering plug-ins to finalize the sound. [Ed.: Interesting, though I’d be inclined to do that after recording!]

The result is called LiveFIRE. I am using v2 Lemur Firmware but I haven’t used many new features — only the tabbed container object, color options, and other little tidbits. [Ed. That may be, but having worked in the Lemur editor, sometimes having just that one object you need can make a huge difference. If you saw an early revision, like the one I first tested, many of these objects are also the result of a series of new features.]

Technical notes: I can’t use my Live set to its fullest capacity due to my MacBook Pro’s limitations with audio buffer.  I have already scrapped my audio interface in turn for my integrated sound card – as it allows a larger audio buffer size. (This problem occurs only when I have audio on all four tracks playing at the same time.)  [Ed.: I’m actually not sure about this detail; we’ll have to discuss it more. Switching to internal audio is usually the opposite of what’s necessary, so we’ll have to have a separate conversation about exactly what’s going on, what the symptoms are, and what the cause may be. An inability to get a sufficient audio buffer, or problems running out of CPU horsepower to complete the tasks, would be symptomatic of either trying to push the envelope a bit too far with the set or encountering some driver-OS-software issue. Then again, it sounds as though Bryant is intentionally modifying the buffer to get certain results – an interesting and unorthodox technique. We’ve kicked off the discussion, so we can look at this some more.]

My future plans are to naturally incorporate the LiveAPI, which will take some time and a lot of remapping. [Ed.: The Live API is a user-supported way of customizing functionality in Ableton Live – it’s a hack, and requires a bit of Python coding knowledge in order to make it your own, but it’s a very powerful outlet and well worth revisiting here later.]

I really look forward to continuing this discussion. What would your ultimate touch controller look like for Ableton Live or other software? Or would you rather dump the touch and stick with tangible hardware control?

Fans of Star Trek: The Next Generation saw this coming – computer display interfaces were destined to allow direct touch from all your fingers, with no mouse or stylus or clunky single-point interface intervening. Jazz Mutant’s Lemur multi-touch hardware was arguably the first widely-available commercial solution to enabling this kind of control of music and performance. Now, several years after the launch of Lemur, multi-touch is mainstream. Apple’s iPod touch and iPhone already support it in hardware costing as little as US$200. Microsoft promises built-in support in Windows 7. HP says computers and displays are imminent. Many others will follow.

But if you want multi-touch to work for music, what’s the best approach? The dedicated multi-touch Lemur controller (and its Dexter sibling) has won over support from some musicians and multimedia artists for specifically catering to their needs. Various celebs have been spotted using them – recently we saw Justice rocking a pair in Rio.

What defines the Lemur is that you don’t use it like a conventional display. Instead, you create interfaces from pre-defined building blocks – the virtual equivalent of adding physical faders and knobs to DIY controller hardware. To me, that’s been paradoxically both its strongest and weakest point. The strength is, the display focuses on controls that make sense for performance and can be easily manipulated with fingers. The weakness is, you’re limited to these widgets – and, increasingly, the Lemur has to compete with mainstream hardware displays that have no such limitations. As mainstream hardware grows, it puts more pressure on Lemur.

In the meantime, though, Lemur’s creators keep improving the available widgets. The biggest firmware update yet, v2 has just hit beta, with the finished firmware available by the end of the year. It’s a free update for Lemur owners, so a no-brainer there. New in this release:

• Breakpoint object for manipulating multi-segment envelopes
• Gesture object: gesture recognition, pinching, rotating, and finger tracing
• Tabbed container: Now, instead of switching endlessly between control pages, you can fit different sets of controls into tabs
• Mouse/keyboard remote control: keyboard shortcuts and mouse movements now become possible directly from the Lemur

In addition, it’s easier to edit Lemur pages more quickly, aliases of objects save memory, and multi-line scripting beefs up custom options.

It’s really good stuff, which makes me wonder: does Jazz Mutant have the ability to support other third-party hardware if it becomes available?

In the meantime, there isn’t actually any direct equivalent for the Lemur, at least not with this screen size. I imagine those with the cash who want to use a futuristic interface rather than just speculate about it will continue to snap up Lemurs. For the rest of us, it’s interesting just watching the development.

Jazz Mutant [Company Site]