Maybe the audio device ran into a nasty loop sending midi credentials, and just too busy to respond with audio, just a guess…
And this why my suggestion was a side note 
1 Like
today it worked fine again, so i´m a happy camper (at least for now 
)
1 Like
“But it was a pretty enticing prospect” - some guy who always forgets to turn his keyboard on
1 Like
Turned into a second nature for me to always power on my controller(s) before opening Cubase. I always had issues when not doing it.
2 Likes
unfortunately, i needed to disable WinRT again and switch back to normal midi, some strange things happend with WinRT indeed
for example, i was already working in cubase for 3 hours, then took a coffee break, after the 15min coffee break when i returned to my desk and wanted to continue the remote controls did not work anymore (no screensaver, no energy saving at all, no sleep mode at all, computer is not even connected to the internet permanetely)
or another one, i did freeze 2 VSTi, which took aprox 2minutes, once it was finished, none of my remote controls did work anymore 
in both cases, in the midi remote control settings, all my controllers were showing as connected.
but normal Midi functions, like playing and recording from a midi keyboard, still worked at even this stage, just the midi remote control feature was screwed.
so yes, returning to normal midi and in case i want to add a new midi controller to my setup, i will restart cubase again.
i have pretty limited space on my desk, so i its not possible for me to have all my devices permanetly located on my desk and plugged in, some i take from a shelf, put it on the desk, play a couple of bits, and then put it back into the shelf again until i need it again in a few days or weeks. so having to restart cubase to be able do this is a bit of a workflow killer, and using Win RT and Remote Control is acting weird randomly also doesnt help.
@Steinberg Team, please fix this!!
Since I end up turning on MIDI stuff after launching Cubase all the time I played around with this a bit. You don’t need to restart Cubase to reconnect the MIDI, the problem seems to occur at the Project not Program level. So loading a different Project will fix it too.
The least intrusive way I’ve found to resolve the issue is to:
- File>Save the Project, followed by
- File>Revert
I haven’t tried making this into a Macro, but suspect timing issues might arise.
2 Likes
not on my end unfortunately, i tried reopen the project several times and also tried opening different projects, just tried it again like a few minutes ago after reading your post. but still negative 
remote control aint working
The only way on my machine currently is, to close Cubase entirely and reopen the application.,
cheers
Odd that the symptoms differ. I’m on Windows 11.
I’m suspicious this might be more Windows’ fault. I have a nanoKontrol that I don’t use with Cubase at it. It’s used to directly control my RME interface. And it also looses the connection every so often, although I haven’t narrowed down the cause.
From what I understand, but I maybe wrong obviously, you’re talking for a slightly different issue from what @exoslime has. He’s talking about losing functionality while the midi remote shows as being connected. From some testing I’ve done here, some times though the midi is correctly received by Cubase (i.e. showing at the monitors) it’s the midi remote that somehow doesn’t react. But then again, I’m not sure if it’s something to blame on it, since for example on a Mac I never experience this, it’s happening here only on Win 10/11 and only for testing purposes, i.e. to see what other users face.
I have experienced this exact thing as well
(Win10, Cubase Pro 12.0.70)
1 Like
More like wondering if these might actually have a common root cause
Sure, especially if both issues appear just on Win.
When I want to connect and disconnect MIDI devices frequently while running Cubase, I sometimes revert to going old school 5 pin DIN connections with those devices.
That’s not always possible and not ideal by any means, but generally ok for my use cases on my Win10 setup.
In my experience Windows MIDI frequently sucks on plug and play and multiple software connections to the same device. But it shines on backwards compatibility with vintage USB devices and MIDI applications.
1 Like
yes, this is a true, i would love the idea of having an 16 I/O Midi Device that can be running all the time, and you just need to connect traditional midi cables.
many modern devices are lacking of those midi ports, all they give you is an USB-C port and thats it, which on the other hand is neat because its just one single cable, you will have midi in/out and power supply via USB.
exactly, the midi remot control devices are still showing as connected but midi remote control functionality stopped working
regular midi work, like playing VSTi is still working like a charm, even if you use the same controllers that also setup as a remote control as well.
so in a general sense, the devices are still working, these still show up as connected, cubase is still receiving and sending midi data on a regular midi channel in your project , just remote control is unable to do so, remote control is sending out midi data to the controller, i see it on the LEDs on the controller, like transport bar (stop, play, loop, encoder values) is perfectly syncing, BUT not accepting incoming midi signal from the controller after its screwed, like when i´m pushing my buttons or rotating the encoder
typing the above just made me thinking and i just might found a workaround.
in the past, i have set my midi devices that i use as midi remote control devices to hide in the studio midi settings, so that they are not listed as my midi track in and ouputs to keep this section neat and tidy.
so i changed the visibility to on, on all of them
then i have created some new midi tracks in the project, for each of my remote control devices one dedicated midi track, and i routed the inputs of the midi track accordingly to each of the device.
(once this is setup, you can hide these midi tracks or move them somewhere in your project where they dont distract you)
and then i started testing by adding and removing midi devices like a crazy:
and then the unbelievable happend: the remote control seems to keep the connection alive 
please also try this on your system and share if you have similar results!
3 Likes
I can confirm that this works here. Next stop, Template Editing!
How did you even think of trying this?
2 Likes
i´m so happy to read it works for you too,
haha, same here, next steps for me is editing all my templates!!
well, i thought of this because i´m using some shared controllers, with shared i mean, devices that i use as remote controls but also as instrument inputs to play virtual instrument (like my NI Maschine Mikro MK3, i use the pads for playing, but using the softbuttons and glide as remote control for plugin parameters and cubase transport section), and those “shared” controllers usually always have a dedicated midi track in my projects, somehow during testing i noticed that those controllers were not affected by the remote control wreck. but i didnt think of it thoroughly through back then, i thought thats more random behaviour.
just when i wrote above post it suddenly came to my mind, that perhaps because my remote controller midi devices are hidden in the settings, that may cause the issue, so i unhide them, but that wasnt it, but also that during test why a shared controller still worked and a non shared controller that only was connect via midi remote did not. so thought, ok, lets pretend such a non-shared controller would be also setup like an midi instrument controller, so i did setup the first midi track and routed the input accordingly and bam… it worked
2 Likes
In the today’s update, 13.0.40, we have some news!
2 Likes
Excellent news !
fantastic news!