Cubase 15.0.30: MIDI Shows in the Transport Bar but Never Reaches Instrument Tracks
The short version
On Cubase 15.0.30, MIDI from a controller can register in the transport bar while no MIDI at all reaches instrument tracks. The inputs, ports and routing all look correct, because they are correct.
Resetting Cubase’s preferences fixed it in both cases I saw. On Windows that means quitting Cubase and moving the folder at C:\Users\<you>\AppData\Roaming\Steinberg\Cubase 15_64 somewhere else, then relaunching.
Reinstalling MIDI drivers, changing USB hubs and reseating cables will not fix it. Before you reset anything, read what a reset costs you.
Does this match what you’re seeing?
- The MIDI activity indicator in the Cubase transport bar responds when you play.
- No MIDI reaches an armed instrument track. Nothing sounds, and a test recording captures nothing.
- Note data and CC data are both affected.
- In Studio Setup > MIDI Port Setup, the controller is listed and its “In ‘All MIDI Inputs’” boxes are ticked.
- The controller works in other applications, and Windows sees it.
- You are running Cubase 15.0.30.
If that’s the picture, your routing is not the problem and there is no setting to find. I looked.
What this isn’t
The transport bar indicator is the key piece of information. It tells you MIDI has already travelled from the controller, through the cable, through the USB port, through the Windows driver and into Cubase. Everything upstream of the application is working. The signal is being lost after that.
That rules out the whole category of fixes people are usually pointed at. My first client arrived having already reinstalled his Windows MIDI drivers, reconnected his equipment and swapped USB hubs, on advice from web searches and from ChatGPT. None of it worked, and none of it could have, because none of it was where the fault was. He booked an hour with me instead.
I started by reproducing the fault myself and confirming his input routing was correct, so that he knew he hadn’t caused it. Then I went looking for a setting that would explain it, and didn’t find one.
The fix: reset Cubase’s preferences
When the settings are right and the behaviour is wrong, the preferences are the next place to look. Cubase stores window positions, device configuration, key commands and a great deal else in a folder of its own, and a problem in there produces behaviour with no visible cause in the interface.
Read this before you do it
A reset leaves your projects, audio files and installed plugins completely alone. What it does reset is your custom key commands, MIDI Remote and Generic Remote mappings, workspaces, track and channel presets, and Control Room setup.
I asked both of my clients about these before touching anything, and both told me they used none of them, which is why I was comfortable going to factory state inside a one-hour session. If you have years of key commands built up, your answer will be different. Move the folder rather than deleting it and you can put it back.
If you’d rather test the theory before committing, Cubase has a Safe Start Mode: hold Ctrl-Shift-Alt as you launch and choose “Disable program preferences”. That starts Cubase on factory defaults for one session only and restores your own settings next time. It’s the reversible way to find out whether preferences are the cause. I move the folder by hand because it’s what I’ve always done and it leaves me the old preferences as a file I can inspect, but Safe Start Mode is the gentler first step.
- 1Quit Cubase
Check that it isn’t still running in the background. - 2Open the preferences location
In File Explorer’s address bar, type%appdata%\Steinbergand press Enter. - 3Move the
Cubase 15_64folder out
Drag it to your desktop, or anywhere outside the Steinberg folder. Moving rather than deleting means you can restore it in seconds if this turns out not to be the cause. - 4Move out any older Cubase folders too
If you seeCubase 14_64or similar alongside it, take that out as well. On a fresh start Cubase pulls settings forward from previous versions it finds, so leaving them in place means you don’t get factory defaults, you get your old version’s preferences. That defeats the point of the exercise. My first client had Cubase 14 preferences present, and I moved both out deliberately. Inherited preferences from an older version cause their own compatibility problems, which I’ve written about elsewhere on this site. - 5Relaunch Cubase
It will take longer than usual while it builds a new preferences set. Reselect your audio device, then play your controller into an armed instrument track. In both of my cases, MIDI was flowing again at this point.
Two clients, same morning
I saw this twice in back-to-back sessions on the morning of 28 September 2026, with two unconnected clients. That’s what made me write it up.
The first client had no obvious trigger at all. The system had been working, then it wasn’t. He had Cubase 14 preferences present alongside 15, and I moved both out so the rebuild started genuinely clean.
The second client had moved his HALion and Groove Agent content to a custom location, and that location was throwing Windows errors — he had disk corruption, which was why he was attempting a reinstall and why he contacted me. The MIDI fault appeared around the same time. The preferences reset fixed his MIDI too, but the underlying disk problem is a separate and more serious matter, and fixing the symptom in Cubase does not fix that.
That second case is worth being careful about. Failing storage is a plausible way for a preference file to end up unreadable, which means his instance may have an ordinary explanation rather than a Cubase one. So I’d treat this as one genuinely unexplained case and one case with a possible independent cause, not as two clean data points.
What I don’t know yet
I can’t tell you the cause. I didn’t diagnose a specific corrupted setting and then fix it. I ruled out everything visible, tried the standard reset, and it worked. Twice. That’s a reliable fix and an unexplained fault, and I’d rather say so than invent a mechanism.
Open questions: whether it is specific to 15.0.30 or affects other builds; whether HALion or Groove Agent content operations are involved at all, or whether that was a coincidence in one case; and whether it comes back after a reset over time. I’ll update this page as I see more of it.
If you’ve hit the same thing, I’d like to hear about it — particularly your exact Cubase build, your controller and interface, and what you were doing immediately beforehand. Two cases is an observation. More would be a pattern.
If Cubase is behaving in a way that doesn’t match its own settings, I can take a look with you over a remote session.
