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.

Compact MIDI controllers for your fingers are plentiful, but tiny foot controllers are far fewer. map~map aka Marcus Fischer decided to build his own by performing a simple but clever mod of the KORG nanoKEY. Now, personally, I find the nanoKEY the one product in the nano series that’s lacking; it feels more like a QWERTY keyboard than anything resembling a MIDI keyboard. But Marcus transforms it into the world’s most compact and portable foot controller. You may have to be somewhat delicate with your toes, but he says the solution works perfectly!

i’ve been wanting a compact usb midi foot pedal for a long time. i built one out of a usb number pad last year but it was less than ideal. tonight i popped all of the keys but five off of my korg nanokey in order to see how it would work as a pedal. it turned out that it worked really well. i cut some small pieces of plywood out to raise the key height and some scrap plexiglass to cover up the missing keys. a little spray paint and double stick tape and it was all finished.
i think it turned out pretty well. not bad for a cheap keyboard and scrap materials.

279 / nanopedal

Those wooden blocks look quite lovely. KORG, you may have inadvertently created a new product.

The grid is in. While the monome remains the standards bearer for hardware with grids of buttons on it, arrays of buttons are suddenly everywhere, in the commercial Akai APC40 and Novation Launchpad, and, from Livid Instruments, the Ohm64 and now the Block. I think it’s a real compliment to the monome’s creators – and the community that has authored ingenious open software for the monome – that there is this excitement around the design.

The latest entry is Livid’s Block, a compact, aluminum-and-wood controller that’s easy to carry and which weighs less than 3 pounds. It’s not a monome – it eschews the monome’s stringent minimalist design aesthetic and adds knobs on top, faders on the side. That layout has made the M-Audio Trigger Finger a blockbuster hit, so I think it could attract people who want more than just buttons. (That’s why choice is generally a good thing.) But just as importantly, the Block takes cues from the monome beyond the skin-deep. As with the Ohm64, Livid is working to open-source both the guts of the hardware and the software on the computer. The instruments are made by hand using sustainable materials and finishes, manufactured in Texas in their own shop rather than the lowest bidder overseas. The hardware itself encourages hacks and customization. These are principles championed by the monome’s Brian Crabtree and Kelli Cain, and they’re badly in need of some company. Livid, like those monome creators, is a handful of individuals rather then a big company, but they give us new hardware that embodies sustainability, openness, and local production – and that makes the monome and its principles stronger. (Livid has been crafting performance hardware and Max patches for many years.) And while this bus-powered USB MIDI device doesn’t yet support (OSC) OpenSoundControl, that could come – without sacrificing conventional MIDI connections to outboard gear when you don’t have the computer connected. (Clarification: as with the Ohm64, OSC support is not yet available but should be possible. Stay tuned.)

Basic specs:

• 8×8 backlit keypad with corresponding knobs, function buttons, and faders
• Square layout that can be used at any rotation (so the USB port lies where you want it)
• Runs a suite of apps built in Max/MSP from Livid – including a sampler, synth, sequencer
• blockEditor for customizing layouts, lights
• US$399, available November 1

I’m interested in more open software, so I’m working on making an editor in Java and would love to hear what else people might want. (SuperCollider looper? Pd algorithmic grid controller? Processing library?) These I hope to make work both with the Livid hardware’s added faders and knobs, and the monome’s more minimal design. Of course, OSC will be terrific for computer applications if that comes to pass, but I love the idea of gear that can also talk to MIDI hardware.

I really like Novation’s Launchpad, but for a little more money, you get a beautiful case, additional controls, and added flexibility, all in gear handcrafted by the maker and with an open approach to hardware and software. Without getting into a debate over the merits one way or another, consider this: you can choose. We didn’t use to have these kinds of choices in music hardware. The fact that we do now – not only the ability to choose the nameplate, but the very philosophy behind the device’s manufacture – I think can benefit everyone, users and manufacturers alike. It opens up the entire music tech industry to new ideas and new variety.

http://www.lividinstruments.com/hardware_block.php

The “space bassoon” Eigenharp seems to have landed from another planet. Today, I’ve got good news: it’s bringing alien gifts with it. By next year, both the software and the high-performance protocol the instrument uses will be open source. Taken together with other advancements in the open source community and with protocols like OSC, that could mean we’re at the vanguard of a golden age for more open, more intelligent, more expressive digital instruments.

Genuinely new music controllers made available commercially don’t come along very often. So this week’s news of a strange but wonderful-looking instrument shaped like a bassoon with customizable key controls turned many heads. With high-resolution, high-frequency data and reliance on the computer for everything from sound generation to mapping the keys to different tunings, the computer connection matters. Eigenharp’s chairman, John Lambert, sets the record straight for CDM on the software, the way it talks to your computer and other gear, and how open the tools and protocol will be.

I’ll be talking more with John next week, but I want to bring you this news now. Part of blogging means that you don’t hold back – you share that first reaction and then learn more. I’m pleased to say I was dead wrong on the Eigenharp. What looked on the spec sheet like MIDI-only communication and proprietary software turns out to be just the opposite. Sometimes, being wrong is great. Here are all the details:

What protocol do the instruments use?

The instruments talk to their base station by a dedicated, high speed, differential, transformer-coupled, error-correcting digital protocol designed (and tested) for use in noisy stage environments by ourselves. The wire used is a 4 core, standard star quad mic cable and can be up to 40M long. The base station then talks to the control software running on the host PC (Mac at the moment) via a dedicated protocol over USB2. In the host system, the native protocol used between agents (our software components) is a network protocol called Eigentalk. This can run over Ethernet wires (with slightly increased latencies due to some smart jitter buffering we do). We will be making this public and freely available (when we open-source our main software) in Febuary next year. There is an open API, to be published at the same time, for our equivalent of AU’s or VST’s, hosted in our software, EigenD. This is rather richer than the AU and VST API’s, for reasons connected with the expressiveness and configure-ability (is that a word?) of our system. A couple of interesting AU vendors are looking at producing native EigenD instruments at the moment, and I think there will be many more in time. We try to avoid MIDI wherever possible as it has so many serious performance limitations.

Had you considered OSC?

We did have a look at OSC but there are a bunch of things that our protocol does that OSC didn’t (not least of which, for example, is clock syncronisation for jitter removal, utterly vital over ethernet for live performance) so we decided to grow our own and release it. Absolutely no reason whatsoever that we can’t interoperate fuly with it though, I suspect that an OSC EigenD Agent will probably come quite soon after the open source release.

Ed.: Actually, with OSC (OpenSoundControl) moving increasingly toward broader input and assimilating other standards, I can easily imagine that a future implementation of OSC could begin to implement these features. More on both protocols in the coming months. -PK

Is it possible to use this as a controller for MIDI hardware? MIDI software?

Yes, EigenD has in and out MIDI gateway programs. The incoming [MIDI] is mainly used for pedalboards at the moment (to control scale, key, tempo, etc.), although there is no reason you couldn’t use a midi keyboard to play notes. We’re using the MIDI out to do a wide variety of things, including playing MIDI sound modules, and controlling video DJ software and lighting systems. There is a huge reduction in effective bandwidth when ‘downsampling’ to MIDI, but for a lot of things it still works very well. And of course, the AU and VST standards (which we fully support) are a kind of MIDI interface.

Is it possible to access its native protocol for custom software / Max-Pd patches and the like?

Well, we’re open sourcing the whole thing early next year, and I think there’ll be a lot of work done to glue all sorts of external stuff in then. Max/MSP has attracted a lot of interest in this area. The whole of EigenD is kind of built for this really. We’re an Open Source company: my main personal desktop is Linux and I have a strong personal commitment to open standards. I offer a number of ‘programming bounties’ for Linux improvements on my personal website at http://johnhenrylambert.com.

Tell us more about open-sourcing the software. What tools did you use to build the software.

It’s written in a mixture of C++ and Python. It’s quite scary code, but very clean and pretty, with little ‘cruft’. I think the open source community are going to have fun with it. Its a big system too, 8 years of R&D in one huge release. I don’t think that there’s been anything quite like this open sourced before in the music world – it is a bit as if Logic or Ableton were GPL’d tomorrow.

Thanks, John! Stay tuned for more details, and let me know if you have specific questions for the creators.

I don’t know if it’s “the most revolutionary new musical instrument of the last 60 years,” but let’s be clear on one thing: the Eigenharp Alpha is utterly, beautifully insane. It combines breath and finger input in a bassoon form factor, but with quite a lot more physical control, a computer connection, and no internal sound source of its own. The breath input comes from a crooked tube as on a bassoon, with finger input in a touch strip, a fretted, light-up keyboard, and keys that have their own various forms of expression. Launched yesterday in London, the Eingenharp is getting a lot of attention. (And yes, some of you spotted signs of its launch all the way back in June, to which I say – I’m sorry I’m so late to the party.)

From BBC: Do you drum it, strum it or stroke it?

I hope to speak to the creators soon. Already, I see some indications that there are equal parts genius and madness here. The controller itself, even in the bizarre bassoon form factor, has an extraordinary amount of control, with high-resolution keys, percussion keys, elaborate control arrangements that can adjust tone or record samples, and extremely precise breath and touch. At £3,950, many computer musicians accused of “knob twiddling” by the creators probably won’t be able to afford the top-of-the-line model, but I do believe an instrument like this can easily, fairly cost this much, it’s a cost reasonable for musical instruments – and there is a £349 “Pico” edition for mortals.

There’s some madness, too, however. For the “instrument of the future,” the creators appear to have chosen MIDI, via USB, in place of a modern control protocol. Then, they plug the instrument into proprietary Mac software. (A Windows version is expected early next year.) There are software models of a Cello, a Clarinet, and a Synth, but there are also gigs of samples oddly loaded into SoundFont format. Given the futuristic ambitions and the sky-high price, closed software and antiquated I/O seem puzzling to me. I’m also skeptical of the approach here of piling on as many controllers as possible.

CORRECTION – CORRECTION! Yes, indeed – proprietary software and the limitations of MIDI wouldn’t make any sense – and apparently the creators agree. So the software will be open sourced, as will their custom-designed protocol. I’ve got all the details – required reading for anyone working on expressive instruments.

But don’t get me wrong. I think this fascinatingly bizarre instrument is worth exploring. The hardware design looks exceptionally luxurious, and there is some genuine design innovation in the controller the likes of which we’ve never seen in an instrument beyond a prototype or two.

Oh, and yes, I already want the Pico – and I think the Pico’s fewer controls may actually make more sense.

Basic specs:

Video of the key action, among others collected on YouTube:

The “Alpha,” the flagship:

• 120 keys, plus 12 percussion keys. (Wait — 120? Yes, you read that right.)
• Two strip controllers, one on each side.
• Breath pipe and mouthpiece.
• 11-bit resolution (2048 values) in the keys and strip controllers, 12-bit resolution (4098 values) for breath.
• Internal audio interface with mic pre, converters, and headphone out – so you need to carry this and a computer, but not this, a computer, and an audio interface.
• A “Base Station” with inputs for expression pedals and foot switches, which also contains the USB connection. This connects to a floor spike on which the instrument rests.

http://www.eigenlabs.com/alpha/

The Pico:

• 22 keys (18 for playing, four mode switches).
• Keys work via direct pressure and lateral pressure in both directions, as on the Alpha.
• Breath pipe.
• Strip controller.
• Same resolution: 11-bit keys, 12-bit breath.
• £349.

http://www.eigenlabs.com/pico/

To be honest, I’m quite a lot more interested in the Pico, not because I think cheaper is better, but because I’m curious whether you can’t be just as expressive with the more limited set of controls as with the kitchen sink approach of its big brother. After all, 22 keys is roughly the number you’d find on most reed instruments, including the Bassoon. True, the piano has 88 keys, but it also doesn’t really have anything else – and it’s able to have so many because of its form factor.

In fact, I’m sorry, but I love the Pico. It looks friendly, it looks portable, it isn’t terrifying-looking like the Alpha, and it seems it’d be more at home in a variety of musical venues than the Alpha. Sometimes less is more. Let’s see if I prove to be correct.

The software, though I hope you could also customize your own software rig using the MIDI input:

• Modular, allowing the routing of control inputs, sound sources and samples, loopers, and synthesis and effects.
• SoundFont oscillator.
• Physical models of the clarinet, cello.
• AU host for adding your own plug-ins. (And yes, this is where I think you’ll have the most fun.
• A system for triggering events, takes, key, and mapping scale.
• An interactive arrangement system for step sequencing.
• Oddly, an extensive Steinway D multi-sample. On the other hand, for years we’ve all have been playing bassoon and other reed samples on the keyboard, and in organ form for centuries, so now the reed instrument gets its revenge.

Source: Eigenlabs software specs.

The instrument’s creator, John Lambert, repeats the maxim heard at new instrument design conferences: “We’ve got pretty fed up with watching people twiddle knobs on stage.” Naturally, that means… turning to the Bassoonist, that sex icon of the orchestra? I’ll run with it.

One other tidbit from that article:

He says there is one high-profile musician who is about to take delivery of an Eigenharp, but won’t give any names.

Yeah, Herbie Hancock, we know it’s you. (Okay, they are an English company, so maybe it’s an English celeb, but really the question is whether Herbie is who they mean, or whether he’s filling out the pre-order as we speak. He’s like what we would all be like if we had a budget.)

Anyway, consider this a first look. I hope to get closer to the actual instrument soon.

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.

There’s a curious distinction in hardware keyboards. You’ll find plenty of keyboards geared for performance with software at the low-end to mid-range. But if you want a keyboard with uncompromising durability and action – and you’re willing to pay more and lift more weight – those choices suddenly disappear. Suddenly, you have to buy a workstation keyboard or something with built-in sounds or even built-in speakers. What if you want a really uncompromising keyboard to use with software and nothing else?

It’s almost as though manufacturers assume “serious” musicians want to gig with built-in sounds on a standalone keyboard. That’s a pretty stunning assumption in the year 2009, given the versatility, reliability, and unmatched sound quality and diversity of software instruments. If you’re looking for a controller alone, your options are limited. M-Audio, Novation, and others have some great affordable options, but nothing really high-end. Roland, Yamaha, and Casio have some nice controllers, but the higher-end models aren’t dedicated to the task, and therefore there’s no way to dedicate all your dollars to the controller itself. (Dig deeper, and there’s still more sacrifices to make – yes, you can have x, but then we take away y…) My short list would probably be Doepfer’s lovely keyboard in a road case and Studiologic – and that’s about it.

Studiologic’s new Numa Nero, therefore, looks like the serious controller a lot of us have been waiting for. It’s a full, 88-note keyboard made for serious musicians. Yes, part of it is plastic, but plastic doesn’t necessarily mean “cheap” – good-quality plastic can be more durable than other materials. And the design itself finally focuses on getting you the best-possible keybed and action, assuming your software will take care of the sound generation.

• Graded hammer action (essential for piano players, as it makes the lower end heavier than the higher end)
• The last key mechanism design by late Fatar founder/designer Lino Ragni
• Double-dipped, “full-body” solid black keys – not hollow black keys. (The press release points out that most digital pianos have hollow keys, which is something I can verify. Unless you play in C major all the time, this is a major problem.)
• 20 dynamic curve settings which “sense” playing in real-time and respond accordingly. It sounds like the piano action equivalent of anti-lock brakes; I have to try it to understand what they mean!
• 4 zones with independent velocity curves, MIDI, program, pedal, and control settings
• Two pedal inputs, plus an illuminated side wheel controller. (The side is an unusual place for a wheel, but I could still see being able to reach it live.)

Now, what’s missing from all of this is a control surface, which bothered me initially – you don’t, for instance, get faders to use as drawbars. Upon reflection, though, I actually think having all that empty space is a huge advantage. If you’re an organ player, you can add a drawbar controller. If you’re controlling unusual instruments, you could add a touchscreen-equipped laptop. Or add a monome. You get the idea.

And the best feature of all may be this: “An aluminum back piece slides out to support another keyboard, sound module, or laptop, without the need for another stand.”

No, my only remaining gripe is that, while the keyboard supports aftertouch, it’s monophonic aftertouch, not polyphonic. Poly aftertouch seems to be a dying breed, but it would certainly have qualified this keyboard as “ultimate.” I’m nonetheless dying to play the Numa Nero. I’ve been waiting a long time for a worthy controller that doesn’t try to make sounds or arrange beats for you or do anything other than talk to your software setup, and this could be it.

US$1274, which goes to prove my point – focus entirely on the controller, and you can keep the cost low without compromise. Weight: 57.3 ponds.

There’s also a 22-pound Numa Nano coming at winter NAMM; keep your eyes out for that one – if it could be just as brilliantly-designed but more liftable, it could be the perfect companion, a nano on the road and a Nero back in the studio (or when you’ve got transport).

Numa Nero Product Page

And yes, it’s worth considering the entire Studiologic range. Ironically, the line they call “vintage” is the one with lots of added controls. They’re absurdly cheap for the quality, have action that can beat most of the pricier options out there, and immensely logical designs that pack maximum playability into the weight and form factor. The designs are, charitably, “workmanlike,” but if it’s more playable, who cares? I also understand they’re easy to service. Now, the only remaining question is why the Italian-based Studiologic seems to be so alone in getting this area right.

Take a weekend, and make something: that’s the challenge behind the Music Hack Day, which joins a growing phenomenon of events built around collective creation. (CDM held its own tangible interface hackday online, which I definitely hope to follow up soon!) Initiated by Dave Haynes of music sharing service Soundcloud, the Hack Day has already hit London. Many of the events were Web app-based and focused on consumption rather than creation of music, but we also saw a chordal synth plug-in and beer bottle percussion instrument.

The Berlin Hack Day, which wound up earlier today, offers still more projects focused on the creation side of music hacking. Having Ableton and Native Instruments as sponsors likely helped the mood. And as you’d expect from one of the world capitals of creative hacking, Berliners don’t disappoint.

Among the projects: a beautiful, elegant 3D sequencer, a fun bird-and-sky multitouch soundmaker with multitouch trackpad input, and a robotic xylophone controlled by monome. Someone even worked out a way to turn NI’s Maschine into a rhythm game, complete with Street Fighter sounds.

I’ve got some of my favorite projects here, but see also an eyewitness report (in English and Italian) at Audio News Room:
Just back from Music Hack Day Berlin
… and keep your eye on the wiki:
Berlin Hack Submissions

xylobot run by monome from robb on Vimeo.

Monomist Rob Böhnke and Ramsey Arnaoot created one of my favorite hackday projects so far: a monome-controlled robotic xylophone. The ingredients: one monome grid controller, one Java application for step sequencing to the output, one Arduino open source controller board, and one terrific xylophone “robot” made of an array of servos that strike the bars of the instrument. Oh, and some hot glue and wood, of course.

Project details

Debugging

Audio loop

Of course, what’s especially impressive is nailing this in just a weekend – imagine what they could do with more time and iterations.

Proof that musical visualizers don’t always have to be trippy, futuristic, Tron-like 3D landscapes (and that’s me speaking as a fan of such things), Gernot Poetsch instead chose a whimsical environment with clouds and cartoon birds, inspired by the graphic identity of Twitter. (No actual Twitter is involved, meaning you lose the, ahem, unreliable, buggy, unfiltered chat network but keep the cutesy happy sky! Works for me!)

The visuals are built in Quartz Composer, which via OSC transmits messages to synthesis language ChucK for noisemaking. The surprise is, the multitouch input is not a Lemur or an iPhone – it’s the new MacBook touchpad under Snow Leopard!

iLoveAcid is a beautiful-looking nodal sequencer by Jakob Penca which uses wireframe “tracks” to guide music playback through a sequencer, transmitting events to your soundmaker of choice via MIDI or OSC. By using curved timelines and connections, it’s a veritable model railroad of music, in which formations combine to form more complex structures instead of simply stepping across a grid. Despite appearances, it is so far only two-dimensional – but then, the z displacement could easily be assigned to some form of modulation. I’m really eager to see the video of this.

One ingredient: Processing, which makes it easier to write visual code and to connect to Java libraries.

Project Page

The hardware controller for Native Instruments’ Maschine software drum machine has been adapted to other software, like Ableton Live. But this is surely the first time it’s been made into a game. Using Maschine’s MIDI output as a game control and sounds from Street Fighter, MaschineFighter is a simple, Simon-style rhythm game. Unlike Simon, though, there’s a twist – instead of rote patterns generated in advance, you face off against a friend and try to out-rhythm each other, battle style. I think it’s actually a pretty brilliant idea, and could become a new sensation for us electronic music nerds – not to mention, it’ll finally test our rhythm in a way electronic performance often does not. (Correction: It is Mac-only, making use of the PYMIDI Objective-C based library, which, since everything else that starts with “Py” usually means Python – a la jThings that mean Java – I assumed, incorrectly, was built on Python. But anyway, if you like the idea, carry on! And, actually, having a pure Objective-C CoreMIDI interface is also pretty awesome.)

Hoping for a video of this, too.

If you have a project that didn’t make this list, or if you add documentation after the fact, let us know.