Hello,
I created a MIDI remote controller, but I did not enter the right model name.
How can I change it ?
Hi @PatriceJ ,
You (unfortunately) have to delete it and then create it newly from scratch using the correct name. The name of the device is a key identification data element for saved user mappings. That’s why we don’t provide a convenient way for renaming.
It’s just as @Jochen_Trappe said (obviously).
Now, technically, you can actually do it, though not conveniently as said.
- Close Cubase
- Create a new folder in your “Lemur” main folder, and name it after the new name you want to give to your controller, say Lemur-a-b-c
- Copy your original json file from your Lemur-5-3-2 folder into this new folder, rename it as Lemur_Lemur-a-b-c
- Open this copy. Search for the DeviceName key. Alter its value to the new name Lemur-a-b-c
- Save and open Cubase
- Add this new controller using the usual method. No assignments will be there. No worries
- Close Cubase
- Open [yourDocumentsFolder]/Steinberg/Cubase/MIDI Remote/User Settings folder
- You’ll see two files, one with its name starting with your previous vendor_name (in your case this should be Lemur_Lemur-5-3-2, and another one with the new name Lemur_Lemur-a-b-c. Both files should have a suffix of _globalmappings.json
- Open the first one using a text editor and copy all of its contents
- Now open the second one (the new one), clear all of its contents, and paste the contents you’ve copied earlier
- In this new content, replace the value for the key DeviceName to the new name
- Save and reopen Cubase
If everything was done properly, you should now see the new controller, with the old assignments, at least this is what happened when I gave it a try.
Not sure however, if doing the above process is actually faster than recreating a remote, especially if no big list of assignments is there
M.C.
A big THANK YOU , it works and it was faster for me as my surface as 40 controls or more.
Hi Jochen,
I have to say that you are one of the most supportive Steinbergians and it is really great that you are here in the forum to communicate with users. Thanks for that. Having said that I cannot spare you from a very fundamental critic: I am repeatedly surprised that absolutely basic fundamentals of computer science are violated again and again. Do “coders” really not understand to stick to an absolutely fundamental rule: Never use natural object names as an identifier that is used for internal references in a system? This is absolutely basic computer science knowledge - did it get lost when coders forgot about databases? ;o).
Seriously… there is no reasonable argument to make a wrong conceptual design decision (chosing the natural name as an identifier that is used as a reference in the system) and then arguing that this wrong choice be a good reason for NOT allowing to change the naturale name of the object.
Sorry for the rant.
It has a history: I am in computer science and large systems development for decades - and this - exactly this definitely wrong design decision has cost companies tremendous amounts of money. Natural names change. This NEVER has to affect system interals. The solution is called “surrogate” and really… this is basic.
Maybe lost knowledge?
Thx, Ernst