When I start a project, the MIDI Remote Mapping Assistant is set on the “Default” Mapping Page.
But there’s a problem : I can’t update, delete or rename that “Default” Page.
I can only Duplicate it and modify the obtained copy, which I customize with all sorts of applied Mappings and rename for example “Custom-2023-08-28” Page.
Do you know if that precisely “Custom-2023-08-28” page can become my new “Default” page ?
Because I often wonder why some settings don’t work, and most times, it’s that “Default” page failing me.
The Default page cannot be deleted nor renamed from inside Cubase.
But then, why don’t you reassign things the way you want them, to this Default page?
Anyway, there is a way to actually delete it from the outside, and then rename another page to Default, by editing the connected globamappings.json file in the MIDI Remote/User Settings subfolder. But I wouldn’t recommend it if you’re not familiar with json, because things can get nasty and create a crash eventually.
It’s a custom hardware map meant to receive the signal of 1280 pads (16 novation launchpad mini mk2) via BMT Pro and a dedicated virtual BMT MIDI channel.
There are multiple layers of signal feeding into different MIDI channels, but they are not routed to the Remote MIDI Mapping : some are routed to instruments, to the previous system (Generic Remote) or to other softwares.
I also hope you won’t deactivate the Generic Remote system anytime soon (next Cubase versions) because some options it provides are not available yet in the new MIDI Remote Mapping —I don’t remember which ones right now but I wrote that somewhere after trying to reprogram all my Generic Remote ideas into the new system.
Besides the default page issue, this setup is remarkably stable.
At last, I find the backup process of MIDI Remote Mapping a bit uncertain, several files and folders, but maybe I missed something, and I regret not being able to rename the name of a Model/Vendor/Script Creator without json editing kindly suggested above and the associated risks.
Yes, by design, the “core” remote is inside its own folder, while “additions” are to the subfolder I’ve mentioned earlier. This has the obvious disadvantage of having to remember to backup both these files, and the advantage of deleting the “additions” when you want to keep the “core”. This is actually more useful when writing scripts and want to revert users’ additions.
Fortunately, this type of editing can be done without worries, even when we’re completely strangers to json. We have just to be careful a bit, but nothing really dangerous here.
See this screenshot for where to make these changes: