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.