I also had problem with midi remote when experimenting WinRT, went back to previous setting, deleted all my Midi Remote inside Nuendo. And also after closing Nuendo deleted my .json in my :
C:\Users\yourname\Documents\Steinberg\Nuendo\MIDI Remote\User Settings
And deleted sub folder in :
C:\Users\yourname\Documents\Steinberg\Nuendo\MIDI Remote\Driver Scripts\Local
Then in Nuendo created new remote and imported my saved script file, it looks like it solve the problem…
I eventually got rid of the duplicated inactive midi remote controllers by hiding the .JSON Files in a subfolder, then recreated the controllers in one of my projects.
For every project opened, the duplicate controllers persisted, so next I deleted each inactive controller then immediately saved the project. After closing then reopening the project, only the active controllers are displayed.
I had to open every project to rinse and repeat the delete then save method. Now all old and new projects show only active controllers under the midi remote tab.
The old .JSON files will remain hidden in the SU folders. I will delete them only after I completely understand how the midi remote script file system works. It’ s still a mystery to me ATM.
I updated Nuendo to the latest version, and also updated the firmware of the Icon controllers. Now when I startup Nuendo en open a project (an existing one or a new one from template), I have to manually add the controller because it is missing. Even if I saved the project with the controller added.
In short: Nuendo forgets the midi remote as soon as I quit Nuendo.
How can I make it so that the controller is always there, regardless of what project I open? Is there a way to “clean” the controller setup in Nuendo and set it up so that the controller is always present at startup?
EDIT: I tested with other midi remote scripts (Akai). And that also disappears. So it seems that Nuendo doesn’t remember any midi remote setup when the program is quit.
Not sure if it can help, but for Windows users the midi used by the remote have to be un-check (not visible) in the Nuendo/Cubase midi port setup.
It’s a question of time (few more months before the big change) because actually Windows don’t support midi multi-client access.
At the moment only one midi port per soft is supported.
So if you are on Windows maybe when you re-start Nuendo the port are reserved primary and exclusively to Nuendo and not anymore for your midi remote… This can bring to different problems…
If need more soft per one midi port, pass threw loopMIDI
I don’t know what to do anymore.
Another instance appears randomly on my M-Audio Oxygen Pro.
In one project it is OK and in another project a second instance appears.
Then the first project is also faulty.
After a restart, everything seems to be OK, but then another instance appears randomly.
A file with the name ‘blockeddevice’ is also created. But there is nothing in it except ‘’
I have attached the Midi Remote folder with the files. I have had a look myself, but can’t do anything with it.
It would be great if someone could help me, because all the tips mentioned here have not worked for me.
https://www.dropbox.com/scl/fo/k6hx7kbzi0yg8ee4tlrtp/AJdujYvICLnhypsGdJLl-jk?rlkey=xr85ijtu0hoxbbdl9of8fk7mz&st=qjup1dap&dl=0
Same issue as all others above “Ghost” instances of midi remotes from being previously connected to another USB port. CONFIRMED. Cubase 14. Latest
Lots of half methods in this thread and can’t tell if there is a real solution.
Anyway, the issue still persists here on Cubase 13 and 14.
Midi Remote still has a lot of kinks to work out.
Agreed. It would help if someone could provide an example using a very simple project ( eg. just one track and just one controller) that replicates the problem every time, then the steps to solve it for that one project.
Trouble is, we’re all busy making music and the problem doesn’t appear until we have multiple tracks and controllers, making for multiple variables.
I’m confident that this issue is down to the controller having been previously connected to a different USB port, rather than any bugs in the Remote midi API itself, most of which seem to have been solved in 14.0.20.
For my part, I’ve ‘solved’ the issue by just buying additional USB cards and never changing the wiring once a controller is plugged in, but that only works with a desktop PC with spare card slots. Also, I only use Cubase so I don’t have the added complication of swapping between Cubase and Nuendo.
Maybe this is the solution. It would be nice if someone cleverer than me could post how to solve for the simple project described above using LoopMidi
Iam not 100% sure that all i going to say is correct but it’s working find for me so i will share my thought and what i have done.
I think it’s a conflict in Windows when sharing the same midi port between multiple software that cause those problems, so we have to be sure that every software have is own midi port.
In my Midi Remote iam using Stream Deck.
_ _
in LoopMIDI I create :
StreamDeck2Daw
Daw2StreamDeck
(you have to create 2 port, one for input & one for output, for no feedbackloop)
_ _
In Cubendo studio setup, i only activate “Use System Timelamp for Windows midi inputs”, i had midi remote problem (double, not connected) when Direct Music was selected.
I havent check yet the latency differences between Windows MIDI and DirectMusic, if they have…When i play keyboards…
So the result is that i only have Windows MIDI.
_ _
And then we have to unselect the loopMIDI port that have been created in loopMIDI before.
Here the
Daw2StreamDeck
StreamDeck2Daw
_ _
Then in Midi Remote Manager create your control, here is mine for StreamDeck (you can see that my loopMIDI port are connected inside)
_ _
In my Stream Deck, all is connected to loopMIDI :
_ _
So i hope it will work you, but anyway soon Windows will officially bring the Midi Multiclient Access to Windows 10 and 11, so it means no more conflict between multiple software using the same midi port, at the end better midi connection without headache configurations. I have been waiting this for years… 
FYI: I am also seeing this “ghost” disabled extra for my Novation SL MK3 script. This script was used in previous version of Cubase. Removing and reinstalling the script appears to always remove BOTH surfaces.
I haven’t played with this much, however the “ghost” surface (showing disconnected) shows a different set of connections that I probably errantly used previously for the standard MIDI port, as opposed to the correct one.
Interestingly, the surface created for my StreamDeck experimentation is only showing up once. This script was recently created and is (so far) not duplicated.
FYI: I was able to resolve this issue by reestablishing the connections that was expected by the “disconnected” surface/controller. I was then able to remove that occurrence.
At one point I had the SL connected both via the USB MIDI and through DIN MIDI via a MIDI timepiece, also connected via its USB MIDI.
So, it seems that the issue was indeed that I had created a second instance but with the connections for that instance unavailable, it was not offering the option to remove that device.
Now I’ll have to see if the issue is resolved or reappears.
