I’m having this problem with 13. I set up a controller, closed Cubase and turned off the computer. When I opened up the same project later it was gone.
That’s a pretty bad bug. Or am I missing something?
I have the same problem. The MIDI Controller dissapears after reloading Cubase or script from MIDI Remote Manager. Problem appeared (as for the other users) after upgrade to 13.0.50. 14.0.10 have the same problem unfortunately.
Steinberg, at least don’t break the things that are working with your upgrades. It is embarassing. What kind of quality testing are you guys doing there?
Same problem here. My X-Touch is saved between start-ups, but my SSL UF1 isn’t.
Judging by the date of this thread it’s been this way for too long - it should have been fixed by now.
Now I accidentally discovered that if I press any key on my controller keyboard while Cubase is starting up, the previously saved MIDI Remote initializes correctly. Hope this information can help…
Wow!!!
Way back in C12 I gave up on MIDI Remote (had to build my own map for a Roland Juno DS-88) , because it would always just stop working after a while. I may revisit with this trick, though I’ve since rearranged my set up so my keyboard is no longer facing my computer monitor.
Thanks, @Guilherme_B !
Doesnt work for me… this issue is really disappointing…
I have a Novation Launchkey 49 MK 3. It seems cubase has destroyed the original default settings and wont let you make new ones. The best i can get working is the keybed and drum pads.
Midi remote has been nothing but a fail for me. Faders jumping all over the place, with the issues well documented including a procedure to duplicate the issue with Steinberg for near on 2 years - Nothing done to fix it.
Yup. Hope your work on the Masters thesis has gone well. We sure do need you on this Midi Remote API implementation stuff. Your work on it has been essential as limageurpublic said earlier in this posting.
Still not fixed in 14.0.20.
Uhh that’s very disappointing. Although I’m on Nuendo 13 the DAW aspects are identical with Cubase 13.
I tested this morning and my icon v1-m mixer settings and script were saved perfectly with Nuendo 12 (i.e. Cubase 12) but not withNuendo 13 latest version.
So when Nuendo 14.2 is released on 19/03/25 it will still have this saving state problem for midi remote control surfaces. Strange to allow a bug like this to get under the wire for 2 maintenance point iterations
2 points? This bug was introduced in a late 13. Last working cubase is 13.0.41. And I think we can be quite sure that Nuendo 14 will be bug compatible with Cubase 14. So the bug have been there since 2024-10-21 and have been reported in more than one thread.
Hi, Nuendo 14.0.20 bld. 240 still has this bug. Shame on Steinberg
Are steinberg developers kidding us not to solve that issue ? how do they want us to upgrade to cubase/nuendo 14 if we are obliged to use cubase 13 for a friendly user behavior of that DAW ?!
I have not looked into forum since a year and i see nothing has changed. The midi remote is still the fraud ripoff to the customers, since the release of it. Nothing happened to the midi remote editor in 3 years… yeah NOTHING, but announced that Generic Remote and MCU will be considered “legacy”… yeah yeah nice… NOT
Minor adds to the API thats it, for those hobby scripters. Still reading only about issues with that crap that it is. Fancy buttons and faders does not make it a “cool” thing or success. In a nutshell: The generic remote has quirks, but it can do the job most of the time. What can you do with the midi remote editor? A fraction of GR and thats it. For what it does, i must seriously ask here, who needs this crap? I must say for what the editor offers, if you can not do this otherwise, you probably should not sit in front of a DAW or simply just forget about it.
Hm I still have this problem in June 2026? I’m on latest Cubase.