Hacking a Remote Codec for the Launchpad Mini

42514I decided that I need a better way to select patterns/loops on Reason devices such as Redrum, Matrix and Dr. Octo Rex during live performances.

I know the Livid Ohm64 will do the job and it looks super cool but it’s expensive too. And since I already have a nanoKontrol2 which I’m quite happy with, the Ohm64 seemed like a bit of an overkill.

After a bit of online research I decided on a Novation Launchpad instead and went off to my local music store to get one. I looked at both the full-size “S” model and the “Mini”, both of which I knew to be supported by Reason from my research.

I decided on the Launchpad Mini. I’m OK with the small buttons and I only have so much space on my desktop… plus it’s a bit cheaper than its bigger brother, so what’s not to like?

Well… it turns out that Novation did’t bother implementing their AutoMap software for the Launchpad Mini. And they are not providing any remote codecs for Reason either. So the Launchpad Mini basically just works like a keyboard in Reason… and it’s not even velocity sensitive!

So much for the advertised “Reason support”.

It is  possible to map buttons in Reason to the Launchpad Mini of course, but the buttons on the control surface don’t light up and show the “state” of the software, which was what I expected.


Luckily I applied for access to the Propellerhead Remote SDK a while back and decided to get my hands dirty.

I haven’t actually used the Remote SDK before and it turned out that the most difficult and frustrating part of developing my first remote codec was actually figuring out how to download the SDK! Let’s just say that the Propellerhead developer support could be better…

After I got hold of the SDK things were actually pretty straight forward. It probably took me 7-8 hours to figure everything out and put together the codec. I have absolutely no love for Lua but the Remote API is clean and logical, and the documentation provided in the SDK is pretty good.

I decided to implement most buttons on the Launchpad Mini as simple toggle buttons. Since I plan to map individual Launchpad buttons to different devices in Reason, I decided not to map the buttons to anything by default. I wouldn’t make sense, really.

For the top row of round buttons on the Launchpad Mini (labelled 1-8) I decided to do something special. Rather than acting as toggle buttons, these buttons are mapped to the bar position in Reason: As the song pointer in Reason moves from bar 1 to bar 8, these buttons light up one by one. When the song pointer hits bar 9, the Launchpad “wraps around” and starts from 1 again.

Very cool, if you ask me. I tend to structure the music I make in 8 bar sections and I find that having a visual cue like this during a busy live performance is very useful. This way, I can focus on other aspects of the performance without losing track of the bar count.

The codec can be downloaded from the GitHub. Enjoy!

6 thoughts on “Hacking a Remote Codec for the Launchpad Mini

  1. Hey,

    Just found this and it’s really great to see that you have done this.
    I’m having a bit of trouble with the remote map side of things and basically wanted to map the buttons A-H for the transport controls in Reason however it’s not working for me. 😦
    Can you contact me please? richard.hider AT ntlworld.com


    • Actually I managed to get the remote map working after all. 🙂
      This is really useful, one suggestion though.

      Would it be possible to have 16 of the pads set up as midi notes to control Kong??
      Thanks again.

      • Glad to hear you solved it.

        Yes, I’m pretty sure you can make the pads play notes and map them to a Kong device. I suggest you take a look at some of the codecs that come with Reason (hint: on Windows they are found under the C:\ProgramData folder which is hidden by default) – this is how I figured out how to get my codec working.

        If you haven’t already done so, I also suggest you sign up for the Remote SDK. This will give you access to some basic documentation and a forum where you can ask questions. You will need to supply a company name for “legal reasons” though… go figure. In this day and age where even hardware manufacturers want us to get involved and hack their stuff you have to wonder why a company like Propellerhead does not take a more “open” approach.

      • Hey, I’ve got 16 pads set up as Kong and Redrum triggers now. Would it be ok to share the modified codecs online? I will list you in the credits and link to the original files.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s