I am having severe problems with MIDI in Cubase 15 PC. Automation has not worked properly for over a week. I get sporadic partial functionality, which then dissappears. Bizzarely, there are number odd problems which come and go, but CC automation is 95% broken. If I can get this alone working the situation would be tolerable. My Nord Keyboard works flawlessly.
Even though my generic faders (let’s call them Arduino Leonardo faders or “ALs”) were set up properly (IMO), (and worked before) no data was reaching the tracks - except on a few inexplicable occasions.
I rolled back to WIN 11 24H2. I reinstalled Cubase, I bought a second set of faders called AMC3 Touch which are class complaint. These arrived today but also do not work. Theyare seen in studio set up and I can see action on the hardware, but on action in the tracks. I have tried several options
When I first loaded up Cubase today, Cubase gave no error messages and both fader sets could be seen in Studio Setup, and Cubase was not showing missing ports. Still no action on the tracks (With RW on). So I decided to restart Cubase and it notified me of “Missing Ports”. Now my original RL faders do not show and both sets give no action on the tracks.
I have had other unrelated missing ports - a channel in my surround sound set up went missing, but is now re-engaged and working.
Please if anyone can help I am desperate! I shall also post on the Discord thread.
You are on Windows, right? This issue has been reported on other forums and the solution seems to be to roll back the latest Widows update. Apparently, you are not alone. It’s not a Cubase issue.
No, there’s much more going on with ZeroZero’s setup. I thought maybe it was the Leonardo driver, but here we see it wasn’t. I’ve lost track of all the various threads in various forums, so not sure what is working vs what isn’t right now. But it’s not just the MIDI update, especially as it has been rolled back on this PC.
The remaining big-ish MIDI problems we’re aware of are with inMusic drivers, and virtual ports (the latter has a preview fix available on our discord server; it will go into Windows updates at the end of April).
@ZeroZero The first thing to do when a MIDI device is seen but not working in Cubase is to try it in something simple like PocketMIDI, or if you had Windows MIDI Services tools installed, midi1monitor or midi endpoint monitor. Look at the output and see if data actually gets through to that. Then verify you have the right channels etc. set up in Cubase to receive the data.
BTW, the thread title is confusing. You had rolled back to a previous version of Windows.
Hi Pete,
I had a day without crashes. I am writing expression maps. I think my system has settled down.
I had so many issues over 3 weeks and I did not work out what waas going on, so apols for too many posts. I was confused.
Here is my diagnosis. Win 11 with MIDI 2 caused crashes here. Crashes then caused preferences issues and maybe more. First I rolled back, and reinstalled Cubase only, things were better but far from good. Only after trashing preferences also, did things improve. As for the Arduino faders, I could first see them, in Studio Set up, and have them working, then after a restart, they would dissappear, then, come back after a power down.
They had to go.
Replacing them was also required. So, it was multifactorial issues and the strangest period I have had since buying the software back in 1993.
I shall cautiously wait for Cubase updates, before updating windows 11 to 26H, but I can work now. Thank you for your help, fullish breakdown is on Discord.
I was having a lot of MIDI problems after the latest windows 11 update a few weeks ago. I tried lots of things but nothing worked. Then I found a temporary fix on an Iconnectivity facebook forum where they also referred to windows update MIDI issues:
Open an administrative console. Then execute the commands:
“net stop midisrv”
then
“net start midisrv”
I get an error after the last command, but the service got up just fine and the issues are gone after that. I have to do this a few times per week. Hoping that Microsoft will soon fix this.
