Having trouble getting your MIDI keyboard to work with Cubase 14? This case study details how Audio Support resolved an issue where a Launchkey Mini MK3 wasn’t sending MIDI input to Cubase. The solution involved activating the ‘All MIDI Inputs’ setting for the device in Cubase’s MIDI Port Setup
A Remote Support Case Study by Paul Andrews of Audio Support.
Audio Support is a small company that connects with clients with music technology experts to resolve issues with their studio setups. As part of a recent remote support session, Paul Andrews helped a client work out why his MIDI keyboard wasn’t working in Cubase 14.
The Client’s Problem: MIDI Input Not Detected in Cubase 14
My client was using a Launchkey Mini MK3 MIDI controller keyboard. When he pressed the keys, we couldn’t see anything displayed in Cubase’s MIDI Input monitor.

Initial Troubleshooting Steps
Checking Physical Connections and Keyboard Power
Starting with some basic troubleshooting steps, I asked my client to check the cable and what he could see on the keyboard. He told me that the lights were illuminated on the keyboard. This told us that the cable was correctly connected and that USB power was coming from the PC.

Restarting Cubase and Reconnecting the Keyboard
I asked my client to go through the following steps:
- Close Cubase
- Disconnect the USB cable from the Launchkey
- Wait a few seconds
- Reconnect the cable
- Re-open Cubase
No difference. MIDI still not being displayed.
The Solution: Activating ‘All MIDI Inputs’ in Cubase’s MIDI Port Setup
Navigating to Studio Setup > MIDI Port Setup
I asked my client to open Settings – Studio Setup – MIDI Port Setup.
Identifying the MIDI Keyboard (Launchkey Mini MK3)

Ensuring the ‘All MIDI Inputs’ Box is Checked and Saving the Settings
We had found the problem. The Launchkey was not active because the All MIDI Inputs box was unchecked for that MIDI device. I told my client to check the box and save the settings.
We went back to Cubase’s main window and tested the keyboard again. This time the VST instrument started playing back notes when keys were pressed. Problem solved.
Key Takeaways:
- This case highlights the importance of checking DAW-specific MIDI input settings when troubleshooting connectivity issues.
- A client’s Novation Launchkey Mini MK3 MIDI keyboard was not sending any MIDI input to Cubase 14.
- Basic checks of cables and keyboard power confirmed the hardware was functioning correctly.
- The issue was located within Cubase’s MIDI settings.
- The solution involved navigating to Studio Setup > MIDI Port Setup and ensuring the ‘All MIDI Inputs’ box was checked for the Launchkey Mini MK3.
If you have any similar problems with Cubase and would like to book remote support from a music technology expert, please make a booking or get in touch.
Recent Reviews
Let’s Get Your System Running Smoothly.
No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.
I usually reply to enquiries within a few hours during UK weekday daytime.
Once you make an enquiry, I’ll read it personally and reply with initial advice or a link to book a remote session if needed.
For booked sessions, you’ll receive a secure AnyDesk link and we’ll talk via WhatsApp or voice chat. Sessions last up to an hour — long enough to diagnose the cause and apply a practical fix.
Make an Enquiry
I’ll reply personally as soon as I can — usually within a few hours during UK daytime.
Book Your Session Securely Online
You can book your Audio Support session instantly using the secure form below.
Choose a time that suits you — I’ll confirm by email and send remote-access details before your appointment.

Outside the UK? Use the Timezone icon to book in your local time.
- 💳 Session fee: £90 per hour (UK Pound Sterling)
- ⏱️ Availability: Usually within 1–2 days.
- 🗓️ Duration: Each session lasts one hour.
- 🔁 Rescheduling: Sessions can be moved up to 24 hours in advance.
- 🔒 Security: Remote access is one-time only and closes automatically when the session ends.
- 🌍 Timezone: Default times shown are UK (GMT/BST). Use the timezone Icon to set to your local time
You don’t have to keep guessing what’s wrong — I’ll help you find the cause and fix it, so you can get back to making music.
More Case Studies
Recent problems solved for real clients.
Logic Pro Slow Loading on M2 Ultra: The £10 Cable That Fixed It
28 October 2025
Client’s Question
Why has Logic Pro slowed down to a crawl?
Session Result
Incompatible cable identified. Replacement ordered.
Read Full Case Study Report: Logic Pro Slow Loading on M2 Ultra: The £10 Cable That Fixed It
Client’s Question
Why does Logic Pro keep crashing when I try and load a project?
Session Result
Project settings updated. Upgrade recommendations made.
Read Full Case Study Report: Logic Pro 10.7.7 Crashing – Fixing Plug-in Conflicts on macOS MontereyFixing Cubase Plug-in Loading Errors After Migration to an M2 Mac running OSX Tahoe 26
20 October 2025
Client’s Question
Why does Cubase keep crashing when I load a project?
Session Result
Incompatible plug-ins removed. Cubase loading.
Read Full Case Study Report: Fixing Cubase Plug-in Loading Errors After Migration to an M2 Mac running OSX Tahoe 26
Client’s Question
Why does Logic Pro stop recording in the middle of my vocal takes?
Session Result
Faulty cable identifed. Replacement ordered.
Read Full Case Study Report: Solving Logic Pro Dropouts for a Singer Using Scarlett Solo and Rode NT1-A