Hi, I see these assignments:
Isn’t this correct? Perhaps you had more at some point?
Thank you m.c.
That’s exactly my data.
Hmmmm.
If there is nothing wrong with the midiremote file then I don’t understand why sometimes only the mapping.
Yes, but apparently it messes up my midiremote when I load a project in Cubase and my Oxygen isn’t on.
After that, all projects related to the created midiremote are defective when I start Cubase with the Oxygen turned on. It has something to do with saving projects and the Oxygen status (on/off).
Replacing the globalmappings file seems to fix the error for the time being.
The question is, why does Cubase reset my global mappings for the Oxygen when it is not turned on?
Why is the global mappings file always used when saving, even if no changes have been made?
You can see that from the timestamps on the files. It all seems very fragile to me. All it takes is for something in Cubase not to run smoothly and Cubase destroys the global mappings file when saving. On the other hand, my last Cubase crash was last year. 
I’m probably too much of a layman to understand the whole thing, even though I thought I was technically savvy. So far, I’ve always been able to solve my problems with Cubase myself, but I’ve probably reached my limit here. 
I just deleted the “Native Instruments_S61_95364A487A93DC7649A3C92F4F53FB1A_globalmappings” file in the “User Settings folder” and tried “Import Script,” and the script with the mappings was loaded without any problems!!!
Thank you m.c! anyway!
Yes, it has to do with project saving.
When we save a project, an instance of the MIDI Remote surface is saved inside the project. This is my understanding so far.
Now, the thing is that when something goes wrong, 99% of the time (I think) it is when the MIDI Ports are not there, and this may happen not only when we have our controller disconnected as you do, but also when for example in Windows, the port names change. MR tries to save the surface. BUT, which are its mappings? Note that we can have two or more identical controllers, and Cubase needs a way to distinguish them. From what I understand, the way it does this is by inspecting their MIDI Port names. So, what may happen when these MIDI Port names are no longer there? This is not a trivial exercise, especially when whichever solution comes out, has to be careful with older remotes setup. This is something that I happen to know that Steinberg is working on. Not sure what the result will be, just wanted to point out that it’s not an overlooked issue.
I have discovered it doesn’t matter whether or not the M-Audio controller was on or off. It still loses the mapping. And yes it seems like Cubase is overwriting the file each time or at a random time… I don’t know which. As I mentioned in my post I reloaded saved working files into the default path that Cubase uses and I got the same result of lost mapping. I wish they would fix it so I can get on with production.
totally weird behavior , same happens to me, just with artruia mkII
I sent in my issue to Cubase support and am awaiting a response. Hopefully it will notify them of the problem. I hope also that others will report it to them as well so we can get this fixed.
If I have understood Martin and m.c. correctly, Steinberg is aware of the problem. We can only hope that they find a solution.
However, I fear that there will be no solution for Cubase 14.
I actually wanted to skip version 15 because I’m not really convinced by the upgrade.
That behavior to create problems (and somehow delete the mappings file) when the controller is not attached when Cubase is started really needs to be fixed. I’m using a laptop and also want to work outside the studio. But when I’m back I, want everything to work as expected. (Similar problems are with the audio devices where ins and outs gets messed up when they change - specially with external instruments).
As for now I have several setting folders and files with I need to restore from a backup everytime I used Cubase outside the studio. This is super annoying.
It should be just possible to just save a state of Cubase with ALL SETTINGS for different environments. Is that so difficult?
Hello Matthias,
apologies for addressing you directly in this thread.
I have just read through the release notes for Cubase 14.
For update 14.0.40, it says:
‘MIDI Remote now saves and recalls previously configured devices as expected.’
Unfortunately, this is not the case for some users of Cubase 14 and Cubase 15.
See, for example, here:
Unfortunately, the latest release notes do not mention this issue either.
I just wanted to ask if anything is being done about this?
Many thanks and best regards from Germany.
Have the midi remote issues of 14.0.40 and 15.0.5 been resolved in these updates?
No.
There again, these 15.0.6 and 14.0.41 releases are labelled as ‘hotfix’ updates, with just the fixes/improvements listed at their release notes included. Suggests to me there is still a proper maintenance update to come/being worked on… Hopefully one that’s released before festive period/holidays, kicks-in proper…
Our team is looking into this. Unfortunately, we can’t give you a release date for the fix yet.
Thanks, Matthias,
and sorry for hijacking the other thread.
I have four controllers: Akai LPD8, Akai APCmini [or Nektar panorama P1–either or] and Novation Launchpad X.
Cubase v15 sees all the controllers, but buttons are no longer programmed. Native controllers are still there. I.e. in the Akai APC, the play, record buttons and faders still work, same with the Nektar…. faders and transport work, controllers which came with the device, but not programmable buttons/faders.
Cubase has not lost my MIDI remote settings for the Akai LPD8.
Yesterday I programmed a new MR script for Novation Launchpad X, and this morning, I launched Cubase, again, my settings are gone.… so I tried importing the Launchpad script I saved yesterday in “User Settings”, it did not load.
Adding this info on the offchance that my situation with the Akai LPD8 still working might possibly shed some light on this problem.
Unfortunately no, I updated to 15.0.6 today and I’m still experiencing issues with MIDI Remote. I never had problems with MIDI Remote on 14 – they showed up with the first version of 15. But I want to keep on using 15 anyway, because otherwise I think it’s a wonderful update.
I don’t think MIDI Remote issues from version 12 have been fixed yet, let alone ones from current versions like 14 and 15.
I also started having issues with the MIDI Remote after updating to Cubase 14.0.41. The X-Touch worked fine for me before C 14.0.30 and it works fine on Cubase 13. But since the 2 latest updates on C14 now the X-Touch doesn’t open correctly. It doesn’t update when loading a project and even if a project is closed but Cubase is still open, when another project is loaded, X-Touch again doesn’t update, even though I had gone through the steps listed below to make it update. When project loads the faders and colors appear and then all faders go to the off position and colors disappear. Then I have to go to MIDI Remote under menu STUDIO and click on the rescan icon. 4 instances of the X-Touch are appearing, 3 connected and 1 disconnected. After the rescan only 1 appears connected and the other 3 disconnected. And now the X-Touch is updated, colors, etc, but the faders are still in the off position. I have to use a Mixer Snapshot to return the faders to their last save position. I open the same project in Cubase 13 and this is not happening, it’s working correctly. Windows 11 latest updates, X-Touch connected with USB. Total bummer!!! Pay for updates and get worst functionality???