Does anyone know what files I have to restore to get them back?
unless you saved the script you can not get it back it seems. Lots of problems have ocurred lately for me too with midi remote. Such a workflow killer.
did you make the MIDI controller setup yourself or are you using a downloaded script?
In Windows the midi remote is located in the documents/Steinberg/Cubase/midi remote
Yeah its custom…but I have all of it backed up realtime on GDrive…just need to find what I need to recover
The script is still there for hardware but all mapping pages are gone
Cheers
I think the mappings are here on Windows:
%userprofile%\Documents\Steinberg\Cubase\MIDI Remote\User Settings
Thanks @Johnny_Moneto
Hmm no sign of that folder here
The ole where is that piece of info found goose chase again 
I saved mine as custom_midicontroller.midiremote. this midiremote file copy files into these folders but I did never manage to recover a custom creation that got lost from Cubase which I didn’t save. might aswell just redo it and make sure to save it. many people have problems with midiremote these days. It been a know for a while which Steinberg says is fixed now in 14.0.20.. but I still have problems with certain premade scripts which are coded. The ones I map myself inside Cubase is now back to working for me.
Is there any chance that your Documents folder is synced to some cloud and that the cloud overwrites the content of the folder on the hard drive, effectively erasing the files that you created?
yes mine is…but it would be in the trash folder as it keeps it there for 30 days. It also doesnt make sense because the actual remote definition is still there…just all the mappings have disappeared
Can you have a look at the path of the script in the MIDI Remote Manager?
Usually all the scripts (including factory) are installed in Documents. But since te folder is rather empty on your computer I wonder where they are.
I can see the script
This is just the remote surface definitions including the indexes that the mapping pages would link to…the same as most setups eg Ableton etc
So there is now (it would seem) a missing a separate file that manages the linking…?
Have you decided to put all scripts in another folder? Or did Cubase install its own scripts on drive X: ?
What’s the path for one of the Cubase scripts, like the KeyLab Essential 49?
Unless you have told Windows to use X:\User\DAW\Documents as your OS’ documetns folder those files should not be there afaik.
I imagine this is the root cause for the issues.
Old school…keep c only as system/persistent device. Any fluid data on separate drive
Documents and user folders etc are repathed via the OS eg my docs/relocate. Never had this affecting anything previously as thats where the environment variable is pointing to
It is a user script so its in the correct location and the surface looks correct, its now just missing all the mapping pages. The time stamp is still the old correct one ie wasnt overwritten so its seems there is another part to this story
This doesnt seem to work if you have a space in user name…cant remember how to escape it
It works if you paste it in the location bar of Windows Explorer
1 Like
Ok, if you have redirected the path then it should work. Did you re-path the variable %userprofile% or which variable did you work on?
Maybe Cubase uses %userprofile%.
Yeah the OS handles it
This is the path…but its still just the json surface definions
This is where the current version is stored
and it has the affected time stamp on the file
However this has all been working fine since February
These are the mapping files. The ones you were missing.
As far as I understand it:
Explorer:
Documents...\User Settings - mappings
Documents...\Local... - scripts (hardware surface descriptions)
In Cubase:
MIDI Remote Manager / MIDI Controllers - mappings
MIDI Remote Manager / Scripts - scripts
Yep…
But How do I reinstate the mappings to the control surface? That is the key required
Tja, I am not an expert and at the moment I haven’t figured this out.
Your screenshot indicates that there already is a connection to the mappings file, but I might misinterpret the screenshot.
@m.c : Do you know how to connect a script to an existing mappings file?
so I think I figured it out…maybe
JSON = Surface
Midi remote = Mappings
I had backed up some random folders a little while back…I reloaded from that location (xml studio where I do a lot of remote work) and voila!
There is a lot of work on it as I set up a shift that allows you to select the pages from the 4 modes. If only this surface had better quality encoder button press and feel…otherwise perfect
Now I just have to work out how to restore all the port setups/control room…