In my case the mappings have disappeared for two times in the course of 1 year. I simply delete the midi remote folder in documents/nuendo/etc and it is restored when launching the program again. But understandably the whole implementation must be checked.
1 Like
My control surface mappings disappeared yet again.
I think it may have been because I had previously opened a Cubase project in another studio where my control surface was not connected. This has now happened a few times in similar circumstances.
However, I successfully restored the mappings using a method Realist outlined in an earlier posting.
Below I include the notes I wrote to myself, detailing exactly how I did a successful restoration. I keep these for my own sanity, but thought they may be worth sharing in case they help anyone else.
This is written for windows os, I guess any file locations on a mac will be different.
Requirements:
-
The Midi Remote (hardware) must be connected and the assignments to be mapped must exist.
-
You must have a backup available of the correctly working Midi Remote script, which you have exported previously.
TIP: To export (save) a backup of a Midi Remote script:
-
Make sure the script is working before you export it!
-
Start Cubase, open Midi Remote Manager, go the Scripts tab
-
Export the correctly working Midi Remote script (‘Export Script’ button) to a safe location. You will then have a file with the extension .midiremote.
To restore the disappeared Midi Remote mappings:
-
In Cubase, open Midi Remote Manager, go to the Scripts tab
- Select and delete (‘Bin’ button) the relevant non-working MIDI remote script.
-
Go to the Cubase ‘User Settings’ folder. (In Windows - C:\Users\*username*\Documents\Steinberg\Cubase\MIDI Remote\User Settings)
- Delete the relevant non-working remote _globalmappings.jason file for your remote hardware.
-
In Cubase, open Midi Remote Manager, go to the Scripts tab
-
Import (‘Import Script’ button) your previously backed-up midiremote script file from your backup location.
In the Midi Remote window (displayed in the Cubase ‘Lower Zone’) you should now see the Controller Surface, with the restored mapping assignments.
If the mapping assignments are missing, something may have gone wrong during the earlier export/back-up of the midiremote script, or it was not working at the time it was exported. It is therefore important to be sure that the MIDI remote is working properly at the time you do the export.
-
Good luck!
1 Like
Firstly I am following all the backup advice found here and I am able to restore my mapping. However, Cubase is unstable in saving the mapping and I will recount my latest incident for reference to Cubase to investigate.
While working on a project I edited my mapping, tested it and found it to be functioning correctly. I then exported the (functioning) script to my storage folder. I saved the project then closed it, and exited Cubase. I then went to my Midi Remote folder located in Cubase and saved a copy of the (functioning) folder with the new edit.
I then shut down and restarted my M-Audio Pro 49 controller configuring it to my custom preset that only transmits midi cc numbers. After starting the controller, I relaunched Cubase and opened the previous project folder and all was well.
Later on, I worked on the project without using the controller.
This morning I turned on the controller, launched Cubase, opened the project. The surface was there, but the mapping was gone. I went to the manager and imported my saved .midiremote backup file. I got a window asking if I wanted to overwrite which I accepted.
Not only was the mapping still gone, but I now had three additional empty surfaces displayed.
I will go back and restore the saved entire Midi Remote Folder and everything should be back to the way it was when I initially saved the backup.
This is the way it is and I hope the scenario can give the Cubase people some clue as to what is happening.
2 Likes
Restoring the entire MIDI Remote folder is the safest method and always works. 
Support for this (and more) can be found here:
1 Like
Agreed.
The issue, I believe, is that I should not have to keep restoring the MIDI Remote folder to re-open a project where it was working perfectly before.
I have used your advised method and it does work… so far.
The .midiremote script file alone, is not retaining the mapping. So it is, at this time, an ineffective method of backing up.
This is unacceptable for a “professional” software program. May have been solved earlier if the beta program was open to the paid users. It would certainly increase the chances that bugs and dysfunction would be spotted more quickly. Ableton Live, Bitwig, and Cakewalk all have open betas, and I’ve I’ve seen it make a huge difference in their development.
2 Likes
They don’t because it’s assumed most of the solutions for the MIDI Remote are just a matter of some goodwill of programmers and the API, which is barely tested because it’s a Pro-only feature.
Just discovered a quick way to reload the midi remote folder in the Mac (until Cubase fixes this issue) by using the Automater feature. I can select the process of deleting the corrupted folder and replacing it with the good, stored folder by running a workflow file.
I lost my MIDI remote custom script settings right after the .41 update in Nuendo. It’s never happened before.
Thinking out loud: Class action suit: we all walk away with a cool $1 million each. 
1 Like
Someone may have already posted something similar - I had to remap my faderport 8 many times since I figured out how. Not ideal.
1 Like
Same problem Mac Cubase 150. Set up a complicated mapping. Working perfectly. Went back to use it a couple of weeks later. Control surface was there but mapping was no where to be found. What a huge waste of time 
1 Like
Same thing happened to me. I got lucky because I have a backup system on my computer and was able to recover the lost data. tbh, no matter the reason, it is always worth having some kind of backup in place. You never know when something like this will happen, especially when it comes out of nowhere like it did with Cubase. Total time saver in the long run.
3 Likes
I keep getting duplicate sometimes 3 copies of Native instruments Kontrol S series but my main bugbear is that i have been trying ti install stream deck cubase pro Profiles V3.2.2 The latest but it does not work traced this to midi remote not woking wasted days and days over christmas hols but to no avail wish i had tried the cubase forum earlier seams I have wasted hundreds of pounds on a streamdecx xl plus software Plus time thanks Steinberg .
StreamDeck XL works fine with Cubase. You might want to remove it and start from scratch, carefully following the PDF guide. There are also a few posts on here that might help you, if you search for them.
thanks for that , I reinstalled it on my laptop with cubase 15 and it all worked till i rebooted the laptop, I have just read all 155 messages on this topic so thanks to all the people who have contributed I know have some hope that i may find workaround
Is there any update on fixing midi remote, I have now read the forum, all 155 posts ,and it explains a lot of the unreliable midi remote problems ,I have experienced, including multiple instances of NI S 88mk3 it’s just not consistent.if you want me to help diagnose the problem let me know
Brian
Again, completely reproducible:
Load project with Roland FP10 switched off and all MIDI Remotes are in tact.
Switch FP10 on = all MIDI Remotes greyed out.
No. Steinberg still has no solution to all those problems.
Maybe they have it, maybe not, they’re not telling us anything… So all we can do is muddle along and wait for 15.0.10 - it might bring the solution we’re hoping for…