Novation Launchpad Pro

[NateTheLightingGuy]

Here is the fixture definition for the Novation Launchpad Pro's RGB matrix.

User manual: https://customer.novationmusic.com/site ... ide-en.pdf

Programmer's Guide: https://customer.novationmusic.com/site ... uide_0.pdf

The manual unfortunately does not provide an easy way to connect the Launchpad to QLC+ (or other lighting software in that matter) because it was designed primarily for use in Ableton Live. I had to experiment with it in QLC+ in order to find out how to get it interfaced and working properly.
The good news is, I have found an easy way to get both talking to each other and I am making a video on how to interface the Novation Launchpad pro with QLC+. I'll be sure to post it when it's finished.

UPDATE 5/3/19: Just added the Input Profile.
UPDATE 7/28/2019: Video is completed and you can view it here: viewtopic.php?f=30&t=13455

[Marvil]

thanks bro

[mattallmighty]

Is there a fixture file for Launchpad S?

[NateTheLightingGuy]

Is there a fixture file for Launchpad S?

No, I haven't seen one made for it, sorry. If you wanted to experiment with yours, I'm sure you could probably make one!

[mcallegari]

The Launchpad Pro input profile was added on April 30th, 2016 to QLC+
I'm wondering what's the difference with this one

[NateTheLightingGuy]

The Launchpad Pro input profile was added on April 30th, 2016 to QLC+
I'm wondering what's the difference with this one

Here are the differences:
1. My version uses OSC rather than MIDI. Using OSC helps attain faster response time with the Launchpad Pro, and there is a noticeable difference in response time.
2. David Giardi's fixture Profile has all the buttons set to Type: "Button" Including the pads. My input profile has the pads set to Slider because they are velocity sensitive and will respond a certain level depending on how hard you press the pad.

Also the instruction on David Giardi's fixture Profile on assigning colors on the Launchpad Pro was by MIDI feedback http://www.qlcplus.org/forum/viewtopic.php?t=9375, I found that using a separate universe and treating it like a DMX output device (with MIDI plugin) allows you to easily change colors on it like a DMX light. If you watch my video series I made on it, I go in greater detail on how to take advantage of this. https://www.youtube.com/playlist?list=P ... mJjBON1PBN

I know that there is more than one way to interface this device (like how David Giardi did it), I just found this way to provide the most flexibility when programming lights and controls to use the Launchpad Pro.

Thanks for asking, hope this helps!

[mcallegari]

Alright, thanks.
In general I would keep both the profiles.
However, I still don't understand where's the OSC trick
This page (https://novationmusic.com/en/launch/launchpad-pro) doesn't mention OSC anywhere.
Did you use some sort of MIDI<->OSC bridge?

[NateTheLightingGuy]

Alright, thanks.
In general I would keep both the profiles.
However, I still don't understand where's the OSC trick
This page (https://novationmusic.com/en/launch/launchpad-pro) doesn't mention OSC anywhere.
Did you use some sort of MIDI<->OSC bridge?

Actually no, Now that I looked more deeply into what I did, the Launchpad does use the MIDI Plugin both ways. When I was first experimenting with the Launchpad Pro, I thought that having the Input Profile set to type: OSC reduced the latency but now that I tried it with type MIDI again, I have determined that something else was causing that issue, and having the type set to OSC had no effect. I have attached the corrected Input profile to state type MIDI.

Here are the updated differences between David Giardi's and my input profiles:
1. David Giardi's was made with QLC+ version 4.10.2, mine was 4.11.2
2. Mine has the addition of: "<MIDISendNoteOff>False</MIDISendNoteOff>" in the Input Profile's code. No such parameter was found in David Giardi's Input Profile.
3. David Giardi's fixture Profile has all the buttons set to Type: "Button" Including the pads. My input profile has the pads set to Slider because they are velocity sensitive and will respond a certain level depending on how hard you press the pad.
4. Some of the labels for the buttons use slightly different names for the arrow buttons. (David Giardi's "Run 7" vs. Mine "Row 7 Arrow")
5. And last, we both have a different numeric naming system for the pads. (horizontally ascending vs. descending)

Those are the differences I could find looking at the code for each input Profile.

[mcallegari]

Thanks for the further info.
One last question before I upload your profile: did you create it from scratch or did you start from Giardi's profile?

I ask this only to know if I need to credit both of you or just you, because in the end I will overwrite the current profile with yours.
Thanks

[NateTheLightingGuy]

I created my Launchapad Pro Input profile from scratch.
Thank you for adding the Input Profile and Fixture Definition.

[mcallegari]

Input profile updated.
What's the fixture definition for? Loopback usage?

[NateTheLightingGuy]

The Fixture Definition maps all 128 color options for all the buttons and pads on the Novation Launchpad Pro, when the user wants to set the color, they can see the 128 options making it easier to select a color on the fly. It works just like the color presets on a standard DMX light fixture. I show how it all works in my Connect the Launchpad Pro to QLC+ video series: https://www.youtube.com/watch?v=kb_ciAg ... dex=2&t=0s

Launchpad Pro Color Palette

[mcallegari]

OK, I had to watch part 1 and almost all part 2 to realize you're most likely suggesting an inefficient way to manage this device.

You suggest to occupy a universe with a fixture basically just to see the color it does. And as far as I can see, not without difficulties (at some point you can't find the button you want to light up )
Probably you're missing one handy function I introduced in QLC+ a few years ago: custom feedbacks.
Basically I added them for the AKAI APC mini.

When you hit on "auto detect" in the widget properties dialog (which can be opened by double clicking on the widget BTW) you should also press on the "Custom feedback" button on the left.

Please read (again) the docs: https://www.qlcplus.org/docs/html_en_EN/midiplugin.html
We even added a "AKAI APC LED Feedbacks" for this reason.
We can easily add a "Novation Launchpad Pro" section, with all the colors and values (even with a small preview box showing the color) as a reference for users
We can also add the device here (https://www.qlcplus.org/docs/html_en_EN ... vices.html) and add a note regarding Note velocity and live mode.

What do you think?

[NateTheLightingGuy]

OK, I've taken some time to read the docs, play around with the launchpad and try make the pads light up with feedback. Unfortunately, After playing around with the settings I have not been able to make the pads light up. I have been using the custom feedback option following David Giardi's instructions and trying other options as well. I've read through the programmers guide as well to see what that could tell me. https://resource.novationmusic.com/site ... uide_0.pdf
I still could not figure it out. It seems as though LED feedback may need specific codes in custom feedback in order to light up the pads. I might reply to David Giardi's post to see if he could provide more detailed instructions on how he made it work.

I do like the idea of making custom feedback work (and have a reference color chart as well! ), but there are three things I see that can be more easily accomplished by using a separate universe to program button lights.
1. Animated buttons. You can have a button set a certain color when it's on or off, but if you want the button to flash or change color when enabled. I don't see a way of doing that in custom feedback, unless custom codes are allowed.
2. Instances of needing to control more than one button color at a time. (custom codes would allow you to do this.)
3. Programming launchpad light shows.

I'm glad you pointed out the custom feedback. I previously overlooked that option. As far as I can tell, that could work for most user's needs for buttons, virtual sliders, and pages, but I can't find out how to get the lights to come on on this device.

After I finish my video series about connecting the launchpad pro how I originally did it. If I can get the feedback to work out, I might make videos about doing it that way as well.
In the end, it may require device specific programming for the launchpad pro in order to fully support it's features. As for me, I can only conclude that using a separate universe is the best way to go about this for now, and I've never had any trouble using it this way when setup properly. It is 100% compatible with all assignable buttons and their preset color palette.

I believe this can be listed as a supported device, with the mention of note velocity and live mode as you said. One thing else I forgot to mention is this is the Novation Launchpad mkII. It's not explicitly stated but this is the second generation of the Launchpad Pro, I believe this is important to mention since mkIII is out now.

[mcallegari]

Nate, I don't have a Launchpad pro, but I have a AKAI APC mini, which in principle works the same.

The configuration is:
- universe 1: DMX USB adapter
- universe 2 (but could be any): AKAI APC
Screenshot

As you can see, the APC is set as input AND feedback.
Then I created a VC button and assigned APC button 3-3 to it.
I wanted OFF state red blinking (value 8) and ON state green (value 2), as indicated here.
So I've set custom feedbacks as shown

In this case, feedback values are MIDI values, so from 0 to 127 only. Considering your fixture definition for the Launchpad pro (which is not a fixture, right? ) DMX values (0 to 255) should be divided by 2 to fit into MIDI.
So for example if you want to do the same I did, you could have OFF state bright red (value 5) and ON state bright green (value 20)
It's pretty simple when you understand it.
Once you do, we can write that famous color table with values

Project attached in case you need to have a look at it.

[NateTheLightingGuy]

Thank you for working with me on this, After looking at the pictures on how you setup your interface and giving it some more thought, I realized that I did not check the feedback box and that it had a different channel to feed midi back to. After that, I got the custom feedback to work properly! It just required "MIDIIN2 (2-Launchpad Pro)" as the input and "MIDIOUT2 (2-Launchpad Pro)" on the feedback channel In programmer mode.

Launchpad Pro setup MIDI.png (10.2 KiB) Viewed 7776 times

I guess I'll be remaking my Connect the Novation Launchpad Pro to QLC+ video series to support both ways for interfacing!

Upon playing with the color mapping, I've found that even though the launchpad is connected via MIDI, It still likes the 0-255 value feedback for colors, just like your AKAI APC as you described in the docs.

This color chart below was taken from the programmers guide, the values just need to be doubled.

I'll update my fixture definition's colors to match this chart and update my post when it's finished, so the people who want to create light shows with the launchpad can do so more easily.
Again, thank you Massimo for taking some time to help me with this!

[creativeking]

Does anyone know if there is also a fixture file and input profile for the Novation Launchpad mini MK3?

With the Launchpad pro file, there are 8 buttons that do not respond at the Launchpad mini MK3.

Or if someone has an explanation how to change the fixture file and input file to get these buttons working, that would be very nice.

Thanks!

[VFX]

Does anyone know if there is also a fixture file and input profile for the Novation Launchpad mini MK3?

Ordered mine today and going to work on this

[oggio]

Any idea if it can work with the first version of Novation launchpad?

[GGGss]

Should be possible ... you have to set the correct emulation mode. (See manual)