Hello, I want to share a strange behaviour. Maybe you find it interesting.
Recently I upgraded to Cubase Pro 15, the 15.0.21
Very nice, nothing to complain. But I noticed my midi controller wasn’t copied from my Cubase Pro 14 version automatically. After opening the CB 14 version once, closing and opening CB 15 again…there it was 
Today update to 15.0.21 same experience. No midicontroller…closing CB 15, opening CB 14, closing and opening CB 15 …Yep, there it was
Shouldn’t it immediately show when updating / upgrading?
Regards,
Ruud
Hi,
Are you on Windows or Mac?
Are you talking about MIDI Remote device or a plain MIDI device?
Hi, I am on Windows 11 latest updates and using Arturia keylab 61 mkII
Hi,
Do you use Arturia keylab 61 mkII as a MIDI Remote device, or as a plain MIDI Controller?
Hi,
I Think I use it as both.
But I think there is still a little problem.
When opening Cb Pro 15 today to make some screenshots for replying your question, I looked in Studio tab on the hub.
There was no Midi Remote available.
Then opening a project, knowing i used Midi remote device or midi controller (not shure about the difference) yesterday, still not showing.
Opening same project in CBpro 14 gives double controllers…
removed 1
Saved and opening CBpro15 gives No midi controller surface in the hub studio tab.
But the project now gives the controller
After closing the project, the hub studio tab now also shows the midi remote
AFter closing CB15 en opening again…the midi remote is gone…
So my ‘‘trick’’ seems to work for a little while during a non broken session. But after closing CB, same trick is needed.
Maybe a little bug or some settings i made not correctly?
Regards,
Ruud
It’s a bug that support either doesn’t want to acknowledge or has simply accepted.
In Cubase 14, there were massive issues with duplicates. Cubase also deleted assignments from MIDI Remote scripts.
This has largely been resolved in the newer versions of Cubase 15.
However, one issue has not been fixed or understood.
Projects created in Cubase 14 that contain this bug have a negative impact on projects created in Cubase 15.
If you delete the greyed-out controller, the MIDI ports in the script file are deleted.
What Steinberg could do:
Integrate a function that deletes the greyed-out controller ‘gently’ and without side effects.
Leave only one controller of the same brand and lock the MIDI ports for that controller.
There must not be one active and one inactive controller using the same MIDI port. That is illogical in itself.
As I’ve already mentioned, Steinberg Support doesn’t understand this bug and I’ve now given up.
There are countless threads here about these bugs, but no one at Steinberg seems to be making the effort to look into them properly.
I’ve explained everything to Support in great detail, including projects and script files, but I haven’t been offered a solution.
Hello @Martin.Jirsak is this something already mentioned at support?
I have disabled my ‘midi remote script’ and use the midi learn cc function within the plugins. when using this I actually see the knob rotating in the GUI, but not when I use midi remote script and use automation.
I think I have to dig in way further to completly understand this functionality’s.
Hi,
This is a known issue.
Once you set MIDI Remote in Cubase 15.0.21, there shouldn’t be a problem anymore.
Hi, should I build from scratch or import script?
Hi,
If you have a backup of the script, I would remove all instances in Cubase, and the just import it (once).
Thanks!
I have a question. when i made the script, my ‘Arturia’ was on User 3 and midi channel 10.
I now think this affects the way the midi controller works. Hitting the drumpads does show on the controller surface, but when switching to for example user 2, with Midi channel 1, the knobs are still affected by midi controller, but the drumpads don’t.
So is there a rule of thumb for witch midi channel you should use when creating a new surface, or is this in some way directed by the mapping page?
You must always use the same mode. When you assign the faders, buttons, drum pads, etc., they transmit the MIDI channel, CCs and other MIDI values. These must all match; otherwise, problems will arise.
So stay in one mode when using your device as a MIDI remote.
Thank You @Realist I Think I messed up in the earlie days of midi remote. This makes sense to the behaviour. I went to a midi channel 10 setup for assigning drumpads to…drums in the groove agent and started from that ‘user’ to configure the surface.
As from yesterday I noticed 2 selection buttons on keylab wich expand faders and knobs to an extra set, meaning different midi cc.
OMG, still a lot to learn 
Regards,
Ruud
