My son came over today he is a programmer but lives 60 miles from me he followed the instructions from the web site for the stream deck and the forum very precisely and got it to work we made a copy of the whole cubase folder 15 rebooted and all is well so far ,so I must have been doing something wrong but not sure what . 
If it’s too complicated for average users, then it’s not mature enough, or stable enough, or both.
Yes I agree if they give us the information required to do proper diagnosis that would be a big help but so get a precise list of do,s is useless if it doesn’t work, but for me it now works and Steinberg doesn’t have to admit any faults 
This issue has been undermining people’s work (and wasting their time) since October. For such a fundamental part of workflow, it is time for Steinberg to give MIDI remote top priority.
6 Likes
Yes totally agree with this.
2 Likes
I was just about to buy Cubase PRO 15 when I read this and it makes me kind of nervous. When I wrote in this thread a warning came up with a message that told me that the Midi Remote problem was solved?
Is this true or do I misread that ppl still have problems with this issue?
I migrate from Cubase 12 PRO because of problems and cannot afford more time to not producing music as it was meant to be.
So please tell me that the message was true and I can buy and install Cubase 15 PRO as soon as possible.
I have cubase 15 running with streamdeck XL , Mackie Master control 8 channels, Kontrol S88 MIII and Berhinger UMC umc 1820 running on windows11 so i can confirm that this can be made to work, but you must be very precice about the steps to set up steamdeck I use the cubase pro profiles and they use Midi remote and control cubase with midi commands , the set up is logical once you have faild multiple timesw and then succed , You must follow the install to the letter comma and dot , this is hoe my son sorted this for me , now my set up seams stable , but only time will tell, it was a lot of work but it was worth it, hope the same is true for you
Brian
Interesting. Where did you see this warning, here in the forum? Who sent it? And what is the warning about, when a problem has been solved?
That message came from the software that is used to run this forum. The topic was marked as “solved” by the OP. Thus whenever somebody posts a reply a little notification is displayed that this topic was marked as “solved” already.
This doesn’t necessarily mean that the discussed issue is gone.
1 Like
“Solved” in this case does NOT mean that the problem has been officially solved.
It only means that Steinberg has acknowledged the problem and is looking for a solution. How far this search has progressed has not been communicated at this time.
Cubase 15 is great, fast, snappy, quite solid. Still my DAW of choice but the remote script issue certainly isn’t solved.
2 Likes
Which year? 2023, 2024?
2 Likes
Yes me too, take a look at how many blank instances there are of the Nektar. If I scroll to the right there are many more. I also have a Novation Launchpad X, and there are about 15 or even 20 blank views in the MIDI remote window for the Novation.
Cubase V15.0.6
1 Like
Yes, the problem persists. At least having my midi remote folder backup works for now, I just replace it everytime the mappings disappear. Unfortunatelly, I still have to remap the knob on the faderport 8 because that one keeps losing it’s mapping everytime it seems.
The year MIDI Remote was introduced as a feature.
Do you restart cubase everytime when u replace folders?
I have like 16 blank mapping thr. Staring at me and saying “ Do Charlie Gonna fix this or not"? 
Yes, I close Cubase, replace the folder and then restart it.
For as long as MIDI Remote is being unreliable and until a solution can be found, I have decided to disable my Cubase Midi Remote controller scripts altogether and revert to using TouchOSC and TouchPortal to manage my workflow.
Is there any news or any way to see if they even work on this? Has anyone spoken with the support? The temporary solution with saving the scripts for the global settings elsewhere and copy them back after the problem comes up is not suitable because you loose all project relatet mappings, too.
Have to say I am really pissed about this. This is a huge issue for my workflow.
No.
The developers probably have other things on their minds than fixing the problem.
Next week, the NAMM Show is starting and everything revolves around WaveLab 13…