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!
2 Likes
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.
1 Like
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.
2 Likes
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.
1 Like
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.
1 Like
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?
1 Like
(post deleted by author)
1 Like
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…
2 Likes
Our team is looking into this. Unfortunately, we can’t give you a release date for the fix yet.
3 Likes
Thanks, Matthias,
and sorry for hijacking the other thread.