I plan to buy a Novation launchkey 37 MK3 and I wonder if it’s a good choice as a master keyboard / midi controller for Cubase 12.
I know it is in the midi remote script list but could someone confirm me that the Novation launchkey MK3 series are fully supported ?
The Launchkey MK3 series have a full integration with Ableton live but I know that previous Cubase versions were not supported at all (transport, mute, solo…’ etc.simply didn’t work). Hope the main functions are now supported !
Previously I used it with CBP11 as a Mackie HUI with ports; MIDIN2 (2-Launchkey Mini MK3) and MIDIOUT2 (Launchkey Mini MK3).
It maps OK in CBP12 using the same ports as it used in CBP11, but FULL integration it has not.
The missing functionalities in CBP12 are:
The “>” button above Stop, Solo, Mute does not function in CBP12, but it did in CBP11 using Mackie HUI.
The track colours are not mapped to the track selection buttons on the device (as it does, I believe, in Ableton) . But they are mapped to the image of LaunchKey Mini in lower window view (maybe Steinberg will fix this?). Obviously they are not mapped in CBP11 either.
Poor differentiation between the ON and OFF colours for Track Selection (bright WHITE and not-so bright WHITE) and MUTE (bright YELLOW and not-sobright YELLOW).
Whereas in CBP11 using Mackie HUI, the ON and OFF brightnesses are MUCH MORE differentiated.
That is, you can hardly distinguish the OFF and ON states in CBP12 compared to CBP11.
Selection of banks is confusing in CBP12, so easy to lose track (pun intended) of where you are.
Overall not so good,
Apart from the functionality of the Start/Stop button, which IS better in CBP12, LaunchKey Mini MK3 as a Mackie HUI in CBP11 is more useable (particularly moving through Banks and ON OFF colours).
Great to see that you’re discussing Launchkey [Mk3]! You should find that it integrates very well when correctly set up - providing access to many features, including transport control. Features available are shown in the video provided in the Help Centre article linked above.
The latest firmware available from Components also enables full RGB support.
I’ve now installed the latest LaunchKey Mini MK3 FIRMWARE off ‘Components’ via Microsoft Edge (It doesn’t work with my normal browser, Firefox).
And YES(!), the track selection buttons on LaunchKey Mini MK3 are now colour mapped to Cubase track colours! Fabulous!
The only disappointment for me is the lack of ‘Bank Selection’.
It would be more useful if the track selection buttons (shift+Arp and shift+Fixed Chord) moved the selection display in banks of 8. OR that “Shift+>” and “Shift+StopSoloMute” moved the track selection display in banks of 8.
Currently, Shift+>" and “Shift+StopSoloMute” does not function at all. Track selection (shift+Arp and shift+Fixed Chord), scrolls through both tracks and folder-header, which forces one to abandon the use of folders IF you want these buttons to only select tracks and not the folder-header!
Anyhow, it’s positive progress, but the script just needs some adjustment to enable bank selection instead of just track/folder selection.
I don’t understand what you mean by turning off Mackie HUI in the settings. MAckie HUI appears in Studio Setup only, and mine has no ports connected and is inactive as far as I know. So I don’t know how to go any further with that.
My complaint is not that Launchkey Mini Mk3 isn’t functional under MIDI remote, it’s that one key pad is unmappable (the partner pad with the ‘>’ mark directly above ‘Stop Solo Mute’), and it would be better also if the track buttons only recognised tracks, and not folders too when scrolling through tracks in the mixer window.
Otherwise, LK Mini Mk3 works as expected, although I’d like to be able to adjust the colour intensity of the pads because the difference between ‘off’ and ‘on’ isn’t that great for some colours.
Wondering whether anyone is having issues with writing automation with the launchkey 37 mk3 and the midi remote script.
I’m able to write automation normally when using the scripted controls like the default volume/pan. However, using the mod wheel or the custom knob mode, automation changes aren’t correctly reflected in the cubase automation lanes. The lanes aren’t even created when recording automation at all.
What the image shows:
(1) midi event shows recorded mod wheel automation but that lane is just a straight line in the automation lane.
(2) The lane with visible changes is the expected behavior using the scripted volume control.
(3) My midi port settings. Maybe I’ve set things incorrectly?
Finally, is there a way to access custom knob mode mapping or any shift level page using the midi remote editor? I can’t seem to map secondary controls that are accessible through the shift command on the controller.
i think there’s a bug in Midi-Remote-Implementation by Steinberg.
My Launchkey 37 does not work well with Cubase 12 and I’m not the only one. No Problem in Cubase 11.
Steinberg support is horrible (no solution no answer according to the problem). In Ableton Live lite there’s absolutely no problem - all works fine so it seems not a problem with Novation launchkey.
At this point I can not recommend using Cubase 12 with Launchkey and new midi remote functionality.
Bought a Launchkey 37 a few days ago, and it makes my Cubase 12 freezes and crashes constantly. When it’s unplugged I have no problem anymore, but while it’s plugged I can’t work at all.
Any Idea ? Should I ask for a refund and get another keyboard ?