The Traktor Kontrol X1 is an exercise in minimalism, reducing the various uses of Traktor to a few encoders and buttons and a compact form factor. But while it supports MIDI for use with any DJ software, its “high-resolution” mode – as with Maschine before it – uses a proprietary protocol. The unit will sell for US$229 when it ships in February of next year.

The control arrangement of the Kontrol X1 fits a selection of essential parameters into its narrow form factor. The controls are divided in right and left into the two decks, with four sets of effects controls each. There are dedicated controls for browsing through tracks, and cueing and tempo controls. The case can be used either horizontally or vertically.

The strategy appears to be to focus on controlling loops and effects, while those who want to work with digital vinyl can view this as a consolidated mixer / browser interface.

There are some nice extras, too. The box itself comes with Traktor LE, meaning someone can get started with digital DJing for about two hundred bucks. And for another $49, you can add a custom stand and case – details too often left out of controllers.

We saw this controller in September, in use in Richie Hawtin’s set. On NI’s promotional site, Richie has something interesting to say about Traktor, which is that it isn’t necessarily getting used by everyone in the same way:

You can put ten people on a stage with Traktor, and each one of them will have a different way to be creative and bring out their personality through it.

My sense is that this hardware will be well-received, because it is focused on some clear functions, it’s compact, it’s cheap, and it can be used in different ways by different people. Those trends have proved successful in controllers of late. On the other hand, it seems that a generation of hardware controllers that could have employed an open, standard, high-resolution control protocol are doing anything but. Ableton has locked certain software features to certain controllers, and in its controllers uses only MIDI. NI uses higher-resolution data, but has not continued to actively develop OSC. That could mean that, while open-source and visual software continues to progress, we may have to wait years before commercial music software comes to support any standard for this kind of communication using anything other than low-resolution MIDI. The big question may be, is there any incentive to commercial makers to do otherwise?

www.native-instruments.com/traktorkontrolx1.info

Novation’s Launchpad, its affordable (<$200) "grid" controller, may have a big Ableton logo on it. But underneath, it's just a MIDI controller. Bi-colored LEDs, containing a red and green element for red, green, and amber output (amber = red+green), can be triggered using simple MIDI note and control messages. That means, whether you're looking forward to Max for Live or you're sequencing in a tracker or writing Processing sketches, you can use the Launchpad just like any other MIDI controller.

One of the things I thought was a major demerit for Akai was the fact that they failed to ship a MIDI implementation for the Akai APC40. MIDI implementations are the charts of MIDI messages we've had since the very first MIDI devices came out in the 80s. They're usually printed in the back pages of the manual, and even the cheapest gear has often had one.

Score: Novation 1, Akai 0. Novation has done the MIDI documentation, and then some. Its MIDI “Programmers Reference” is out even before the official Launchpad ship date. And rather than just doing a MIDI chart and assuming people know how to read it, they’ve taken the care to fully explain the way MIDI messages work, how to calculate the right messages, and how to really use this. Experts will have all the information they need, but newcomers will also find they can spend a little time and learn how to do what they want.

Launchpad Support with Downloads (see Programmer’s Reference at the bottom)
Via: Novation released Launchpad Programming Guide, and Protocol [Nezoomie's Zen Wave Blog - great read]

It’s listed as “for Max/MSP programmers,” but anyone using MIDI will want to have a look; that’s obviously relevant to far more than just Max. (In fact, there’s not a single mention of anything specific to Max in the document.)

What might people do with stuff like this? Well, as of just four hours ago, Matt DiFonzo lets us know he’s written a simple monome emulator. It’s even got a clever name:

nonome – monome emulator for Novation Launchpad

There’s some bad news mixed with the good. Even with something as simple as a grid of buttons, MIDI isn’t as friendly as it could be. I still would like to have a MIDI editor for the Launchpad so you can reassign buttons if you like — that’s a feature, incidentally, available on rival Ohm and Block hardware from Livid Instruments. Also, the documentation reveals that Launchpad uses “a low-speed version of USB,” which runs at a maximum of 400 messages per second, thus taking 200 milliseconds to update a Launchpad’s LEDs. (There are some workarounds, but they’re … more work. Clarification: Once you double up messages, though, you can get this to a more acceptable gap, and that’s for updating all the LEDs, not the latency of input messages.)

Also, here’s a hint to Novation: use a Creative Commons license for that document. That way, your users will be free to document even more ingenious solutions and friendly guides. You win, and your users win. For instance, I have the illustration here, which I should be able to do for purposes of reporting on this story. But can I write my own how-to guide using your guide? Why not make it explicit to encourage me to do so? (They list the PDF as “proprietary,” though there’s no explicit license, and I think they just mean “proprietary” as in “what we’ve done on our hardware.”)

That’s a difference between open hardware and closed hardware, but I don’t even want to belabor the point — CC licenses are something a commercial company like Novation could easily use. In fact, if anyone at Novation or Ableton would like to talk to me about why I think it’s a good idea, I’d like to extend an open invitation. I’m no legal expert, but I can explain what it means to me as a user and developer, and connect you with some of the right people at Creative Commons and the CC-using community.

But those gripes aside, kudos to Novation for getting this documentation out here. I think it’s really good news for people experimenting with grid controllers. And we’ll be looking at how all of these tools, hardware and software, fit together, and how open source development can make them more powerful.

Patchers and coders and hackers: if you’re interested in working on interoperability between all this stuff, let us know.

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.

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.

GPS Beatmap from Jesse Stiles on Vimeo.

“Locative art,” the idea that somehow location will feed into music and visuals, has eluded culture. We have the technology, in the form of sophisticated databases of location information and highly accurate, publicly-available GPS satellites. But it’s one of those solutions in search of a problem, and begs the question, why?

That is, until you unleash a nearly 6-liter V8 Ford LTD Crown Victoria on the legendary Bonneville Salt Flats, and your driving gets translated to music. Now it makes sense. And sweeping through the salty dust in one of America’s greatest action-car-chase cars of all time, manipulating music on a Max/MSP software patch, all becomes right with the world. (That’s how it is in my head, anyway.)

The planet is your control surface.

Such is the project sent by co-creator Jesse Stiles, who worked with Rich Pell (and editor/documentarian Olivia Robinson) under the name Face Removal Services to perform this vehicular musical production. (Thank, as well, The Center for Land Use Interpretation / GPS Expo 2006. PS – I think we now know what to do with all those clunkers Americans are turning in for Cash for Clunkers.)

Now, this covers only X and Y axis. I think we need to add the Z-axis, for base jumpers. (I had a dream last night in which I was hang gliding from the rim of the Grand Canyon to the Colorado River below, a reminder that the Earth – and computer interfaces – do not have to be flat.)

“Studio” for many of us means packing musical production tools into a corner of our desk, then being able to fit the whole thing into a backpack and take it with us. It’s bringing along your entire production to a cramped rehearsal room and adjusting tracks in a hotel room. It’s putting together an assortment of unusual pieces of DIY hardware, mobile game systems and an iPod touch, and composing and performing a live PA set. So packing in functionality means a lot.

That makes it worth considering a hardware solution like Cakewalk’s V-Studio 100 in obsessive detail. Combining an interface with mixing, control, recording, and software functions makes the VS especially relevant to the computer musician.

I was one of the first people outside Cakewalk to lay eyes on the V-Studio 100. Part of the initial appeal to me was that it seemed to combine a lot of the tools I wanted into a single package.

Sure, its big brother, the V-Studio 700, is an impressive unit with loads of onboard options. But the V-Studio 100 was more my speed: it has that apartment studio, backpack-friendly attitude. And don’t let the “SONAR” in “SONAR V-Studio 100” fool you, either. While it’s great having a free copy of a special edition of SONAR on Windows you can use the VS hardware and even the plug-in bundle that comes with it on any host on either Windows or Mac. And — oh, yeah – you can also make use of all that audio I/O and mixing to do some crazy stuff with your plugged-in portable game  consoles and iPhones and homebrewed electronics.

The real test is whether this one unit can perform the tasks you need. The V-Studio 100 tries to be a number of different things:

• An audio interface (up to 24-bit/96 kHz)
• A mixer
• A control surface
• A wave recorder
• A software bundle

Correction: The street price of the whole package is US$699. (I had incorrectly put the street at $800 instead of $700!)

Anything that does that much will naturally have to make some compromises. Some of those compromises I think are rather well-conceived on the VS, while others I hope will evolve over time.

This will be partially a review, but partially a description of what it’s like using the VS, so if you do have one of these, I can hopefully give you a sense of how to begin using it.

What’s in the Package

The VS-100 itself is a tidy rectangular box with the main two audio ins on the front, USB, MIDI, and remaining audio I/O on the back, and mixer controls, menu, transport controls, control surface shortcuts, and flying motorized fader on the top. The unit feels terrifically solid, both in overall feel and the details of all of the controls. I wish it came with a carry case, but it’s the right size to fit a lot of generic gear cases out there. Documentation includes a Getting Started Guide, Hardware Manual, and two discs. One disc contains the SONAR V-Studio for Windows, a special edition of the SONAR DAW, plus a big bundle of plug-ins that will work with either Windows VST or Mac Audio Unit hosts. The other disc ships with drivers that work on both Mac and Windows. (In other words, Mac users miss out only on the free SONAR VS – not a deal-killer since you probably have a copy of GarageBand or another DAW, anyway.)

The whole unit weighs just over four pounds and can easily fit into a compartment in your laptop backpack or larger briefcase. You do need its power source – because of the pres, motorized fader, and mixer functions, this is just too power thirsty to draw all its electricity from USB – but the 9V power adapter is relatively compact.

Audio Interface

The VS-100 is a 10-in, 6-out interface. Of course, that’s actually relatively modest for interfaces of this price range. At the same time, those interfaces are just interfaces, the quality here I think is really good, and this could be a pretty practical set relative to what many people actually need.

Here’s the basic configuration:

Inputs 1-2: XLR mic jacks and balanced TRS 1/4” jacks. Input 1 has a Hi-Z (high impedance”) switch that switches to a 500 k ohm impedence for guitars. There are also mic preamps on both 1 and 2. There are also physical knobs on the front of the unit for adjusting input sensitivity of 1-2.

A phantom power switch is located on the back of the unit for mics that need power.

Inputs 3-4: Dedicated mono TRS jacks (balanced).

Inputs 5-6: Stereo phono pair (unbalanced).

Input 7-8: Digital S/PDIF input on the back. (Input only; there are no digital outs.)

Input 9-10: The mixer output can be selected as a separate two ins.

Outputs 1-4: Four channels of balanced TRS 1/4” output. Can you say quad sound, anyone? (Hey, it’s actually the most practical option for live performance.)

Outputs 5-6: Unbalanced stereo output.

You do get 1-in, 1-out MIDI, accompanied by Cakewalk/Roland MIDI drivers, which traditionally have given me good results on both Mac and Windows.

The mic pres on inputs one and two sound really transparent, much higher-quality than I would have expected, and the one indication that Cakewalk and Roland aren’t thinking of this as just an entry-level unit.

For the one-man/one-man performer, it’s a pretty ideal configuration, it’s great having unbalanced I/O, it sounds good, and you have dedicated level knobs where you need them. I’ve played out with the VS, and it’s an ideal solo computer audio interface.

Even given that, you probably wouldn’t buy this box for its audio alone. You could get a MOTU Traveler, for instance, with FireWire audio, lots of additional analog and digital I/O, more pres, and internal mixing capability. But it’s the other features that make it a contender.

Mixer Operation, Interface Operation

The VS adds to its interface mixing functions and a built-in set of effects. And note that on the mixer side, this isn’t a “software” mixer as you provided by some of the VS’ competition. You get a compact but very functional set of hardware controls that allow the VS to handle mixing functions, even when you’re also using it as an audio interface, and even when you’re in cramped spaces.

On the effects side, the VS includes a dedicated compressor and 3-band EQ for tracks 1-6 (as inserts on 1, 2, 3/4, and 5/6). Via some cleverly economic menus, you can edit parameters for these settings using the toggle buttons above the mixer knobs, in conjunction with three dedicated encoders and the value knob. It’s not hard to get the hang of toggling around, and while you don’t have dedicated controls as you might on a full-blown mixer, functions are rarely more than a button press or two away.

While it’s a bit harder to get to, there’s also a decent-sounding internal reverb included, as well. It has specific sends for each channel (1, 2, 3/4, 5/6) and adjustable send level, though you’re hard-wired to some basic modes (ECHO, ROOM, SMALL HALL, and LARGE HALL).

Quick tip: Hidden in the settings is the ability to route audio to your USB port pre-EQ. (Look for Menu > Utility > To USB > PreEQ.) Generally, recording with in-line EQ is a very bad idea, because there’s no way to go back to the raw audio. With this setting adjusted, you can use EQ for live performance but without impacting your raw tracks if you want to master, say, a live session later on.

The VS-100 can operate both as a standalone mixer – something you’d take to your gig while leaving the laptop at home – and a combination between a mixer and an audio interface. Because of that, its operation is a little different, so let’s actually walk through the signal flow itself.

Navigating Signal Flow

Scenario 1: You’ve got the VS plugged into your computer.

You might plug a guitar into input 1, depressing the Hi-Z switch, and a mic into input 2.. You can then adjust input level on the “SENS” knobs on the front. There’s no dedicated LED level meter, but you do get a level meter on the LED screen on the top of the unit.

Monitoring is a little different than on most audio interfaces. You have two places at which you control the level you hear. The “MAIN MIX” knob controls the level for the mixer – which is also your zero-latency, direct monitor level, the level from your input before it reaches the computer. For the output from your computer, you would adjust the “PLAYBACK” knob.

The advantages of working this way: you can use this as either a traditional interface, or as a mixer – handy with multiple ins plugged in. And you get dedicated knobs for 1, 2, 3/4, 5/6, and (the digital ins) 7/8 for use in mixer mode. You can also feed the main mix out to a PA, so for live performance you can keep a mix going to your audience without carrying along a separate mixer.

Embarassing side note: In my haste, I initially assumed the “PLAYBACK” knob controlled only the flash Wave Recorder. It actually controls playback of your audio interface through the main outs when you’re in USB mode. You’ll, um, want to turn that knob down before you plug in the unit, as the outs are pretty hot. You can imagine what happened to me. Happily, my monitors survived. Oh, PS – Cakewalk actually should have put that in their manual, as there is a prominent warning about the “MAIN MIX” knob, but not “PLAYBACK” – and this is called SONAR V-Studio, so they should expect people will be connecting it to the computer straight away!

Scenario 2: You’ve got the VS operating standalone.

The mixer functions are pretty self-explanatory. In this mode, the Wave Recorder can record from your main mix, it can play back tracks, and it has loop playback. The ins and outs work otherwise as they would in DAW mode, and you still get the built-in effects. The one downside in this mode is that the DAW controls – the shortcut keys, track select buttons, and flying fader – are all basically meaningless. It’s too bad that they couldn’t do some sort of double duty. But it’s still nice to have this box as a mixer and effects unit on the go. There’s even a metronome feature, so it could be a decent box to carry around to rehearsal with you, especially with the built-in Wave Recorder, if you don’t already own such a unit and just want to budget for the VS alone.

Scenario 3: Disaster strikes.

Here’s the best thing about having two modes: try yanking out the USB port while the VS is plugged in. Normally, that’s a very, very bad idea (and it’d be an especially bad idea when using FireWire, as you could theoretically fry your computer or interface). But with the VS, the hardware will automatically switch its routing to the wave recorder, and the mixer will continue operating normally.

In other words, you can have a cable come unplugged or a computer crash and save a gig by keeping sound going on the VS. With WAV playback on the WAV Recorder, you could even switch over to a flash card for backing tracks.

The Control Surface

At its simplest, the control surface gives you just the basics: transport controls, mute/solo, and arm, plus the main feature – a motorized flying fader. Of course, in a lot of situations, that’s exactly what you need for basic recording. In fact, thanks to the fact that the fader is motorized, you may not need other faders, given that most mixing scenarios involve adjusting just one track at a time. (Riding more than one fader can tend to cause you to overcompensate when fine-tuning levels, a bit like oversteering.)

The track select keys toggle tracks. (It doesn’t matter which track is selected in software, even in SONAR.) Using the shift key navigates buses (SONAR only). The value knob can also be used for additional manipulation.

Transport keys can move not only the transport but, using the shift key, from marker to marker.

For those of you who have managed to escape the experience in real production, using motorized faders is a joy. The fader will near-silently shift to whatever setting you choose. I remember using Digidesign’s motorized faders when they first came out and finding the effect almost magical, though in those days the technology was priced as high as a compact car and the faders moved with a little “thump” sound. Happily, technology marches forward.

In ACT (Active Controller Technology) mode, Cakewalk maps its own SONAR software more intelligently. By default, this includes the Value encoder and the three encoders below the LCD, so that if you, say, bring up an instance of one of the included Studio Instruments, software parameters automatically map to those hardware controls. It does make quickly accessing basic settings a little quicker, though if you’re a heavy synth user, this functionality is unlikely to compete with similar and more advanced  “automatic map” controllers and software like Native Instruments’ Kore, Novation’s ReMOTE line with Automap, and M-Audio’s Axiom Pro with HyperControl, or Cakewalk’s own ACT in combination with a range of hardware. There just aren’t enough controls on the VS, by contrast. In a pinch, though, ACT is still useful on the VS, especially if you enable the “DAW Full Asgn” setting in the menu. It automatically maps the mixer knobs for use with ACT, too.

Unlike technologies like HyperControl and Automap, ACT is limited to SONAR, but SONAR users, I think you will find yourself using it at least a little, just because it’s there. My one criticism would be that it’d be great if there were a keyboard shortcut for switching to “Full Assignment” mode without digging through menus. That way, you could easily toggle between using mixer controls for mixing and using them for ACT.

Confused by all these options? Given that all these technologies rely on MIDI, anyway, I think we badly need an open spec that allows you to easily support any host with any hardware, without the fuss. Someone out there adept at Reaper scripting, for instance, I’d love to hack into this.

What if you don’t use SONAR? Mackie Control Support

You can still get basic control with V-Studio using Mackie Control. It’s just as easy to set up: choose Mackie Control as your control surface, then select the V-STUDIO CONTROL port as your input and output. In software like Ableton Live, Apple Logic, Reaper, and others, the VS will automatically map to basic mixing functions. Transport controls work perfectly, the motorized fader jumps to the right level, and mute/solo/arm buttons work. I tried it in a number of apps and had no problem.

There is one catch: because of some of the limitations of Mackie Control, you don’t get to use those extra knobs. While Full Assignment mode remaps all the controls to MIDI and should allow you to manually create your own MIDI maps for your favorite software, it also enables ACT mode. That means that you lose all the functionality of Mackie Control if you turn it on. You can have one or the other, but not both.

It’d be nice to see Cakewalk modify the functionality of Full Assignment mode so that it can coexist with Mackie Control. That way, you could use the rest of the control surface as a MIDI control surface rather than losing the functionality of those controls. It’s a subtle point; as I said, I think people will use the transport and mixer controls far more than synth controls because of their relative convenience. But it would make a nice firmware upgrade.

Speaking of firmware upgrades, make sure you’ve upgraded to at least 1.19 firmware before attempting to use Mackie Control. This release fixed a number of bugs, including one that prevented me from switching to the “OTHER” DAW mode (from SONAR.) Once I updated, though, this performance was seamless.

The Wave Recorder

One of the reasons you might want to drop the VS in your gig bag is that it combines a mixer with a wave recorder in one box, and can replace a computer or a mixer+recorder combination. Pop in an SD card or SDHC card – capacities up to 32GB via SDHC – and you can record the stereo mix of whatever is plugged into the mixer. The Wave Recorder also supports easily-accessible playback, which could make the VS ideal for backing tracks. You could, for instance, use it in its computer interface mode in the studio for production, then load all your tracks onto SD and play them back onstage with the VS running as a mixer. Alternatively, you could record a mixed-down rehearsal or performance and take it home with you.

Like Roland’s mobile recorders, you also get basic marker and looping functionality, which could help you practice or transcribe a tricky portion of a song or create more sophisticated backing arrangements if you were feeling especially ambitious.

True, you could bring along a mobile wave recorder, but the convenience of combining the recorder with mixing functions makes it ideal in cases when a portable stereo recorder is not.

There’s one major caveat, however. Playback from the wave recorder and recording of the stereo mix are both possible when the VS is operating in standalone mode. But when it’s connected via USB, each of those functions is defeated – no playback, and no recording. The transport controls are reassigned to become software control surface functions, and the SD card slot becomes useless. That’s too bad, as one of the first things I wanted to do with the VS was to be able to record live sessions without relying on my computer hard disk, recording the same live mix I’d feed to the PA.

I was able to confirm with Cakewalk that Roland is aware of this limitation and investigating possible solutions; it may be technically possible to resolve the issue with a future firmware update. They were not able to confirm at this time when a fix was coming or what form it might take, but I’ll provide updated information if it becomes available.

In the meantime, it can still be useful to have the VS wave recording function, as it does mean you can leave the laptop at home for various recording and practice scenarios.

Driver Support

As with previous Roland/Cakewalk outings like the SONAR Power Studio, the VS-100 comes with extensive documentation on how to tweak driver settings under Windows, and you can expect extremely up-to-date and reliable support for Windows technologies, including the WASAPI adjustments made in Windows Vista. (WASAPI is Windows’ general audio interface for software; it’s supported on the software side by applications like SONAR, but it’s essential that hardware driver implementation be robust in order to acheive proper support under Windows. Translation: Cakewalk gets their drivers right, so Windows works properly and you don’t have to worry about it.)

Installation on Windows winds up being pretty easy. Install the driver disc to get up and running. Install a second disc, and you install a huge suite of plug-ins as well as the special edition SONAR VS software. The bundle installed over my existing Cakewalk SONAR Producer Installation just fine, and then the newly-installed effects became available not only to SONAR VS, but my existing SONAR install, too, as well as all my other VST-compatible DAWs (like Live and Reaper).

The Mac installation winds up being easy, too, however. The Mac version fully supports Core Audio, and I got excellent performance in Logic Studio 9. Logic also mapped easily to Mackie Control.

Bundled Software Gems

The VS Production Pack includes a set of effects and instruments for both Mac and Windows:

• VX-64 Vocal Strip – a combination deesser + “compander” (compressor/expander) + tube-emulating EQ + Doubler + synced Delay. That could have been a bunch of gimmicks. But it winds up being all awesome.
• Native Instruments Guitar Rig LE
• Boost 11 Peak Limiter – actually a pretty decent and relatively transparent limiter
• Channel Tools – a set of channel utilities for enable/disable/swap L/R channels, adjusting stereo and mid-side mode, and adding delay.
• LE versions of Dimension (sampler), Rapture (synth)
• Studio Instruments Bass, Drums, Electric Piano, Strings: all some very lovely-sounding, lovely-looking instruments

Bundling light-edition software with hardware is a popular choice, but the VX-64 is the real stand-out. The set of tools integrate beautifully, there’s a fantastic live spectrograph tool for a view of what you’re doing on each of the modules, there’s a lovely drag-and-drop routing interface, the UI is clear and well laid out, and the whole think sounds utterly wonderful. I don’t think it’d be hyperbolic to say the VX-64 is the best software plug-in Cakewalk has made yet; it just packs in all the goodness you might like for vocals in a single window.

There are enough unique capabilities here that, even if you have a collection of plugs or a DAW with lots in it from a rival maker like Ableton’s Live Suite or Apple’s Logic Studio, you’ll find something useful. The danger to all of this is that there’s a sort of kitchen sink feel to the suite, and it could well overwhelm beginners, but the VS generally feels better suited to intermediate-to-advanced users, anyway.

SONAR VS

The sleeper hit of the whole package is the VS edition of SONAR. Usually I like light editions of DAWs about as much as I like diet soda – it’s just not as sweet as the real thing. But the VS is a pleasant surprise. It feels a bit like GarageBand for grown-ups. One of the complaints about SONAR from non-converts is that its do-everything user interface can feel cluttered, particularly by providing lots of different routes to the same thing. I think that’s a fair criticism, even as I respect what SONAR does.

What’s remarkable about SONAR VS is that it feels like it sacrifices none of the functionality of its big brother, but wraps it into a much cleaner interface. Channel strip pop-ups on the left allow easy access to every parameter. A reduced toolbar icon provides essentials without being overwhelming. There are still some hard-to-read icons, and the software is likely to, again, be a bit complex for beginners. But for users with some experience, there’s a real sense that tools and options have been thoughtfully chosen.

All of this may be overkill for those of you loyal to an existing DAW, but it’s still worth noting the job Cakewalk has done. Of course, the message to Cakewalk should be clear: SONAR itself needs a window layout that’s this clear, either as the default or something you can switch on easily.

Note that you actually don’t need SONAR VS to get any special integration with the V-STUDIO 100 hardware and drivers. Driver setup is the same for SONAR VS as SONAR; it takes a few steps but in either tool, you get excellent driver support, and I don’t think there’s any question that Cakewalk’s support on Windows is exceptional – enough so that Windows really isn’t a hassle.

Conclusions

The VS hardware brings together something I’ve been waiting for in hardware for a long time. It’s beautifully compact, too – but, naturally, that means it also has to make some trade-offs to put together so many elements in one package. It’s simply worth considering if it’s the right set of trade-offs for you.

The good:

• The unit is physically lovely to work with, in terms of its layout and feel.
• The pre’s sound great, and while the audio I/O isn’t as extensive as on some interfaces, it’s practical for a lot of real-world, one-person, mobile producer situations.
• Using the motorized fader is addictive, and works in any Windows/Mac software.
• The control layout winds up being very usable, and it’s nice having compressor/EQ instances within easy reach.
• You get rock-solid Roland audio and MIDI drivers (particularly important on Windows).
• SONAR VS is actually a great little audio package.
• The VX-64 is a real gem for anyone working with vocals, and overall the software bundle is a terrific value.

The mixed:

• The WAV recorder gets defeated when you plug in a USB cable.
• The VS would be more useful as a control surface if you could more easily map the rest of the surface to MIDI – without having to use SONAR and without having to defeat Mackie Control.
• The ACT controls can be a little confusing on such a compact control surface.
• Even with those two great pre’s, the VS probably won’t be your first choice if what you really want is just an audio interface.

Despite some weaknesses, though, to me the VS’ strong points are what can make it a terrific choice. A remarkably compact mixer combined with the flying fader and transport control and the audio I/O you’re most likely to need? That could be enough to sell you, before you add in additional value from some of the software gems that come with it.

At US$699 street, there are cheaper options around, but by the time you add a control surface, a mobile recorder, a mixer, and an audio interface together, it’s a different picture. There are also other control surface-mixer-interfaces out there, but some skimp on audio quality while others lack the VS’ elegant compactness.

The VS still counts as the most control, mixing, and audio functionality I’ve seen in any backpack-friendly box. And as such, for the laptop music production warrior wanting to maximize space and power, it’s part of a handful of essential gear to consider.

Cakewalk V-Studio 100 Minisite

For another review of this unit, check out this post from Boing Boing Gadget’s excellent Rob Beschizza. And Rob takes some really gorgeous photos of the VS, too.
A Weekend with Cakewalk’s SONAR V-Studio 100 [boing boing gadgets]

Having full control of a complete mix and session from your MIDI keyboard – without having to move your hands to the mouse or shift your focus to your computer screen – can be an addictive, if elusive feeling. Here’s a look at one way to accomplish that objective using the new Axiom Pro keyboards from M-Audio and CDM reader favorite Ableton Live, thanks to a first-look video provided to CDM first.

We’ve seen efforts to make this happen before, notably including the Korg Kontrol keyboard series working together with Propellerhead Reason and Novation’s Automap with software like Ableton Live. M-Audio’s Axiom Pro line has a new twist on the idea with what Avid calls “HyperControl.” Several details make HyperControl unique. For one, it doesn’t require any intervening software or drivers; the keyboard is USB class-compliant and plug-and-play, and you don’t have an additional software layer as with Automap. Also, the Axiom Pro is natively capable of sending keyboard commands, and even has a numeric keypad on the front panel of the unit. But most importantly, the Axiom Pro has its own workflow for different editing and performance functions. My suspicion is whether you love or hate HyperControl will probably hinge on how you adapt this feature.

Avid has been kind enough to give CDM an exclusive scoop on an extensive video they produced walking you through the process of setting up HyperControl with Ableton Live, step by step. Now, normally many of the videos from hardware makers make me cringe. John here has done a really terrific job, however. It’s really a tutorial and not a sales pitch, and while I’m a fan of writing and reading, this would be really confusing without the video.

Much of the working method focuses here on controlling the whole session rather than performance parameters. If that doesn’t appeal to you, skip to about seven minutes in for a discussion of “Device Mode,” which is when you finally map those eight encoders to the eight macro parameters for Device Racks so you can tweak your live synth sound. What’s nice here, though, is that you could couple that technique with the tips on recording clips, so you can play, record those clips, play back lips, and tweak all at once, one-man-band/one-woman-band style.

Have a look at the video, and let me know what else you might like to know. What isn’t covered? What other ways might you want to use a keyboard-and-software rig like this?

And don’t worry, while this week is becoming Controller Week (like shark week for MIDI nuts?), it doesn’t have to be The Ableton Live 24 Hour News Network. HyperControl also supports other software, including Avid’s own Pro Tools. Apple just released support in Logic Studio 9 and MainStage which I’m researching now. And while HyperControl is a slick moniker, I’m also researching more conventional control methods, which can even support Linux thanks to the fact that the hardware (unlike Novation’s) is class-compliant. So let us know your priorities in comments, and I’ll see if we can make them happen.

Axiom Family at M-Audio (now Avid

I Want My CDM TV

We’ll be putting more videos onto CDM TV very soon, and now you can subscribe to videos easily via iTunes, Miro, and RSS. Transcoding is fixed, too, so you can load up this video on your iPhone / iPod touch and balance it on the end of the Axiom Pro while you practice these techniques, if you like!

Subscribe to CDM TV with iTunes
Subscribe to CDM TV with RSS
Subscribe to CDM TV with Miro

Still a little thinner than we’d like, but expect this channel to heat up for the …um, fall season.

Ready for more dynamic control of Ableton Live, on the cheap? My how-to on MIDI Remote Scripting in Ableton Live was just last week, but it has already inspired new scripts for hardware, this time on the Novation Nocturn. (My examples for the tutorial were the Korg nanoPAD and nanoKONTROL.) The Nocturn is also very easy to slip into a backpack or carry-on, and very affordable at US$100-130 street. It just happens to become more valuable with a little user hacking.

Why the Novation Nocturn? After all, Novation touts their own Automap technology for just this purpose. But Novation assumed you only want to use the Nocturn Automap with your plug-ins and not to control Live. Here’s the non-dynamic hack from Novation:

How to control Ableton Live with the Nocturn?

Musician NCKN (”Nicken”) of Aachen, Germany has a better solution. He uses MIDI Remote Scripting to create a downloadable file that will map the Nocturn’s eight knobs to your device racks automatically. If you did pony up for Automap PRO, it’s useful, too, as it allows mapping buttons to Live keystrokes. (Bome MIDI Translator would be another option.)

Complete instructions and a free download at NCKN’s site. Be sure to check out his music, too; there’s some wonderful stuff.

DIY: Automap in Ableton Live with Novation Nocturn

Beautiful ambient-ish tracks with field recordings and acoustic noises blended elegantly into an electronic production:

Back to the controller that has an Ableton logo tattooed on it, we’ve got still more APC40 hacking going on, too. Darren Cowley sends along his Live rig and a video:

APC40 Customization from Darren E Cowley on Vimeo.

The “short” film clocks in at nearly eighteen minutes, but here’s the basic ingredients:

Korg padKONTROL + the free Farmpad customization tool for Mac + Akai APC40 + the mighty, powerful Bome MIDI Translator for more control over events + the now-discontinued Lucifer VST (which I believe has now been replaced with the audio-recording-manipulating Live Sync Recorder.)

There are some really tasty hacks here. Scene launch buttons glitch the sound or impact launch quantization. Controls provide quick access to recording and playing audio loops. Effects are on summed tracks for DJ-style effects manipulation. There are clever tricks for using lights for additional feedback. It’s all proof that no two people really approach Live or even this fairly clearly-mapped hardware in the same way.

Side note: I received a comment from a gentleman who is color blind and therefore can’t see the red/green light feedback on the APC40. Anyone with tips? I don’t think you want to rip out the APC’s lights, for sure. It does really prove that one size can’t possibly fit all in hardware.

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.