Hi,
Yes, this has been reported to Steinberg already.
Unfortunately, on my side, I still can’t replicate it.
4 Likes
Thank you, Martin.
I re-assigned my midi remote functions (and backed it up immediately). Works fine (and script file is not reset) when opening files that have previously already been saved in C15, with or without midicontroller being connected.
However I managed to replicate the resetting/disappearing of the assignments again, and most likely the trigger was the opening of a C14 project in C15?
1 Like
Interesting, but more so annoying 
. So being a Nuendo user, things are slightly different maybe . . But we lowly Nuendo users are still on 14, actually 14.04 . . so I have been opening 14 in 14 . . . The whole saving/duplicating the mappings is acting wonky . . how’s that for a technical term?
I only use Cubase 14, not the 15 version.
The same error occurs here too.
The problem is that “Export Script” does not save the mappings.
I’ve managed to prevent disaster by backing up the “global mappings file” that Realist told me about, but I think the inability to back up mappings with “Export Script” is a big problem.
Windows 11
Cubase 15 pro
Native Instruments Kontrol S61 MK3
2 Likes
Hi, since this was a very recent experience of yours, could you please post or pm me with the midiRemote file you’ve exported? I’d like to check whether the mappings were indeed missing. From what I understand generally, the problem with missing mappings, shouldn’t occur because of a faulty midiRemote file, but rather from a persisting global mappings file which was faulty written earlier.
same here, everytime i try to export the the mapping, after one day when the mapping is deleted from my cubase. and i try to import the file. the mapping is not appearing
note i save the file on google docs.
1 Like
Yesterday, I encountered a new phenomenon in Cubase 14.
I created a new, empty project.
Afterwards, my Oxygen Pro was no longer recognised as a ‘Midi Remote’. The script I had created was still there, but I couldn’t activate it or assign it to the Oxygen.
I then exported the script as a midiremote file. I deleted my script from Cubase, re-imported the midiremote file and assigned it to my Oxygen connections.
Then I copied my old globalmappings file back into the folder and everything was fine.
I have no idea how to solve this problem because I’m not a programmer. I looked at the json files using an editor and found something about my Oxy Pro in them. However, I can’t properly evaluate this information. If necessary, I could prepare a ZIP file with my files. Perhaps an expert could take a look at it?
I’m no expert but I can have a look.
1 Like
MR Forum.zip (3.0 MB)
Thanks, m.c.
Here is a ZIP file with various backups and screenshots. I hope you can use it. For now, I’m only concerned with the Oxy Pro, not the nanoKey Studio, to keep things simple.
In the ‘Last Backup’ folder, I deleted the Local folder so as not to exceed the forum’s 4MB upload limit.
The json files you’ve backed up work as expected.
The midiRemote file you have does not include all assignments though. Do you recall when you exported this file and with Cubase version?
1 Like
Thanks in advance, m.c.
I created the midiremote file yesterday when my Oxy was no longer recognised. But I had already exported the script at that point. The assignments were missing there too.
I have now exported the script again. Are the assignments included in it?
Windows Editor and Wordpad only show me strange characters. 
Cubase Version is the last 14 update.
MR Forum Save with assign.zip (6.9 KB)
This midiRemote works as expected, no problems here.
Sure, this file is a mixture of compressed elements, care not about it
1 Like
Thank you very much for your help, m.c.
Your posts reassure me somewhat.
I had these problems when switching from 13 to 14 and now with the new update of Cubase 14. I will keep a backup of the midiremote file and try this file if problems arise again.
I would then delete the old script file in Cubase and re-import the backup midiremote file. Would that be the right approach?
1 Like
Yes but please don’t forget to also delete the corresponding json in the user settings folder. This is partly responsible for the issue.
2 Likes
Thank you very much.
I have now made my final assignments and exported the script.
That should be fine, right?
MR MAudio Final.zip (13.4 KB)
I think you’re right in assuming that it has something to do with whether the controller is on or off when Cubase starts up.
I left my Oxygen Pro out and started Cubase. I loaded a project and then closed it completely.
I turned on my Oxygen, started Cubase and loaded a project. The problems were back. Everything was there, from loss of assignments to non-recognition of the Oxygen or greyed-out duplicates.
The globalmappings file was reset to 1KB. I then replaced the globalmappings file and the assignments were there.
It’s really driving me crazy at this point.
@m.c wrote that the files are probably fine. Even though we both use Oxygen Pro, I assume that something is going wrong in Cubase. Other users are also reporting problems, and my Korg nanoKey Studio is showing the same symptoms.
It has something to do with saving (different) projects and the status of the controllers (on/off).
1 Like
Hello M.C !
Thank you for considering trying it.
Native Instruments_S61.midiremote (8.4 KB)