Introduction
The Launchpad is a midi controller by Novation, designed for use with Ableton Live. There are many reviews and videos showing the Launchpad and Live in action, but there isn’t a lot of information about using it with other software. I wanted to add more buttons and faders to my Bedroom DJ setup, which could be done with other devices, but all those blinking buttons and colourful LEDS were too much to resist.
The Problem
The Launchpad works well with Ableton Live, and Torq can be re-wired into Live. With this setup, Live controls the Session and Mixer pages, and you can map the buttons on the User1 and User2 pages to the controls in Torq – enable LaunchPad in Torq’s MIDI settings, then just right-click the Torq control, then press a button.
This works, but it’s rather disappointing and boring because the LEDs don’t turn on and off. You see, Live contains some built-in logic that receives incoming MIDI signals from the Launchpad, translates the signal into actions and events in Live, and outputs MIDI signals back to the Launchpad to control the LEDs.
Novation’s Automap program promises to map Launchpad buttons into any software, but from what I can tell it really only works with VST plug-ins and a few other software packages.
The Solution
Novation has produced the LaunchPad Programmer’s Reference Guide, which describes the MIDI notes and control signals used by the Launchpad. Armed with this information, the logic built-into Live can be re-written and customized using a Pure Data patch. With this setup:
- A button press on the Launchpad sends a MIDI note
- The MIDI note is mapped to a control in Torq (or any other MIDI-aware application) and triggers some action.
- The MIDI note is also received by Pure Data, which processes the note and sends a MIDI note back to the launchpad. The velocity of this note determines the colour and brightness of the LED.
Progress So Far
To date I have created a simple patch that is working quite well and which I will upload here shortly along with usage instructions. Using it, I’ve created a customizable layout for Torq that maps Quick-Cues, Looping, Effects on/off, Master/Sync, Internal/External control and more.
To create a mapping, an object is created for each button and assigned a MIDI note, a button type (on/off and momentary), and a colour. Unmapped buttons are off, mapped buttons are dimly-lit when inactive and brightly lit when activated. Loading different Pure Data patches configured this way allows you to create an LED-scheme for multiple programs.
Still to Come
To fully reproduce all the features available with Live, I still need to implement:
- The page, session, user1, user2, and mixer controls. Being able to switch pages turns the 64-button grid into an N-button grid. 64 buttons seems like a lot, but you’ll use them up fast!
- Faders. This is a very cool feature of the Launchpad that lets buttons act as faders and knobs. To implement this, Pure Data needs to map a range of MIDI notes into a single MIDI note with a range of velocities. It will also change the routing of MIDI signals. With the basic buttons, LaunchPad <–> Pure Data and LaunchPad –> Torq. To implement a fader will require LaunchPad <–> Pure Data and Pure Data –> Torq.
I’m confident this can happen and it’s just a matter of finding time to build it.
Other Ideas
- implement the LED logic in Max for Live to toggle LEDS for the User1 and User2 pages from within Ableton Live
- implement the LED logic in a VST plug-in and launch it from within Torq (or any other app supporting VSTs)


