As written in the other post, that is a good (and even better) workaround for my workflow. You saved my day!
Unfortunately, the Cubase update 14.0.40 deletes the contents of some MIDI Remote mapping files (*_globalmappings.json) in the directory ā%userprofile%\Documents\Steinberg\Cubase\MIDI Remote\User Settingsā.
Luckily, I had a backup of this directory, allowing me to resolve the issue as follows:
- Close Cubase
- Replace the corrupted ā*_globalmappings.jsonā files in the directory ā%userprofile%\Documents\Steinberg\Cubase\MIDI Remote\User Settingsā with the backup copies.
- Start Cubase.
It would be great if the Cubase team would test the next update more thoroughly. Bugs like this cost customers a lot of time and frustration!
When I updated to 14.0.40 all my MIDI REMOTE scripts stopped working.
Fortunately, I always back up my scripts (they take a long time to build) so I simply pasted my back-up scripts into the remote folder in Documents and everything was sorted out.
Do you have script back-ups?
EDIT - I see a similar answer above.
Moto of this story ā¦. always back-up user created files of every type!
in v15 itās the same thingā¦
Iām noticing the issue doesnāt remain fixed and Iām having to copy the MIDI Remote folder over from my back-up to bring my scripts back.
I guess now 15 is out this will never be fixed for 14.
Hopefully they will fix it for 15 - Iām not going to update to 15 until this issue is resolved.
I had a new Audio PC built over Christmas. The one I had Cubase on started to get issues and it turns out it was the Processor.
Iāve installed 14 Pro on the new PC (AMD Ryzen 9 9900X 12-Core) and itās running very smooth. A lot of my previous issues were no doubt caused by the slowly failing CPU.