My Studiologic SL Mk2 GT doesn‘t work anymore. I have to switch to midi 1.0 mode to make cubase receive midi note input. It worked with Cubase 14. I‘m on Mac, Tahoe. Bug?
This may be the Windows bug that came about in a KB.
Rebooting your PC will fix it if so.
The issue is we have staged MIDI 2.0 bits in KB5066835. That includes the new USB MIDI 2.0 driver. When you plug in a MIDI 2.0 (UMP data format) device for the first time, it loads up the driver, but before Windows can switch it back to the MIDI 1 driver, we grab it and start MIDI 2.0 discovery and protocol negotiation.
Yamaha and Roland have confirmed that a reboot with the device connected fixes the issue and switches it to our older MIDI 1 driver.
Pete
Microsoft
Did you see, that I‘m on Mac?
1 Like
Oh sorry. I did not.
Pete
Microsoft
1 Like
Could anybody confirm?
Nobody with a Midi 2.0 keyboard?
I have a Roland A-88 MK2 which doesn’t work in both Midi 1.0 and 2.0 mode in Cubase 15 (15.0.5 Build 121). Via the midi monitor I do see Note On & Off messages coming in. Both modes do work in Cubase 14.
Running it on MacOS Sequoia 15.7.2 (Intel iMac 27” 2019).
So it‘s confirmed. Will the dev team see this, or do we have to sent a bug report?
Does anybody know?
Always file a bug report.
Pete
Microsoft
1 Like
Where and how? Never did this here…
I had to fish around to find it, but here’s the Steinberg recommended way of reporting a bug.
Don’t forget to tag your thread as an issue.
In order to make the issue subforum better manageable, please follow these easy rules.
- Before posting a new report, please use the search function (to look out for an already existing report)
- If you don’t find a similar thread create a new one (one report per issue)
- Make sure to follow the reporting form below when creating a report
Reporting Form (Feature Requests / Issues)
1. Summary/Title
(Provide a short but descriptive sentence that summaries the issue or feature request)
2. Description
(Provide a detailed description and list the step by step process to reproduce the issue to help the team to understand and reproduce the problem)
3. Expected Results
(Describe what you expected to see)
4. Actual Results
(Describe what you actually saw)
5. Environment
(Count the hardware and software including version numbers being used)
Psyche; I have to ask, when oh when is MIDI 2 going to be real?
Thanks KT! But where do I have to sent it?
It’s real on macOS and Linux today.
It’ll be real on retail Windows in Q1 2026. We were actually targeting end of November, but found a couple bugs related to specific devices that broke backwards compatibility (primarily with DJ controllers/software and device-specific software), so we had to fix those and respin the release.
The MIDI 2.0 stuff has been pretty stable in the builds for a while, but it’s the backwards compatibility that has taken so much more time than expected. We have a 20+ year old API that we need to make sure still works 100% even though the plumbing now goes through a completely different route in the OS. 
Some more detail at the bottom of this post
If any other questions on it, we should probably start a different thread.
Pete
Microsoft
3 Likes
I shall do so. Thanks for some great info.
1 Like
Back to my issue: Tested again and discovered, that it works, when I switch to „Midi 2.0 low resolution“ on my SL 88 GT Mk2. The normal „Midi 2.0“ setting doesn’t work at all. Perhaps this helps.
You can create a new thread here on the forum with an appropriate title and tag it as an issue, then post the information as described above.
If others can confirm based on your description and results, then your bug has a better chance of ending up on the list.
This thread is allready tagged as “issue” an confirmed.
All needed information is within, I think.