Launchkey Mini mk4 – Drum Mode Default behavior inconsistent in Cubase 14 Pro

Cubase
,
1

:receipt: Summary

When using Novation Launchkey Mini mk4 (37 keys) with Cubase 14 Pro and the official Novation Remote Script, the Drum Mode Default (Shift+Drum) does not behave as documented.
Pads fail to trigger MIDI notes unless the track input is manually switched to the secondary port (MIDIIN2), and documentation on this dual-port behavior is missing.

:gear: Environment

  • Hardware: Novation Launchkey Mini mk4 37

  • Firmware: latest (as of October 2025)

  • DAW: Cubase Pro 14 (fresh install, not upgraded)

  • OS: Windows 11 64-bit

  • Integration: Official Novation MIDI Remote Script (auto-installed on detection)

:puzzle_piece: Issue Description

When Launchkey Mini mk4 is used in Drum Mode Default (Shift + Drum), pads do not trigger instruments such as Groove Agent SE or any VST drum plugin.
They appear inactive, even though the LEDs respond and Channel 10 note data should be transmitted.

However, testing shows that:

  • The pads do transmit MIDI Note messages (Channel 10),

  • But only through the secondary MIDI input port — MIDIIN2 (Launchkey Mini MK4 37) — not through the primary port used by the Cubase Remote Script.

:brain: Technical Findings

1. Dual MIDI Ports Behavior

Port Name Function Description
Launchkey Mini MK4 37 MIDI DAW Remote Port Used exclusively by the Cubase Remote Script for mixer, transport, and pad remote control functions. Does not pass MIDI Note data from pads.
MIDIIN2 (Launchkey Mini MK4 37) Instrument Port Carries actual MIDI Note/CC data from keys and pads (Channel 1 and 10). Required for triggering VST instruments.

  • If a track’s MIDI input = Launchkey Mini MK4 37 MIDI → pads do not trigger.

  • If a track’s input = All MIDI Inputs or MIDIIN2 (Launchkey Mini MK4 37) → pads trigger normally (C1–D#2, Ch.10).

This behavior is undocumented and easily mistaken for a malfunction.

2. Contradiction with Official Novation Documentation

Novation’s official user guide states:

“When you select the Drum pad mode, the pads trigger MIDI notes.
By default, the notes are arranged from C1 to D#2 (bottom left to top right) and on MIDI Channel 10.”

In Cubase (with Remote Script active):

  • This statement is partially true but misleading.

  • The pads do send MIDI notes — but not via the same MIDI port that Cubase Remote Script uses.

  • As a result, unless users manually switch the track’s input routing, pads appear “dead”.

3. Behavioral Summary per Mode

Mode Pads Behavior Channel Port Cubase Reaction
DAW Mode DAW Remote (Mute/Solo/Arm) N/A Port 1 (Launchkey Mini MK4 37 MIDI) Works partially (Remote only)
Drum Mode Default Should send Notes 10 :white_check_mark: Only via Port 2 (MIDIIN2) Works if routed manually
Custom Mode (Alt Drums) Sends Notes 10 Both Ports Works perfectly
Generic (No Script) Sends Notes 10 Single Port Works perfectly

:warning: User Impact

  • Default Drum Mode (the one mentioned in the manual) does not work out of the box in Cubase.

  • Users are forced to:

    • Use Custom Mode (Alt Drums), or

    • Route track input to MIDIIN2, or

    • Disable the Remote Script entirely.

  • Confusing for new users, since manual implies Drum Mode = ready-to-use for instruments.

:compass: Expected Behavior

  1. Pads in Drum Mode Default should send MIDI Note messages to the same port Cubase uses for instrument input (or both ports simultaneously).

  2. If two ports must remain, the documentation should explicitly state which one carries MIDI Note data.

  3. Ideally, users should be able to toggle pad behavior between:

    • DAW Remote Mode (Mute/Solo/Arm)

    • Instrument Mode (MIDI Note, Ch.10)

:hammer_and_wrench: Suggested Fixes

Option 1 (Preferred):

  • Merge pad Note output into the main port (Launchkey Mini MK4 37 MIDI), so Drum Mode works natively in Cubase.

Option 2:

  • Add a firmware/config toggle for pad output routing:

    • “Pad Output: DAW Remote / MIDI Channel 10 / Both”.

Option 3:

  • Update documentation (Novation + Steinberg) to clarify:

    • Dual-port behavior.

    • Which port to select in Cubase to access Drum Mode Note data.

:receipt: Additional Notes

  • This behavior was confirmed via testing MIDI monitor:

    • In Drum Mode Default, Channel 10 notes appear only on MIDIIN2.

  • Disabling Cubase’s Remote Script reverts Launchkey behavior to match the official documentation (pads send C1–D#2 on Ch.10 as expected).

:open_mailbox_with_raised_flag: Summary Request

Please review and align Launchkey Mini mk4’s Cubase integration with its official documentation.
Either by:

  • Adjusting the Cubase Remote Script routing,

  • Or by adding firmware-level configuration to let users define how Drum Mode communicates MIDI Note data.

2

If I understand the issue you’re describing correctly, I believe this is normal, expected functionality, but it might be worth raising a ticket with the Novation Support Team so that we can look into this with you.

John // Novation UK :united_kingdom:

3

Thank you for the reply. I already raise a ticket to the Novation Support too. Still on the same topic, the Track Select button also doesn’t function as an Octave Shifter or note group change while in Drum Mode Default, but in Alt. Drum Mode (shift+custom2 pad) it works as expected . So the drum note outside the range of note C1 ~ D#2, can be accessible. Is there any Novation Forum like this to keep in touch with other Novation user?

4

Glad to hear you’ve raised a ticket! A team member should be following up with you shortly, if they haven’t already, to assist you with this. Unfortunately, we don’t have a dedicated forum at the moment. We did have one about 10 years ago, but it was rarely used. Most people prefer to reach out via social media, so we decided to focus our efforts there instead.

If you ever need assistance, in addition to email, you can also contact us through phone, live chat, or on social platforms like X/Twitter, Facebook, and Instagram.