I just picked up a Novation Launchkey MK4 61 and am having trouble creating a MIDI map. I am still within the return window. I saw that @paul said that there are issues with the current Linux kernels. I’m thinking that may be the deciding factor for whether I return it. Any advice regarding whether to keep or return it?
I’m thinking of replacing it with the Arturia KeyLab MK3 61. Does anyone have trouble with the midi map for that one? I don’t see one in the choices of midi maps within Ardour, so does that mean I will need to create a new one for the KeyLab 61?
Yes, my Linux kernel is Linux 6.11.0-21-generic
It is seeing my keyboard Bus 001 Device 003: ID 1235:0146 Focusrite-Novation Launchkey MK4 61
As for why I want to create a MIDI map, it is because I am stumbling through setting this up and have almost no idea what I am doing. Lol! So, I would be very happy to be able to use the builtin support that is available. I’m sure I’m missing something!
I’ve noticed that when I go to the Novation website, it says “no product detected”. So, I’m thinking that may be where I need to start.
Ok, thank you! I managed to get it to detect the controller by installing and using Chrome instead of Brave. So, some progress. I’ll let you know if I get stuck again. Thanks so much!
@paul Just to make sure I have this set up right, in Ardour, I go to Edit>Preferences>Control Surfaces. I toggle Generic MIDI, then double click to show Control Protocol Settings. Select the Launchkey as my MIDI device and the Novation Launchkey 49 for the MIDI Bindings. Correct?
No, not correct at all. That’s a totally different device. Generic MIDI is for devices that we have no custom support for. You should see Novation Launchkey 4 in the top level of control surfaces, that’s the one you want. If you don’t have that, you don’t have a new enough version of Ardour.
Hi @paul, I finally got Ardour updated. I think I have made some progress, because my Launchkey is now recognizing that it is connected to a DAW. This is showing on the controller screen. So, yay!
I had a couple choices for which channels to select for the incoming and outgoing MIDI. I have tried all of the Novation ones, but this is what that looks like. I chose the top Launchkey selection “Launchkey MK4 61 Launchkey MK4”.
With these settings, the Launchkey is recognizing that Ardour is there, but I am not able to use any of the control keys with the controller. Basic MIDI is still working, but nothing related to the DAW. Do you have any suggestions? Thanks!
As long as the two ports have the same name, the current code cannot work correctly. This is a bug in ALSA that we will have to work around. I just don’t know how to at this point.
Other versions of ALSA correctly identify the ports with different names.
Does that mean I won’t be able to use the controls on the keyboard at this time? There’s probably no way for me to rename the ports different things, is there?
For what it’s worth. You might find this thread interesting.
I’ve spent a week trying to get the Launchkey MK4 to work with Ardour, and it’s just not going to happen. When coupled with the fact that, even if the ALSA bug is fixed, any custom configuration for the Launchkey has to be done either through Novation’s website or through a stand alone software package that is not available for Linux, I’ve decided to return it for something else. I just don’t know what yet.
My recollection is that the “custom configuration” is done via a web-based thing, and just requires a browser with webMIDI enabled. That’s certainly what I did.
Also, I don’t think that any custom configuration is actually required at all.
@jondbennett Thanks for the heads up! I appreciate seeing that a fix is being pursued.
I agree with @paul that the customization of the Launchkey is done via the Novation website and a MIDI-enabled browser. I have been able to do all the updates on mine with Chrome. I tried it first in Brave and Firefox, but it didn’t work. With Chrome, I can update the hardware and see all the custom configurations available.
So, I think I’ll hold onto my Launchkey and wait for a fix. Happily, it doesn’t change my workflow, as this is my first MIDI keyboard with DAW integration. So, I’ll just keep using my keyboard for DAW control right now.
Paul, I am willing to help test what you need as well. I don’t know most of what I am doing in the terminal window, but if there is some way for me to help, I’ll be glad to. Thanks for working on this.
