Hi, Cubase’s Midi Remote connections randomly drops and stops working after “X” amount of time. According to the Midi Remote Manager “Status”, the actual connection/midi port is still available and strangely showing it’s connected. However, no midi messages are being read/sent by Cubase from the visual LED feedback, and well, nothing works. These are not USB ports. I’m using a touchscreen through Open Stage Control. Messages are being sent through the ports according to loopMIDI. Cubase is just not receiving or sending anything, even when still connected. I’ve tried using the reset in Studio > Midi Remote > Reset. As well, just refreshing the Midi Remote Scripts. The only thing that seems to reconnect the midi remotes (even though they are connected according to Midi Remote Manager “Status”), is to simply restart Cubase. Is there a different way I can try to re-establish a connection with Cubase that I haven’t thought of? Or, is just simply restarting Cubase the only way? As well, any other thoughts on what could be causing this hiccup? Cheers, DMDComposer

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 :slight_smile:

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?

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. :heart_eyes:

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. :disappointed_relieved: 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. :melting_face: 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

The last problem was solved… :sunglasses:

Steinberg Forums

Midi Remote Randomly Disconnects

Cubase

midi-remote

CKB December 9, 2024, 10:51pm 60

PreSonus FaderPort 2 (2018) midi remote script Cubase

Nuendo 13.0.51 still not working for me. All projects forget the midi controller each time I open it. I rolled back to 13.0.41 again I will not buy Nuendo 14. I will wait and see. I have no confidence in Steinberg at the moment.

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled