I’ve been using Cubase since the dawn of time, and this has always been a problem. I got a new cable and a different USB port, but nothing connected. The usual solution is to delete the user preference file in the C:\Users\Owner\AppData\Roaming\Steinberg\Cubase 13_64.
I’ve recently started using the remote API with Cubase 13.0.41 and the remote device keeps disconnecting, it shows up as disconnected in the remote device manager and I have to restart Cubase in order to reconnect it.
The device is not connected to a real controller but to virtual MIDI ports (loopMIDI), which should be always available. I also have an MCU device and a Generic Remote connected via the same virtual MIDI driver (different ports) and they work fine all the times, so the issue must be specific of the new remote API.
Is it possible to disable midi port detection and only use manual assignment like in the legacy devices?
I’m having this exact problem with both x touch and xtender. Was there ever a fix?
I’ve just noticed that it seems to work slightly better by disabling the “DirectMusic” option in the midi ports setup page, using the ports in Windows MIDI mode instead.
In this mode the remote API will stay connected when I plug/unplug a generic USB device like a flash drive, but the issue is still happening when I connect/disconnect a USB MIDI device.
gleiche Problem AKAI MPK261, Cubase verliert MIDI-Remote- Zuweisung
Is there any information from Steinberg when this major bug will be fixed?
I’ve just bought the StreamDeck Pro profile from SideshowFX, and it seemed to be almost unusuable. I’m on Nuendo 13, but the problem seems to be the same. Fortunately it helps to have a midi track, which has StreamDeck2Daw as its input…
Yeah midi remotes disconnect all the time here too. No rhyme or reason. Used to this kind of thing but will become increasingly problematic as more control surfaces make use of it.
It might seem basic, but in some cases, this can help: double-check that Windows isn’t putting your devices to sleep. Go to Device Manager, find your MIDI device, and make sure that “Allow the computer to turn off this device to save power” is unchecked. This setting can sometimes cause devices to stop functioning properly without fully disconnecting.
That is a great advice in general. I think this is an issue with Cubase 13 however. Cubase 12 does not display these symptoms.
Are you on win10 @mlib?
I am.
I see. The reason I asked is because the setting that @ClarkParker earlier suggested to be unchecked (and I suggested this also in other threads) got defaulted (as checked) in win11.
Just to be clear on this, I never experienced disconnections by having this setting off, and I think that the workaround proposed by @exoslime earlier (adding a track assigned to the port of a remote) is actually all about Cubase waking up the MIDI device at the “low” level, while the MIDI Remote on its own is not allowed to do so (I mean except from querying the ports obviously). This, however, is just an assumption of mine. Anyway, with 0.40-0.41 (cb13) I think that there were attempts to deal with this “wake up” handle. Not sure if it was enough. You see, except from the “obvious” Windows setting, we can always see “disconnected” midi remotes, not because of the OS side, but simply because we may have duplicates of our remotes, using ports that don’t even exist anymore (this again leads to either the OS or to a really disconnected controller), or even remotes sharing ports. This is unfortunately possible if we have a remote disabled, creating a new one with the same ports, and then deciding to re-enable the previous one as well. It is really complicated. That being said, this issue has been reported since early 2022, so, I suppose it was affecting cb12 users too back then.
As a side note, I often saw my devices here (be it a qwerty or a mouse) disconnecting for some secs or even permanently until I physically disconnected/reconnected them. The solution was pretty much the same. To add to the confusion (at least my confusion), when removing a device, it used to affect other already connected ones. Devices totally outside Cubase. Something that I had seen ages ago in my setups. Oh well, just my 2c on this subject, nowhere near to be sure of what’s really going on under the hood 
1 Like
Still no Cubase 13 update since June 4th.
This serious error has not been fixed by Steinberg and there is no information as to why.
Can someone from Steinberg tell us what’s going on with this?
Will there even be an update for Cubase 13 or not?
1 Like
In the meantime I have the impression that the motivation of the script programmers, who kindly publish their hard work here for free, has decreased because of this errors.
The fact is, that the first person to complain about an error like this is the creator of the script. So he works hard and for free, spends a lot of time looking for the error and then it turns out that it’s not his fault. And why should he post his work here at all if he then has to communicate errors for which he is not responsible? No professional programmer likes it when his script doesn’t run perfectly, even if it’s not his fault.
So please, Steinberg, give us a new update of Cubase (this Wednesday) and we will be very grateful. 
2 Likes
I’ve tested the new Cubase update 13.0.50 and the issue is still present. I wonder if Cubase 14 will be any different.
Hi,
This suppose to be fixed in Cubase 14.
I can confirm, this still is happening in Cubase 14. 
I’ve tried using the “reset” on the midi ports, reset scripts/reload the midi remotes. I can clearly see midi activity on the midi devices when using them, but nothing works. I also can see midi activity outside of cubase registered from LoopMidi, so I know info is being sent to the midi ports, and Cubase activity visual LED is registering that something is being pressed, but the remote device does nothing.
I have to restart Cubase, which is the only temporarily fix until it magically disconnects/stops working again, then rinse and repeat. 
I feel if we could get more debug logging when this happens we can narrow it down. Perhaps, through the remote midi device API? We can log where it’s stalling or not registering. I’m just trying to think as this problem has been here for a bit, and if we can help with more info on our side then a solution could be found.
Cheers!
Hi,
I hope everyone is doing well! I noticed that the release notes for Cubase 14.0.10 didn’t mention anything about fixing this issue, but I just wanted to flag that it’s still present in the latest update.
Cheers,
DMDComposer
2 Likes