I’m still having problems with the MIDI Remote. I’m using an M-Audio Oxygen Pro 61 and a Korg nanoKey Studio.
I’ve just noticed that no input or output was found for the Oxygen in the script settings.
Nevertheless, it works. In the Studio settings, the ports are also displayed as Midi Remote, specifically as ‘Oxygen Pro 61’.
Now I’ve realised that the description of the input and output is missing from the M-Audio JSON file. These are present in the Korg nanoKey Studio.
My question is, could someone add this entry for me? I can’t do it myself because I don’t know where it goes.
The files are in the ZIP.
Forum2-4-26.zip (202.3 KB)
Hi,
From the screenshot, I can see that nanoKey Studio is already in use as a MIDI Remote Device at your system.
1 Like
Yes, and an M-Audio Oxygen Pro.
I’ve been in touch with German support for a few weeks now because I’m having issues with duplicates and old projects. It’s a well-known issue here that the MIDI Remote isn’t always recognised, assignments are missing, or it simply creates duplicates.
The workarounds so far have been to back up the MIDI Remote folders from a working setup so you can restore them if needed.
Steinberg has already made improvements in this regard, but today I found what I believe to be another bug, and it has exactly to do with these port assignments.
I tried various tips from support, such as enabling WinRT, but that didn’t work.
Yesterday I also reset the user settings, uninstalled Cubase 12 and 13, and deleted the user folders.
This morning, Cubase 15 crashed on launch, which I haven’t experienced for a long time.
I then had a duplicate of the Korg nanoKey again. After restarting earlier, everything seemed back to normal, but then the duplicates started up again. I’ve now realised that Cubase deletes the port assignments in the script when you delete the greyed-out controller.
So now I’m also missing the port assignment in the Korg’s JSON file, which is where the screenshot comes from.
This probably leads to the problems mentioned above for others as well.
I could restore a backup now, which would of course restore the Korg’s port assignments, but I’ve now used the workaround of opening the projects, deleting the duplicate and then saving. Then I closed Cubase, including the Hub, and my test projects were back to normal without the duplicate. Of course, this only works until you open another project from the past that might contain a duplicate.
I have to say that support has always replied to me so far. So thumbs up.However, I also think the developers need to step in here to fix this, especially since tips have already been given in the forum suggesting that you simply delete the duplicates.
Here are some screenshots of the Korg, before and after.
Before:
After:
You can also see in the script settings that there are no longer any port assignments.
Yesterday:
Today:
It’s also a bit odd that I’ve been having problems with the Korg nanoKey today. The port assignments were still there up until a certain point.
I hope this can be sorted out somehow, as both devices are currently missing their port assignments.
