Minor releases and bugfixes don’t generally make CDM news, but this is a special occasion. Ableton founder and CEO Gerhard Behles got everyone’s attention this week by making the rare public announcement that Ableton’s development team was temporarily halting work on new features to focus on fixing bugs. That has prompted some seriously impassioned discussion, on the Ableton forum but also here on CDM. Look past some of the hyperbola and name-calling, and you’ll see some insightful comments on both sides. In fact, the whole affair reveals a lot about how music software customers view bugs, updates, support, release cycles, and pricing – developers, take note. Naturally, some of the disagreement comes from whether or not users are experiencing bugs: those that aren’t, as always, are happier. But there’s some common ground, too.

Also sobering: read further into comments, and you’ll see who can really lose out in credibility when stuff doesn’t work the way people expect, even more than a developer – music tech journalists (so, um, yes, folks like me). Not to apologize for myself or my colleagues, but one challenge has long been that it’s difficult for one user to find reliability issues. As the comment thread itself demonstrates, some people are blissfully happy whilst others are in absolute agony; look through the specifics of the changelog, and you’ll see why. One person, based on their behavior in the software, could see dramatic, regular crashes, while another sees nothing at all. Now, CDM has an advantage there – we can operate 24/7/365, we don’t have a weeks-long delay waiting for print, and we have a complete feedback loop with you. If you’re finding issues, I want to hear about them.

New release: Late yesterday, the 8.1.1 release moved from beta to final release, meaning you can go grab it now from the latest releases download section. Synthtopia has posted the full changelog.

Some highlights:

• Fixes various problems with the integration of Novation’s Launchpad
• Fixes a number of somewhat specific but showstopper crashes, like “Loading a Max device would crash if Pluggo was already active. I count fifteen instances of the word “crash,” which is a serious issue.
• Begins to address some reliability/performance issues with Drum Racks; specifically, “Having a Live set with particular Drum Racks could increase the CPU usage of the main thread, which would result in very slow graphical updates.” Because of our fondness for Drum Racks, both Dave Dri and I have run into performance problems that would lead us not to use this feature onstage.

I think it’s difficult to make a sweeping statement about something as relative as the reliability of the software. What you can say is that Ableton themselves have acknowledged this set of releases isn’t up to their own expectations, they’re committed to working on improving the situation in exclusion of other factors, and bug fixes are now coming in a steady stream.

In fact, “beatsme” in comments counts up the fixes since the Live 8 release on April 2 of this year, marking 42 improvements (0.16/day) and some 261 bug fixes (nearly one per day). You can read into that whatever you like, but the bottom line is, those issues are now fixed.

8.1.1 is apparently not the release to which Gerhard was referring when he talked about halting forward development; we expect fixes to continue to appear over the coming weeks.

Of course, all of Ableton’s DAW competitors release similar point updates, so any question about the relative reliability of Live should also be asked of other software, as well.

I do have one concern, too: with so many fixes relating to the integration of Ableton’s Launchpad and APC40, why not focus controller features on tools that will work with any hardware? And why not allow users to customize scripts? Many in the Ableton forum are capable of devising their own solutions and providing their own support for those solutions. I don’t think that’s unreasonable to ask, because many applications have focused hardware controller support on generic solutions in this way. I don’t believe there’s a “right answer” to that question – Ableton has made a decision they think makes sense, and that allows them to devote resources to supporting certain hardware units above and beyond what they previously had basic MIDI controllers. But I would still like to see controller support in Live in general mature beyond where it is today.

About those new features… Many readers have asked whether the emphasis on bug fixes will have any bearing on announcements at the NAMM conference in January. I haven’t heard any indication of that; Ableton is planning a party with Serato, and I still expect we’ll see an Ableton-Serato announcement on Thursday, January 14. I’ll be meeting with Ableton at the show to talk about that and any other news.

Other releases: We’ll keep an eye out for other releases, and will check in with Ableton for a big picture of the situation in a couple of months after some of the development dust settles.

Your mileage may vary: Please, if you’re testing new Live versions, let us know your experience. Be specific. And be sure to follow up with whether a thread tracking this bug is open on the Ableton forums.

New features are great, and yes, it’s often us users asking for them. But reliability and stability are more important to most of us. It’s therefore a welcome surprise to see Ableton’s CEO post the following message on Ableton’s forum today, announcing that the company will put new features on hold until some reliability issues are fixed. For developers other than Ableton, it should be telling to see how users respond — if this kind of frankness inspires confidence rather than concern, it could mean that talking more openly about bugs and how to fix them could open up more dialog between developers and users:

Update, 12/29: One release with some fixes is already available, in the form of 8.1.1. It appears to address a showstopper bug I personally encountered with Drum Rack performance under certain situations. I’m testing that fix and others. I don’t believe this is the only update to 8.x that Ableton is planning, or the one to which this message refers, but it is a start. Check out the downloads page.

Some of you have experienced and reported problems with Live 8 several months ago that we have still failed to fix. This is both painful and necessary for us to discuss. We owe you sincere apologies, as well as an explanation and outlook for the future.

Ableton values quality over innovation. Our engineers will stop whatever they are doing to fix a bug when they become aware of it. They must, however, rely on a process that prepares the incoming information and funnels it to them appropriately. Establishing and maintaining this process is the responsibility of management — particularly us, Bernd and Gerhard — and this is where things have gone wrong while we let our attention divert to ambitious new projects.

Our apologies also extend to both the Ableton developers and tech support colleagues because they want to be proud of software and service that users love.

We have now decided to:

• suspend all development towards new features while the whole team joins forces to address the current issues. This effort is open ended and will result in a free Live 8 update;
• make process changes to prevent similar situations from happening in the future.

We hope this plan finds your understanding and agreement. We’d like to wish you a very happy holiday season and a wonderful 2010!

Gerhard Behles, CEO
Bernd Roggendorf, CTO

Pausing forward development to focus on bug fixes in and of itself is not an unprecedented move – it’s just usually not something you talk about. So I have to applaud not only Ableton making the sacrifice to focus on reliability first, but also that they’re being frank about acknowledging issues. I’m honestly not entirely certain just which issues they’re describing, because I don’t have the benefit of the big picture that comes from handling Ableton’s own tech support. Once Ableton does make progress on this upcoming free update, though, I’ll be sure to share what changes are included.

As seen on the Ableton forums, via Bjorn Vayner / The Covert Operators on Twitter.

Clarification: I should hasten to add, as I realized this post could be misread — talking about and fixing bugs is a good thing, but having bugs is not. Ableton, as any music developer, depends on the goodwill and trust of its users. If in fact bugs have made current Live versions less stable, or have adversely impacted the perception of Live, that leaves the ball in Ableton’s court to resolve. To me, the proof is in the release. If you have issues you’ve fully documented that have not be resolved, to which this post may be referring, we’d love to hear about them (emphasis on “documented” and “fully” — let us know exactly the issue and how to reproduce it). Likewise, we’ll watch for fixes. All software has bugs, and being a computer musician means being able to manage reliability and stability to make the computer an effective instrument.

As the company turns 10, Ableton has introduced a set of discounts and giveaways, the most notable of which is a new entry-level edition of Live. Live Intro smooths out a lot of the wrinkles between different starter versions of Live, from LE to hardware bundles. At $99, “Intro” finally gets a logical feature set:

• Full ReWire support, both as host and client (or “Slave” and “Master,” if you want to be all kinky about it)
• Full MIDI support, including remote control, output, MIDI clock (though none of the nifty “external device” support for outboard gear)
• Warping and time stretching, minus the “Complex” and “Complex Pro” modes
• 4 VST/AU instruments, 4 VST/AU effects per project
• Missing Vocoder, Looper, Multiband Dynamics, Overdrive, Frequency Shifter – but you do get SImpler and Impulse
• 2 in, 2 out audio, though you can have up to 64 tracks and unlimited MIDI tracks
• No track grouping
• Full WAV, AIFF, MP3, Ogg Vorbis, FLAC support
• New extras: 7 GB of audio content in the boxed version, 1 GB in the download version

In other words, you get a more-than-capable version of Live for a hundred bucks. It’s certainly enough for anyone who just wants to inject some Live functionality into their ReWire host of choice, and allows people interested in experimenting with Live a non-crippled version they can use. Mercifully, Ableton is offering a free upgrade to Intro from Live LE users — a good thing, because Intro includes some features and content LE lacks. (Okay, it’s still probably not great news if you spent $200 on LE, but at least you don’t miss out on the features.)

Live Intro product page
Live Intro comparison

Sound Packs, Discounts

Already a Live owner? Through January 10, Ableton has a number of deals for existing Live users:

http://www.ableton.com/able10

Discounts on Live upgrades, up to 20%

Free artist packs — from some wonderful artists, too, including Apparat, Mum, Thavias Beck, and our friends at Covert Operators, among others.

The artist packs are especially nice. And Novation is shipping the Launchpad. Of course, the big news today is really Max for Live, so I’d better … keep typing. (Damn you, fingers!)

A monome-like grid controller built for Live, shipping in November for $199 – and I’ve got a first hands-on look with the hardware.

The feature that makes Ableton Live Ableton Live has always been its Session View, an array of Lego-like blocks of music triggering samples and patterns. In the grand tradition of the MPC, mapping hardware controls that make music non-linear has been a major theme of computer music, leading to the monome and the Tenori-On. Usually, consumer gear has only combined these with traditional drum pads, knobs, or faders.

Enter the Novation Launchpad. It’s $199. It’s a grid controller and nothing else, with a set of on/off buttons in an 8×8 array, plus additional shortcut buttons around the sides for switching modes. It’s set up out of the box to integrate with Ableton Live, but it also acts as a generic MIDI controller. It’s bus powered, really lightweight, and compact. Even following Akai’s earlier APC40 this year, there’s something special about the Launchpad: its radical simplicity, and the fact that it is this compact and cheap and plugs in via USB without power, makes this a potential no-brainer for any Live user with a laptop.

I’ve just gotten one of the first Launchpads to arrive (unit “#16″ on the back), so I’ve been playing around with it and can provide some initial impressions and details. I’ve also gotten input from Ableton’s Dave Hill as well as Novation, and I expect to fill in more soon.

monoming the sincerest form of flattery? Of course, one design more than any other championed the radical idea of a minimal grid of buttons — and nothing else. That design statement was the partially open-source, fully-homegrown monome. I’m sure as a result Novation will be accused of ripping off the monome design. I think the opposite: I think the availability of the Launchpad is a huge victory for monome, and an enormous compliment. More than any other design – including the APC40 – the Launchpad really says that an affordable, mass-market device can take on the monome’s radical form. It says grids could become ubiquitous. It’s an enormous validation of what the monome project has done. Furthermore, I think the monome community can continue to reinvent what to do with grids, with software and interaction. There are also many things the monome is – locally produced, sustainably produced, running with open source software, fully community-supported, available in kit form, working with OpenSoundControl, built in a premium form factor – that the Launchpad is not.

[edited for clarification] I think the Launchpad is unlikely to dissuade a person who wants a monome from getting a monome. But what’s significant here is that the design of musical instruments and controllers can adopt new forms. The monome was seen as radical when introduced. It seemed as though the music tech industry wouldn’t produce anything without slapping on some arbitrary knobs somewhere. The Launchpad really does follow the monome’s design cue, and maps control in Live in some new ways. That gives me hope that other designs could likewise tread in new direction, both from independent and larger designers.

Onto the details… The big picture aside, here’s a first look at how the operation of the Launchpad works. I’ll have a short video a little later on today.

Control Modes

The Launchpad has a series of modes that act allow the single 8×8 grid to perform multiple duties. Different modes and shortcuts bring up different visual feedback (by lighting up the buttons) and allow you to control different parameters.

Session mode

In Session mode, the Launchpad does exactly what Akai’s APC40 does. You can trigger clips and view clip state (playing, recording, ready, empty) by color (green, red, amber, and off). You can trigger scenes. You also get the red rectangle that highlights which bank of clips is active.

Unlike the APC40, though, the Launchpad is cheaper, smaller, thinner, lighter, and bus-powered. You can pick it up like a tablet, or squeeze it into a small club space. You can also easily chain multiple Launchpads together (or Launchpads and APC40s), so long as you have enough ports or a USB hub.

Multiple units can simultaneously access integrated control surface functions and clip triggering in Session View. So, for instance, you could have two Launchpads controlling clips, or one controlling the mixer and one controlling clips, or… you get the idea.

Mixer mode + parameter pages

Hit “mixer,” and you see an overview of all your tracks, eight at a time. (You can navigate through your set using the “page” buttons.)

Each row has a different function:

• Volume
• Pan
• Sends A + B
• Stop clips
• Track on
• Solo
• Arm

The “stop” row allows you to either stop an individual track or stop all clips by hitting the “stop” button itself on the right. Solo, arm, and track enable are self-explanatory.

Where things get a bit cooler is if you press the “snd A,” “snd B,” “pan,” and “vol” controls. These allow you to use each column to set parameters. So, for instance, if you want to adjust the send level on your second track, you’d hit “mixer,” then “snd A,” then use the second column to adjust the send up or down. You can fake a “fade” by dragging your finger up or down the column. Now, this doesn’t give you the continuous control a knob or fader would; there’s no interpolation between values. On the other hand, if you’re trying to create stepped, rhythmic changes, that could make the Launchpad (or any grid controller, including the monome) more interesting.

User mode

“User modes” provide open access to the pads for use as MIDI inputs. By default, “user 1″ sends MIDI note messages, and “user 2″ sends control change values.

In the video, you’ll see these modes used for some crazy things, like programming in a sequence and having it continue to light up as you add other layers. In my test – keeping in mind launch date is still over a month away – I couldn’t replicate any of these behaviors. Some of this interaction may require the upcoming Max for Live; I’m awaiting confirmation on details.

In the meantime, you can at least use the Launchpad as a MIDI input in Live or any other software.

Use with other software

Every single button on the Launchpad sends MIDI; I opened a MIDI Monitor session on my MacBook while testing it. There’s not a single menu key that doesn’t send a message. Also interesting: each sends both an on and an off value, which makes it more useful as a button.

It should also be possible, as with the APC40, to use MIDI to light up the Launchpad, complete with color and limited dim levels. I’m assuming the mappings may even be identical to the APC40. I don’t know yet how to do this, however.

Another big selling point for Novation, of course, is Automap support. Along the top, there are alternative labels for the buttons: learn, view, page, instrument, fx, user, and mixer. These will work with Automap and Automap Pro, in case you want to use another host or map to third-party instruments and effects. I didn’t get a chance to test this functionality yet, however.

Physical form factor

The Launchpad feels really good. It’s thin, it’s light, it’s easy to toss in a backpack (as I did today), and yet the plastic case feels very solid. The pads feel good, though I find the throw a little long, making them rock slightly if you don’t hit them dead-center. Angled pads indicate the center, and four pads around them have slight nubs on the surface for additional tactile feedback.

Rubber strips underneath the unit help grip surfaces.

One possibly unfortunate decision was to put the USB port on the side rather than the top, which means you can’t easily put two Launchpads side by side.

Software

The Launchpad ships with a copy of Ableton Live Launchpad edition (aka Live Lite), version 8.0.6. On both my Mac and Windows boxes, I simply installed that version and it automatically found my full Live license. I expect that the 8.0.6 build will get pushed to everyone else in time for launch.

You select the Launchpad as other control surfaces, by looking for “Launchpad” in the Control Surface menu. This presumably means that, like the APC40, a software handshake is used to enable the red clip selection box. I’d still like to see a universal solution from Ableton, one resizable to other controllers. Why not plug in a 4×4 drum pad and bank through clips in a 4×4 rectangle instead of an 8×8 one? The red rectangle is also limited in that it’s tough to see which tracks are selected. (It’s also kind of tough to see, period.) That’s really become an Ableton complaint, though. I’m sure we’ll be working on Max for Live and Live API solutions for heads-up displays that replace all of this soon.

Questions and Initial Impressions

I like the Launchpad a whole lot. Sure, it doesn’t have knobs or faders – but you could throw the Launchpad into your backpack alongside a KORG nanoKONTROL, using the Korg for your fader and knob tasks while the Launchpad launches clips, triggers drum pads, and gets used for live sequencing and playing instruments.

I am a little disappointed that there doesn’t seem to be a way to control Devices. I’d like to be able to take the User Mode and use my eight columns to control the eight macro knobs on any active Device. Sure, you only get 8 values of resolution, but you could set up a Device so that those eight values were musically interesting. I’m investigating whether this is possible; if not, I may look into hacking a solution.

I still think there’s a big place for open tools. The Launchpad is already touting forthcoming use with Max for Live, but that’s only because it sends MIDI messages – and anything else that can send MIDI (or OSC, via work from the Live community to use it) will do the same. I think those of us working on open interaction, though, can find ways of building stuff that works in open tools and closed tools (Java, Pd, and the like are open, Max is not), and open and closed hardware (monome, Livid’s Ohm on the open side, things like the cheap-and-light Launchpad on the proprietary side). Having lots of grids could be a good thing. If everyone has the same thing, the pressure is on to make your performance different from everyone else’s.

But the bottom line is, I think this is going to be a huge hit with the Live user base. And even more than the APC40, I think it’s cheap, an easy impulse-buy, extremely compact, and complements other hardware. It also looks like it’ll be a terrific live visual controller for people who moonlight between music and visual sets.

Since I do have this Launchpad here well over a month prior to launch, and some folks at Ableton and Novation ready to share, if you’ve got questions or concerns, please don’t be shy.

The KORG nanoSERIES has a rabid following among many Ableton Live users, and with good reason. The nanoPAD and nanoKONTROL street for about US$60, provide basic knobs + faders + transport (KONTROL) and pads and X/Y control (PAD), plus a fully-featured, cross-platform editor, but still fit in a backpack. They’re small enough to use in coach on an airplane.

Having to open Live templates, however, just to get the mappings you want is a big pain. So, instead I’ve created a basic set of MIDI Remote Scripts and Kontrol Editor templates for Mac and Windows, Live 6.x and later, and wanted to share them with you.

If you’re Windows-based and a big fan of the nano, I will say that I recommend you use something else altogether – the brilliant nativeKontrol. It’s a hell of a lot more sophisticated, gives you more control, and still requires no template:
nanoLive

Of course, there are some advantages to my (otherwise inferior) humble solution. It’s free, it works on Mac, it’s completely editable, and much of the idea was to provide an easy way of learning about MIDI Remote Scripting. (Check out the tutorial below.) Now, knowing CDM readers, I imagine someone out there can improve what I’ve done, so feel free to modify it and please send us a copy of what you’ve created!

korgnano_live.zip [Cross-platform archive; will update with a fancier release later on once I've gotten some feedback]

Ableton Live MIDI Remote Scripting How To: Custom Korg nanoSERIES Control

And, of course, read all the instructions…

Install instructions:

1. For full control, upload the templates to your Korg nanoSeries using the Kontrol Editor, via the Communication menu. (See your manual for more.)

2. Place the proper folder(s) in your User Remote Scripts folder, inside your user preferences folder (NOT the Live program folder). That’s something like (Windows Vista/7):

[Windows boot drive] > Users > [username[ > AppData > Roaming > Ableton > Live [version] > Preferences > User Remote Scripts

or (Mac OS)

[boot drive] > [Library folder] > Preferences > Ableton > Live [version] > User Remote Scripts

3. Start Ableton Live 6.x or later (restart if it was already running)

4. Select the device. Choose Preferences > MIDI/Sync, select Control Surface in the first column (nanoPAD or nanoKONTROL), and then its Input and Output ports. Finally, enable the Control Surface Input for Track and Remote. Note that you can have more than one control surface, so if you’ve got both nano’s plugged into a hub, set them both up!

Usage instructions

nanoKONTROL Scene 1 is for device control. The buttons act as triggers for pads in drum devices, and the faders control the eight Macro encoders in any selected Rack. You’re free to assign the scene 1 knobs to whatever you like.

Scenes 2-3 control tracks: the top button record arms tracks, leaving the button button free for whatever you like (mute, enable/disable). The faders control level on tracks 1-8, and knobs control the first send for each track.

Scene 4 is basically unassigned and ready for custom assignments.

Across all scenes, fader 9 is the master level. Transport buttons are automatically mapped and will work as expected.

Because there are so many controls free, I’ve created a sample template that pre-maps some parameters. In case you prefer to work that way, that template can get you started.

nanoPAD: The nano is much simpler, but I’ve set up the X/Y pad to dynamically trigger the first two parameters in a rack, making this much more fun to use with a Drum Rack. I like having access to all 8 Macros, so I’ve spread them across the four scenes. The pads will dynamically map to the first 16 pads, with 1-12 on scene 1 and 13-16 on the top of scene 2. There was some trickery to allow you to map these pads more or less as you see them in the software, beyond those first 16. I’ve provided alternative versions that allow easier continuous melodic control or keep CC 1 + 2 consistent across all four scenes.

(I didn’t say that very well, so if anyone’s feeling really motivated and wants to do a quick post or video of this or even modify them and make them better, feel free!)

To avoid accidentally triggering parameters with the X/Y pad, you can either turn flam/roll mode on all the time, or make sure instruments you want to play are added to racks first.

For more detailed instructions on Live setup and how MIDI Remote Scripts work, please see the separate tutorial!

Scripts for KORG nanoSERIES and Ableton Live by Create Digital Music is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.

Want to help motivate me to do more stuff like this? (I and others on Planet CDM really will — open to non-KORG, non-Ableton requests!)

When software has “Live” as its name, you know control will be everything. So it’s great that many control surfaces will behave intelligently out of the box with Ableton Live, including devices like the Akai APC40 and Novation ReMOTE SL. If you’ve used one of these products, you’ve no doubt been able to click a device rack in Live and have a blue hand icon appear in the title bar, automatically assigning, say, the first eight macro knobs in a drum rack to your eight hardware encoders.

But what if you have hardware that isn’t covered by this functionality that you want to use? The easiest solution is something called MIDI Remote Scripting. It’s been available since Live 6, but it seems not many people know that it’s there or how to use it. It’s not a perfect solution, but it’s such an easy hack that it’s worth at least exploring.

For this tutorial, I’ll take the example of the Korg nanoKONTROL and nanoPAD. They’re a likely candidate, at about US$60 street each and with some handy controls (kontrols?) for mixer channels and drum racks. But you could take any hardware and apply the same technique — even something you’ve built yourself — so long as it sends simple MIDI messages.

The upshot: you get simple “automap” functionality without something specific like Automap (or drivers, in general).

Required for this tutorial: Ableton Live 6.x or later. I’ve tested only the full version of Live on Mac and Windows, though I think at least some of the “lighter” versions should work, as well.

This is a long article but a relatively short and easy process. I’m just giving you everything you could possibly want to know about the nanoSERIES and MIDI Remote Scripting!

Introducing MIDI Remote Scripts

Ableton Live uses compiled Python scripts to provide custom support for controllers, as I understand it. I’ve never looked into this specific functionality, and generally you wouldn’t unless you’re a hardware vendor working with Ableton.

As of Live 6, though, there’s a hack provided for everything else, called MIDI Remote Scripts. They’re simple text files that let you specify mappings of MIDI note, Control Change, and channel messages to common parameters in Live. This text file is compiled into a Python script for the hardware when Live launches. Basically, the Remote Script covers:

• The 16 visible pads in Drum Racks
• Device Rack encoders (the 8 Macros for each Device Rack)
• Bank parameters for switching between banks of encoders in devices that aren’t in racks
• Volume faders 1-8, plus the master volume setting
• Sends for tracks 1-8 (just the first two sends)
• Track arm buttons for recording into tracks 1-8
• Transport controls

Now, if you’re not familiar with Device Racks and Drum Racks, and how to use them for instruments and effects, you should absolutely go brush up now. Really, go ahead – I’ll wait. The rack functionality introduced in Live 6 is essential, because it allows you to take complex sets of effects and instruments and map them intelligently to just eight controls.

You’ll notice there’s plenty of stuff that’s not on here. There’s nothing to do with clips. There’s no way of banking up to track counts higher than 8. There’s no way to easily bank between sets of pads in Drum Racks with more slots. There’s no headphone level. There’s record arm, but not track enable/disable. I could go on…

But you do get a pretty decent base set of functionality if the list above looks appealing. Since you’re just using MIDI, you can manually assign any additional remaining hardware MIDI controls to your favorite parameters.

And the most important thing about all of this is that parameters for the Device Rack are dynamic. So while there are eight of them, that covers any selected device anywhere in your set. Click on the device, and the blue hand lets you know the device is under your control. Whichever controls you’ve chosen — say, eight huge mechanical knobs on a DIY hardware controllers — will map automatically.

Finding and Editing the MIDI Remote Scripts

I do mean finding. Your first job is to find the MIDI Remote Script location on your drive.

First, here’s where it’s not: it’s not in the Ableton program folder itself. There is, in fact, a User Remote Scripts folder in there, but it’s not the one you want to use. (I bring this up only because I tried to put my customized text file in that folder, had my script show up in Live’s preferences, but then couldn’t understand why nothing was working. Learn from my mistake, and be wiser.)

Instead, you’ll want to navigate to your user preferences folder.

On Windows Vista/Windows 7, my Live preferences live in:

[Windows boot drive] > Users > Peter > AppData > Roaming > Ableton > Live 8.04 [or your version] > Preferences > User Remote Scripts

(Yours may be in Local rather than Roaming, depending on whether you installed Live for all users. On XP, the path is similar, but in your boot drive’s Documents and Settings.)

On Mac:

[Library folder] > Preferences > Ableton > Live 8.04 [or your version] > User Remote Scripts

Note that on the Mac, in similar fashion to the Remote/Roaming difference on Windows, you may need either the Library folder at the root level of your boot drive or the Library folder inside your user folder (the one you see when you click Home, Documents, etc.).

You’ll find two files in that folder. One is a how-to text file, as pictured above, though it doesn’t tell you that much. The other is a sample file.

To create your custom script, you’ll want to duplicate the UserConfiguration.txt script and place it in a folder with the name you want to appear in Live. So, for my custom nanoKONTROL script, I have:

User Remote Scripts > nanoKONTROL > UserConfiguration.txt

Note that the new file will still be called UserConfiguration.txt.

Customizing in the nanoSERIES Editor

Let’s take a quick side trip to set up our KORG nanoSERIES controllers the way we want.

Out of the box, the KORG nanos don’t come with any software disc, because you don’t need them – just plug them in, and they work. And, in fact, if you’re happy with the default MIDI assignments, you never need to go beyond this. In this case, though, I was interested in remapping some stuff, particularly on the nanoKONTROL buttons, so I went ahead and started editing.

You can head to the Korg Nano site and navigate through support, or even easier is to head to this direct link:

Support Results for nanoSERIES

(If you’re outside the Americas, there may be a different link.)

Click Downloads and choose Kontrol Editor for Mac or PC. (You may also want to grab KORG’s own USB MIDI Driver.)

The Kontrol Editor is really quite nice to use and surprisingly powerful for a $60 piece of hardware. At the top, you’ll see buttons for the scenes on the nanoPAD and nanoKONTROL. There’s a visual representation of the controller which, by default, displays MIDI Control Change and note number assignments. (To change what this preview displays, select the dropdown just below the picture of your nano.) The Browse tab allows you to navigate your file structure, but keep Control selected to change assignments.

You can safely ignore the boxes above the controller for now, which control scene settings and channels. Instead, focus on everything on top of and below the controller. On the nanoKONTROL, the faders’ CC assignments are just below the faders. (Look carefully; that can be a bit confusing at first.)

I’m providing my download of my template, so you don’t have to muck with this, necessarily. But here was my strategy:

nanoKONTROL I was most interested in reassigning the buttons next to the faders. Selecting “Momentary” lights up the button only as you’re pressing it; “Toggle” has it turn on and off. Note that this doesn’t actually impact the messages it sends; just the lights. For Scene 1, I wanted these buttons to double as triggers for my drum pads, so I changed all of them to Assign Type: Notes and adjusted Button Behavior to Momentary. For the remaining scenes, they’re record arm buttons, so those I left as Control Change assignments and Toggle behavior.

The tricky part of this is that KORG has nine faders and encoders instead of eight, and everything in Live is grouped in eight. I made the ninth fader a master. You might manually assign the knob above that ninth fader to headphone out.

nanoPAD All the fun in the nanoPAD editor is to be had on the X/Y controller. The two boxes that are pre-assigned represent X control and Y control on the pad. The third box allows you to define an additional controller for touch across the whole pad. On the pads themselves, note that you can assign up to eight(!) control change or note messages, not just one.

For this project, I just wanted to adjust the note settings to map more intelligently across my Drum Racks, which I’ll explain with the download. That means, unfortunately, going through one by one and changing pitch assignments. For the pad, I’m of two minds. You can keep those CC assignments consistent across all four scenes, or use each scene to control different parameters for a total of eight (conveniently, the number of macros on a Live Device Rack) Note that the scene descriptions at top are just text you add, so the “Drum Kit” or “Chromatic” labels are really just suggestions; they have no functional purpose. You can change them if you want, but the editor is the only place you’ll see them.

User Configuration Settings

Lastly, let’s walk through the changes to make to UserConfiguration.

[Globals]:

For InputName and OutputName, it’s essential that you match exactly the text listed by a MIDI device when it’s connected to your computer. For the nanos, that’s “nanoPAD” and “nanoSERIES.” You can verify this by opening your Live preferences and checking under MIDI.

You also need to double-check your GlobalChannel. Numbering starts at zero, so channel 1 is channel 0, and 10 is 9. You can plug multiple nanoSERIES devices into a USB hub — even an unpowered hub, the power draw is so low — so I like to assign different channels to different devices to avoid confusion.

In the rest of the document, any channel that references “-1″ is equivalent to the default. For that reason, I recommend leaving channel assignments along and just changing the default global channel.

Pads and Device Controls

Here’s the fun part: you can set up pads and Device Controls (Macro) encoders to dynamically control the active device. Choose note messages for the pads, and Control Change messages (with the associated numbers) for the encoders.

Here’s the trick: you need to have everything assigned, or it won’t work. In other words, you can’t assign just the first few encoders or just the first few pads, or, oddly, Live will refuse to recognize this as a mappable device.

Banks and Locking

I didn’t find Banks as useful. Banks allow you to choose banks of unassigned controllers. That can get confusing, though, so I still recommend using Device Racks to manually pick and choose which macros you want assigned.

There is, however, an assignment for LockButton. This allows you to pick a button that will “lock” your dynamic controls to one device. So, for instance, let’s say you have a rack of effects you want to control with your nanoKONTROL. When you’re at home in the studio, you might want to mouse around and click different devices for tangible control. But live onstage, you want just one live performance effects rack. Lock the device, and you won’t accidentally click something else and lose control.

I didn’t assign this on the nanoKONTROL because there wasn’t a convenient parameter to assign, but you can still lock a Device from within Live.

[MixerControls]

This gives you limited automatic control of mixer levels (for channels 1-8), sends (1-2 for each of those channels), record enable (for arming tracks), and the master mixer level. I like having a master to control, so having that ninth fader on the nanoKONTROL wound up being very nice.

Now, it is a little annoying to be limited to eight tracks, but there are two important factors here. Firstly, this is a dynamic assignment, meaning you don’t need to manually assign anything or make a special Live session template. That means you can mix and match MIDI and audio tracks arbitrarily, which you can’t do with a template. Secondly, sometimes having the arbitrary limit of eight channels is ideal in live performance — and it means you don’t have to bank around.

Transport

This winds up working perfectly: you get play, stop, record, forward scrub, reverse scrub, and even a loop on/off switch. Of course, you don’t get some of the other parameters you get from an Akai APC40, like turning on and off MIDI overdub. But, hey, you spent sixty bucks on the Korg and you really can’t balance an APC40 and your laptop on Greyhound.

Setting Up Live

Once your MIDI Remote Script is in the proper folder, your device will show up automatically in Live. That’s especially cool if you’re a DIYer; you could have Maria’s Arcade Button Mashapalooza show up if you want.

Select a configured device just as you would any other control surface. Choose Preferences > MIDI/Sync, select Control Surface in the first column (nanoPAD, for instance), and then its Input and Output ports. Finally, enable the Control Surface Input for Track and Remote. This will allow you to manually override assignments if you want, and to assign controls on your hardware you didn’t assign in the MIDI Remote Script, both via the usual MIDI Map method.

Because I want to be able to easily record-toggle multiple tracks — and because anything else will mean the “toggle” lights on the nanoKONTROL are wrong — I also like to turn off “exclusive” arming in preferences. This way, you can record-enable multiple tracks at once, so that when you want to feed MIDI into your soft synth on track 7, your vocoded vocal track on track 2 doesn’t immediately switch off. Go to Preferences > Record/Warp/Launch > Record > Exclusive and make sure Arm is unlit. (Pictured above.)

One last tip, as suggested by Mike Hatsis of Trackteam Audio: use the Drum Rack’s Auto Select feature, and you’ll automatically toggle the interface to whatever part of the rack’s various pads you happen to trigger. (This works in Live 7 and later only.) This way, you can easily toggle more than the 16 visible pads. On my nanoPAD template, for instance, I’ve already gone to the trouble of mapping the remaining scenes, so the first 16 pads map automatically, and then scenes 2-4 can access other pad slots.

To enable Auto Select, make sure the Chain is visible in the rack, then click the small A button as pictured above.

Alternatives, Future

Now, go forth and have fun!

Granted, this isn’t a perfect control mechanism. If you need to bank more easily between tracks, control a whole lot of mechanisms that aren’t here, focus on clips, or … well, do anything other than the stuff described above … it’s not ideal.

On the other hand, I find this resolves about half of the situations that would otherwise require manual MIDI assignments and, worse, templates rather than dynamic assignment. For basic MIDI tasks, it’s a hack, but a useful hack.

What about the future? HyperControl from M-Audio and Automap from Novation both have more sophisticated integration. The Akai APC40 goes further than previous devices as far as dynamic clip triggering and shortcuts. And other integration is possible with Ableton’s own scripts than what you can do here, although you don’t necessarily get support for all the hardware you’d like to use.

MIDI Remote Scripting is frozen in time in Live 6, so as its own documentation says, there’s some stuff missing. I don’t expect it to be updated, however — too bad, as it is a nice hack.

The Ableton Live API is likely where future action is at. While it’s not an official or supported feature, I have no reason to suspect that it’s going away. On the contrary, you should be able to use API functions controlling clips and most functions of the user interface in Live dynamically. This functionality will be baked into Max for Live if you’re a Max user, but should also be accessible via the hacker-spported, community-based Python API wrapper. Most promisingly, hackers have already wrapped this Python API into both MIDI and OSC implementations, meaning you should have a choice between using Max for Live and supporting this functionality directly from hardware, even without M4L.

I’ll be documenting what’s coming very soon, both on the Max and Python/OSC sides. In the meantime, here’s a preview of what the API will do from our friend Andrew Benson at Cycling ’74. Andrew is himself a visualist, so I expect we’ll see some nifty visual applications.

Max-for-Live: A Sneak Peak at the Live API features

And looking beyond even Live, I think we’re now in a world in which we’re finally moving beyond simple MIDI learn. That’s a big relief. Next stop: OSC.

KORG owners: Downloads coming in a separate article later today!

Corrections/tips: More to add? Let me know and I’ll update the story. -Ed.

Still evaluating Live 8 – or want to learn more about how to use it? You can now read my review of Ableton Live 8 free on Keyboard Magazine’s site:

Ableton Live 8 Review [Keyboard Magazine]
See also (via comments) Nick Rothwell’s review for Sound on Sound June [subscription or US$1.49 fee required]

Keyboard doesn’t yet have comments, so feel free to discuss – or disagree – here.

I wanted to back up a little bit and consider Live as if for the first time. Now, I had also personally heard at least Robert Henke complain at one point that reviews of Live were uncritical. That to me would be a flaw as a reviewer, because all software designs involve compromises, so no software can ever be perfect. Here, I still feel there’s legitimate room for improvement in terms of the way Live handles interactive clip triggering and how it assigns control. Of course, we’re not just passively complaining about it – there’s also a community of Live users working to hack in functionality they need using the Live API, both via Python and forthcoming Max for Live.

Also for the review, I shot some quick video demos of features that were easier to show than describe, namely the new instrument Collision and the Vocoder effect. These are basically mini-tutorials on these creations. See Collision at top, Vocoder after the break at bottom. Fixed! Now the top video is actually the Collision video. (Oops.)

I’m a huge fan of physical modeling and Applied Acoustics, and Collision is one of the best percussion models I’ve seen. It starts to approach some of what’s possible in Apple’s Sculpture in Logic, but in a much more focused context, and with some unparalleled resonators (which you can also use on their own in the form of Corpus). See the top video for a walkthrough of the interface.

We may need to revisit the vocoder issue as there’s a new vocoder in FL Studio (Vocodex in the current beta), plus the existing vocoder in Reason. Sounds like there’s an article here waiting to happen. I like Ableton’s vocoder, though; it’s a different implementation and coupled with their unique Frequency Shifter, you can get some really unusual sounds.

For more Live 8 learning (and a more in-depth discussion of different ways of approaching the Frequency Shifter):

Live 8 Videos: New Warping Explained, APC + ReMOTE SL Integration

Ableton Live 8 Misuse: Ping Pong Psuedo Scratching Effect Video Tutorial

Ableton Live 8 Creative Tutorial Videos: Using and Misusing Groove Extraction

Ableton Live 8 Creative Tutorial Videos: Misusing Frequency Shifter

Mixed Up – Beat Blender and Mixmaster 1200 from Matti Niinimäki on Vimeo.

Ableton Live enthusiasts, you take very seriously what gear you plug into your laptop sets. We’ve seen painstakingly-created DIY controllers like the arcade button hardware below, and bizarre oddities like calculators and arcade cabinets and blenders and Osterizers (above). So, in celebration of New York installment of the Dubspot Ableton Live 8 Tour, Saturday, June 27, we’re going to get together in a fantastic space and have a little Live party. And we want to see what controllers you’ve made.

If you’re coming to town for the Live Tour or are in the New York area, we’d love for you to show some of your creations. Built or customized your own controller? Got your Wii remotes and webcams running your Live set? Built your own special Reaktor / Pd / Max / Python creation to customize your Live performance? Invented some hardware that works with Live? We’d love to see it. It’s a week that includes some of the most skilled Live minds in the planet presenting, plus celebrity appearances by the likes of Richie Hawtin, Scientist, and others. So we expect that even though this is last-minute, this could be a fun chance to get together.

If you’re interested, just sign up below or head directly to the Google Docs form. This is an informal, relaxed venue with drinks and finger foods. (Check out the recent New York Magazine write-up.) The idea is to bring along some headphones or small speakers and show things off in the catacomb-like former stables (and former sex club) nooks of this fantastic bar, meet up, relax, and get to know each other. We’ll also feature a live performance or two; if interested, let us know what your stuff sounds like.

The event will be open to the public; stay tuned for more details on this and the event itself.

And if you want to learn how to use controllers intelligently with Ableton Live – from the cheap and accessible to the weird – I’ll be teaching a workshop at Dubspot on Sunday 6/28.

Sign up, creative folks:

If you’re using Ableton Live 8, you’ve hopefully already discovered the joys of Track Groups. Track grouping is a welcome feature in any DAW, but in Live, the mixer-centric Session View can easily get unruly with endless columns of vertical tracks.

I wanted to share some discoveries about Track Groups, including what I thought was a big realization about how they worked with clips that turned out not to be as exciting as I thought.

To group tracks, select multiple tracks first (click one, then shift-click the last one), right-click (ctrl-click on Mac), and choose Group Tracks. The result – what’s basically a submix:

• You can save space by collapsing tracks in your view, clicking the triangle at the top of the Group
• You can add insert effects to the whole Group, and signal will be routed through that entire chain (making them like a quick send)
• You can control the whole “submix” Group at once using the Group’s mixer parameters

No surprise there. Here’s the surprise.

You’ll see when you create a Group that the Group track has actual clip slots – unlike the Returns, which have none. (Check out “A Return” and “B Return,” created by default, to see what I mean.) You’ll also see a colored pattern for each clip slot that is adjacent to grouped tracks with clips in them:

You can use that slot (seen here on the left) to trigger groups of clips. So, if you’ve grouped four tracks, and the first three of clips, triggering the clip in the Group track will trigger all of those clips at once.

It works just as Scenes do, but with a couple of twists. Unlike Scenes, you won’t trigger everything else in your Session – you have some control over what gets triggered. Also, you’ll see if you click one of the slots for the Group, you get a Clip View for editing.

At this point I got really excited, as I thought we might finally have Scenes that had the same editing parameters as Clips. No such luck. If you click one of the Group slots, you’ll see Clip, Launch, and Notes boxes. This includes things that Scenes lack – Launch Mode options, Quantization override, and Follow Action. So, initially, you might think as I did that we finally had the ability to have Scenes (albeit inside Groups) with more control and Follow Actions. Unfortunately, these actually behave as “wildcard” editing for the Clips. So what you’re actually doing is changing the Follow Actions for all the clips to the right of the Group slot.

That said, you can still use this as a hack to quickly create chains of Follow Action events, so it still could be useful – just not as useful as if Ableton finally gave us more control over Scenes or other groups of clips.

One last note: as further illustration of this principle, you can’t rename the slots in the Groups. That’s too bad, because it would allow you to create effectively grouped Clips that controlled Subclips. If you try to use the Clip Name box, you’ll actually rename all the Clips in the Group – and you still won’t see any text in the slot in the Group.

To me, it would be more consistent if both Scenes and Clip slots for Track Groups behaved exactly the same way individual clips did, enabling the quantization and follow actions that clips do. But that’s just my take.

There are people who are bigger Ableton gurus than I am who read this site, not to mention various people who work for Ableton, so I’m curious to hear what you think about this, and if you have other ideas for how to use Groups. I do remain a little disappointed, because you get track groups in lots of DAWs, but you only get Clips in Ableton Live.

Warp: Engage

The new Warp Mode in Live may actually be friendlier to new users; it’s existing users, accustomed to the previous way of working, who seem thrown for a loop. (Erm… excuse the pun.) I’m at a bit of a disadvantage myself in that I tend not to do a lot of warping/remixing. But Medway Studios has a set of tutorials specifically geared for people wanting some tips on how to assimilate the new working method:

Part 2:

Our friend Dennis DeSantis of Ableton offers his own take in a video shot at NYC-based music tech learning center dubSpot. This is a pretty good conceptual overview of what the whole thing is about.

Basically, what I’m hearing is that people used to previous versions of Warp Markers, while they find it confusing at first, do like the new system once they understand how it works.

Controllerism

Mark Mosher has been doing fantastic tutorials on his site Modulate This. For one thing, he’s got tips for getting Wacom tablets to work in Live 8 and finally getting text entry support, which means Kore works properly in Live at long last (among others).

Best of all, he has a tutorial that demonstrates how he’s putting together all his controllers – the Notation ReMOTE SL with Automap and the Akai APC40 – and making them function more effectively using some subtle controller changes in Live 8.

What’s interesting to me is that this isn’t so much about unique, proprietary stuff added to the APC integration, but basic feature improvements in Live itself, which could help you be more effective with other controllers, as well. That’s the kind of functionality I like to see, because it helps everyone.

All of this is great, but we are getting a little heavy on the Ableton-only video tutorials. It’s time to pick up the screencasting tools and demonstrate other tools, too. I’ve got some time blocked out this summer for the task. Requests?