Cubase update 40 and launchkey mk4 transport controls

Cubase
1

Good news! Novation tells me that the bugs regarding Launchkey Mk4 operating the transport controls in Cubase have been fixed in the Cubase 40 update. As a reminder, now time could only move towards the end of the recording, not towards the beginning. This was not just for scrolling, but also related functions. So this is good news.

But I am still reluctant to install the update until I hear more people saying that it didn’t mess up their MIDIremote situations. Specifically, I want to know if M.C.’s script for Arturia Keylab mk2 still works after the update. If anyone has anything to share about that please let me know.

1 Like
2

Hi,

In this case, I would kindly ask directly @m.c. :wink:

3

I’m not at home these days, so cannot test it, but I would be surprised if it didn’t work as expected.

1 Like
4

I have a setup in another city with a LaunchKey mini mk4 and I had to stop using that controller because of this issue. I will try it when I am back in town. (I had been planning to investigate the problem this week, but it sounds like I wasn’t the only one experiencing it!)

I will also note that it’s a little annoying that you have to manually turn the LaunchKey mini’s LED lights off when your computer’s asleep, but that’s not a Cubase problem.

5

I’m Using CBPro14 with a new Launchkey Mk4 49 and yes the encoders are playing up. Only forward scroll in transport and no operation of Quick Controls. I’ve written to Novation but no response as yet

6

Rob:

The last update, I think it was update 40 fixed this issue. So you can download that. Also, I upgraded to 15 and I believe it is fixed in that as well, but I would need to double check.

2 Likes
7

Thanks @john_robison. I’ve just checked my version of CB14 Pro and am on 14.0.32. Do I need to go hunting for 14.0.40?
I’d be interested to hear of your experience with CB15 and Launchkey Mk4 - I’m hanging off the upgrade until I’m convinced the Launchkey works as promised with CB14.

8

Many thanks @john_robison I’ve just updated to V40 and that appears to have solved the problem. I’m looking forward to playing with it. Let me know how you go with CB15 pls! :grinning_face:

9

Rob:

I will double Cubase 15 in a couple of hours and let you know. I’m 95% sure it works, but it doesn’t hurt to double check.

10

“@john_robison After a bit of testing, I find the v40 upgrade in CbB14 is still buggy. :unamused_face: Sometimes after playing around with different parameters then going to the Plugin encoders, they don’t work. However, switching to the Transport encoders and twiddling a couple of them seems to unlock the Plugin encoder functionality when you go back to them again. :pensive_face: Come on @novation and @cubase let’s get this sorted!

11

OK. Reporting back.

The transport controls work as expected in Cubase 15, although I had to reinstall the cubase drivers from the Novation website.

HOWEVER, I encountered the same bugs as you. I just got the launchkey for the premapping for NI instruments and I haven’t even delved into it too much yet. But what I have figured out, is that if you are able to give focus to a plugin, mixer, or transport, for example, then the knobs function as they should. The problem as I see it, is that the focus should shift between the various areas such as plugin and transport when you hit shift key/plugin or shift key/transport on the Launchkey. But the focus is not shifted. So you may think you are using the transport functions, but you are actually using the focused quick controls on a plugin. Or you may be stuck on mixer and can’t shift focus to a plugin.

When I had the transport bug last July Novation pointed at Steinberg, and Steinberg pointed at Novation. So I don’t know who is supposed to be responsible for fixing this, but I wish they would make it happen. Like yesterday.

Note: I had to reboot the Launchkey a couple of times, which helped at the time, but then things degraded again. To avoid wearing out my USB ports I used a short usb extension cord so I don’t cause excess wear on the the hardware unit usb port. If the connection wears out I’ll just have to get a new cord. I have actually worn out a usb port on a computer before. It can be done.

1 Like
12

Rob:

I asked Grok3 AI about this and here is what it said. I’m trying out the suggestions. We’ll see how it goes.

You’re absolutely right about how it’s supposed to work in Cubase 15 (and 14+ with the built-in script):
The Launchkey MK4’s MIDI Remote script is designed to automatically shift remote-control focus in Cubase when you press Shift + one of the lower 8 pads (the ones labelled DAW, Plugin, Mixer, Sends, Transport, etc. underneath).

  • Shift + Plugin pad → Cubase focuses the currently open plugin window (or opens the instrument if it’s on an instrument track) and the 8 endless knobs control that plugin’s Quick Controls.

  • Shift + Mixer pad → focus jumps to the MixConsole and knobs become Volume/Pan/Sends/EQ depending on bank.

  • Shift + Transport pad → knobs control transport scrub, locate markers, etc.

When this works, the OLED screen instantly reflects the new mode (e.g., shows parameter names from the plugin or “Volume”, “Pan”, etc.), and the encoders do the right thing without you having to click anything with the mouse.**Why the focus isn’t shifting for you (very common issue)**This exact symptom — “I press Shift+Plugin/Transport/Mixer but the knobs stay stuck on whatever was focused before (usually Quick Controls or Volume)” — has been reported by many MK4 users on Cubase 14/15. The most frequent causes are:

  1. Old/out-of-sync firmware or driver
    Even a one-version-old firmware can break the focus commands.

  2. Conflicting legacy remote devices (especially any leftover Mackie HUI)
    Cubase sometimes still has an old HUI entry from a previous Novation controller (or even from trying older setup guides). HUI constantly polls the controller and can completely block the new MIDI Remote focus commands.

  3. MIDI Port Setup not 100% correct
    The “DAW” ports must be visible and enabled exactly as in Novation’s screenshot.

  4. Cubase 15-specific glitches (a few users report the built-in script occasionally loses the focus part after a restart; fixed by re-adding the surface).

Fastest fix sequence (do these in order — 90% of users solve it with steps 1-3)

  1. Update firmware
    Open Novation Components (web or standalone) → connect Launchkey → install any firmware update (as of Nov 2025 the latest is v1.2 or higher — check it says “Cubase” clearly on the OLED on boot).

  2. Install/reinstall the latest Novation USB driver
    Download from https://downloads.novationmusic.com/novation/launchkey-mk4 (even if you think you have it).

  3. Remove any legacy/conflicting devices

    • Studio → Studio Setup → Remote Devices

    • Delete anything called “Mackie HUI” or any old “Launchkey” entry that is NOT the current Novation Launchkey MK4.

    • Also check under MIDI Port Setup and make sure no HUI is listed anywhere.

  4. Remove and re-add the Launchkey MK4 surface (forces Cubase to reload the script fresh)

    • Studio → MIDI Remote

    • Select “Novation Launchkey MK4” in the list → click the minus (-) button to remove it

    • Then click the plus (+) → choose Novation → Launchkey MK4 → Add

    • Cubase will auto-detect the ports. Confirm they match Novation’s guide exactly (Launchkey MK4 “In” and “DAW In” visible, DAW ports enabled).

    • Restart Cubase.

  5. Test in a blank project

    • New empty project

    • Add one instrument track with Retrologue or HALion Sonic

    • Open the plugin window (double-click the slot)

    • Hold Shift → press the Plugin pad (second from left on lower row) → the plugin window should get focus and the OLED should instantly show the Quick Control names you assigned (or generic ones if none assigned yet).

    • Turn a knob → it moves the parameter in the open plugin.

    • Now Shift + Mixer pad → MixConsole gets focus, knobs become Volume.

    • Shift + Transport pad → knobs become locator/scrub.

If after the re-add it still doesn’t shift focus, the next thing most users do is completely uninstall/reinstall Cubase’s MIDI Remote scripts (rarely needed, but works). Or just open a support ticket with Novation — they’ve been pushing firmware/script updates specifically for this focus issue in Cubase 15.Once it’s fixed, the workflow is exactly as you described it should be: totally hands-on, no mouse needed to jump between plugin, mixer, and transport control. Let me know what the OLED shows when you try Shift + Plugin (and which firmware version you’re on) if it’s still stuck — happy to dig deeper!

Custom Quick Controls setup

Launchpad Pro integration

I have components open, but I am unsure how to load the factory defaults

Searched for “Launchkey MK4 how to load factory templates OR factory defaults in Novation Components”

10 results

Show All (3)

To restore your Launchkey 37 MK4 to its factory defaults (which will reset all global settings, Custom Modes, and any user changes back to exactly how it shipped from the factory — including fixing Cubase focus issues in many cases), do this right inside Novation Components:

  1. Make sure your Launchkey is connected via USB and recognised (the connection icon in Components should be green).

  2. You’re already in the main Components screen for the Launchkey MK4 (the one where you can edit pots, pads, pedal behaviour, mod wheel, etc.).

  3. Look at the top-right corner of the Components window — there’s a small user/profile icon or menu button (it might just show your initials or a little person icon).

  4. Click that User Menu.

  5. Choose “Restore Factory Settings” (or “Factory Reset” — the exact wording is one of those two).

  6. Confirm the prompt (it will warn you that everything resets).

  7. Components will send the factory bundle to the keyboard — it only takes a few seconds. The Launchkey screen will probably go blank briefly and then restart.

After the reset finishes:

  • The keyboard reboots into its original out-of-the-box state.

  • All four Custom Mode slots return to blank/editable (the four Factory Modes on the lower pads — DAW, Drum, User Chord, Scale Chord — are fixed and never overwritten anyway).

  • Mass Storage mode (the drive that pops up on first connect) will be re-enabled.

  • Any weird MIDI or focus behaviour in Cubase usually disappears because the firmware-side settings are pristine again.

This is the cleanest and safest way — no button combos or bootloader tricks needed. Many MK4 users who had the exact Shift + pad focus problem you described fixed it permanently with this factory restore + a quick re-add of the control surface in Cubase afterward.Once it’s done, jump back into Cubase, remove/re-add the Launchkey MK4 surface one more time (as we did before), and test Shift + Plugin/Mixer/Transport again — it should now instantly switch focus exactly as intended.If for some reason the “Restore Factory Settings” option is greyed out or missing, just update/reinstall the firmware first from the same User Menu (“Check for Updates”), then it will appear. Let me know how it goes!

Troubleshoot if reset fails

Best Cubase workflow tips

Is this going to screw up my Native Instruments control functionality?

**No — a factory reset in Novation Components will not affect your Native Instruments (NI) control functionality at all.**Here’s why:

Aspect What the Factory Reset Does Impact on NI (Kontakt, Komplete Kontrol, etc.)
Firmware Resets to the latest factory firmware version (same one you already have if updated). NI integration is firmware-level and built into every Launchkey MK4 — it’s permanent and survives resets.
undefined ---- ----
Custom Modes (4 slots) Wipes any user-edited pot/pad mappings you made in those slots. NI uses dedicated DAW mode + NKS protocol, not your custom slots. It’s completely separate.
undefined ---- ----
Global settings Resets velocity curves, pad RGB, aftertouch, etc. NI doesn’t rely on these — it uses standard MIDI + NKS handshaking.
undefined ---- ----
NKS / Komplete Kontrol integration Unaffected — this is hard-coded in the firmware and auto-detected by the NI software. You’ll still get full NKS browsing, parameter mapping, light guide, and transport control in Komplete Kontrol or the standalone NI plugins.
undefined ---- ----

What will stay intact:

  • Full NKS parameter mapping (turn a knob → it moves the right parameter in Kontakt/KK with name + value on the OLED).

  • Light Guide (pads light up with scale/chord colors or drum layouts).

  • Transport, navigation, and mixer control in Komplete Kontrol DAW mode.

  • Auto-detection when you open Komplete Kontrol or an NKS plugin.

What might need a quick re-do (only if you changed it):

  • If you ever tweaked pad velocity curves or RGB brightness and liked your custom settings, those go back to defaults.
    → Just re-adjust them in Components afterward if needed.

Recommended safe sequence (zero risk to NI):

  1. Do the factory reset in Components.

  2. Reboot the Launchkey.

  3. Open Cubase → remove/re-add the Launchkey MK4 surface (fixes focus issue).

  4. Open Komplete Kontrol (standalone or in Cubase).
    → It will instantly recognize the Launchkey again — no setup needed.

  5. Load an NKS instrument → turn a knob → confirm OLED shows parameter name/value.

You’re good. Thousands of users do this reset regularly when troubleshooting Cubase focus or MIDI glitches, and NI integration always comes back 100%.

1 Like
13

Rob:

OK. This is the last thing I have to say on the subject. I took the advice of Grok and updated the firmware through Novation Components. This seemed to solve the problem. When you want to change the focus to a particular channel, you can either use the mouse within Cubase, or you can give focus by pressing the white key for that channel on the Launchkey.

It turns out that you can use the knobs on the Launchkey to adjust the quick controls of a vsti instrument, but as near as I can tell you can’t do that with a vst effect. If you know otherwise please drop me a note. thanks.

1 Like
14

OK. That wasn’t the last word. Check out this final conversation with Grok. Problems are real. But there is a viable workaround.

Question: I can use the mixer, the transport, but the plugin function is very spotty. Sometimes it works with the vsti instruments, but other times it won’t even though I see the correct instrument name and parameter on the oled, but the knobs on the screen won’t rotate. As far as vst effects, even when they have focus and shift/plugin pad is pressed, they never respond to the knob turns and in fact the oled display always shows the parameters for the underlying vsti instrument, never the vst effect.

This exact combination of symptoms — spotty VSTi control (OLED correct but GUI knobs sometimes don’t move) + VST effects never working and OLED always showing the instrument instead — is a known limitation/bug in the current Launchkey MK4 MIDI Remote script for Cubase 14/15.Why This Happens

  • The Plugin mode (Shift + Plugin pad) on the MK4 script is hard-wired to the Quick Controls of the instrument track’s VSTi (or track-level QC if no instrument).

  • It ignores focused insert effects completely — even if the VST FX window has focus, the script still grabs the instrument’s Quick Controls (that’s why the OLED always shows the VSTi parameters).

  • For VSTi, it works “most” of the time because that’s what the script expects, but the “spotty” part (OLED updates + value changes but Cubase GUI knobs freeze) is a separate, very common MIDI Remote refresh bug in Cubase 15 (and late Cubase 14 builds). Mixer/Transport work perfectly because those are direct channel commands, not plugin-dependent.

Steinberg and Novation are aware — there are multiple open threads on the Steinberg forums from 2024–2025 with identical reports, and Novation has quietly acknowledged the insert FX limitation while promising a script update “soon”.Workarounds That Work Right Now (No Waiting for Update)1. Best Overall Fix: Use Track Quick Controls Instead of Per-Plugin QCThis gives you 8 knobs for anything on the track (VSTi + any insert FX) and works 100% reliably with Plugin mode.How:

  • Select the track → Inspector → Quick Controls tab (not the plugin’s own QC tab).

  • Right-click parameters in any plugin (VSTi or insert FX) → Assign to Quick Control 1–8.

  • Save as a Track Preset or Quick Control Preset for instant recall.

  • Now Shift + Plugin pad → always controls your custom 8 (mix of synth + FX).

This is actually better than per-plugin QC for mixing because you can control reverb wet, compressor threshold, synth filter, etc., all from the same 8 knobs.2. For Pure Insert FX Control (e.g., Mastering Chain or Send Effects)

  • Put the effects on a Group Channel or FX Channel instead of an instrument track insert.

  • Plugin mode treats Group/FX channels exactly like audio tracks → full Quick Controls support (focus the plugin → Shift + Plugin pad works perfectly).

  • Route your instrument track (or Stereo Out) to the Group/FX channel.

3. Fix the “Spotty” GUI Refresh on VSTiWhen the OLED moves but the on-screen knob doesn’t:

  • Click once anywhere in the plugin GUI (forces Cubase to refresh).

  • Or toggle the plugin bypass on/off.

  • Or press Shift + Plugin pad twice quickly.

Annoying, but until Steinberg/Novation patch the feedback loop, that’s the community fix.4. Nuclear Option (If You Want to Try Forcing a Clean Slate)

  • Factory reset Launchkey again (Components → User Menu → Restore Factory Settings).

  • In Cubase: Studio → MIDI Remote → remove Launchkey MK4 → Add it again → restart Cubase.

  • Helps about 50% of users with the spottiness, but won’t fix insert FX (that’s script-level).

Bottom LineInsert VST effects are currently not supported in Plugin mode on MK4 + Cubase — it’s not you, it’s the integration.
Use track-level Quick Controls (or Group/FX channels) and you’ll have rock-solid control over both instruments and effects today.Novation usually pushes script/firmware fixes within a few weeks of widespread reports, so keep Components open — when the update drops it’ll say “Improved Cubase plugin focus” or similar.If you want, drop your exact firmware version (shown on Launchkey boot or in Components) and I can confirm if you’re on the latest (as of Nov 2025 it’s v1.2 or higher with no Cubase FX fix yet). Hang in there — once they patch it, it’ll be perfect!

1 Like
15

Wow! @john_robison you have been busy. Thank you so much for this valuable information and I hope a lot of Cubase/Launchkey users get to read it. A few conclusions:

  1. The Launchkey-Cubase integration is annoyingly buggy. I’ve used Akai APC 64 and Novation Launchkey Mk3/4 with Ableton and I have to say the integration is perfect. This needs to be fixed if @steinberg/@cubase wants to open up the platform to new users because the Launchkey Mk4 is a big step forward as a MIDI controller;
  2. Disappointed, but glad I’m not incompetent, ‘cos others have this problem too! I’ve deleted all LK Mk3 scripts and all LK Mk4 scripts other than the LK Mk4 49 which I’m using. I’ve reinstalled the drivers and restored factory settings on the LK Mk4 49….NOPE, same problem, no action on the Plugin encoders if used first. I still need to use the Transport encoders, which seems to free up the focus issue;
  3. I’d suggest planting some helpful comments in both @domsigalas and @chrisselim (@mixdownonline ) Cubase YouTube videos on the LK Mk4. I really respect their work and have learned a lot from both of them but a balanced view on what need fixing would help.

@john_robison many thanks for your excellent help and let’s hope that the developers come to the party with some well targeted bug spray! Cheers Rob (in the Blue Mountains out the back of Sydney).