Cubase 14 Midi remote not saved

Cubase
, ,
1

When creating my midi remote in the lower zone Arturia - keylab MK2,
it is not saved. That means everytime I open the project again I have to create it one more time. It worked in Cubase 13

:slight_smile: Henrik

1 Like
2

Are you creating the whole surface every time or is it that the script doesn’t load?
I have been having issues with the midi remote in C14Pro but currently I’m using the Keylab Mk3 and downloaded the script from Arturia and it’s good… so far.

The only thing I can think of is try and get a script from another user, check your controller firmware and see if that helps?

Sorry I’m not much use but even the support team for my other controller couldn’t help me and I gave up.

1 Like
3

Hi,

This is a known and already reported issue. For some users, the newly created MIDI Remote Devices are not stored, unfortunately.

1 Like
4

Hi when is this obvious bug that should have been detected before release likely to be fixed ( or will it be a NEW FEATURE in cubase 15)

5

I’m struggling with this too.

Any update on when the fix is going to be released?

M

6

Midi Remote basically seems abandoned :pensive:

Prove me wrong Steinberg!

2 Likes
7

Same behavior here. This is annoying…

8

Been testing and this started with 13.0.50 works ok in 13 .0.40 but not later supposed updates when they fix this for 14 will they also fix cubase 13 or has that been abandoned now

9

hi guys…I moved to a macbook after 30 plus years on a PC. My midi keyboard arturia keylab61 mk2 will not save in the controller section at all…lost every
time I start Cubase 14 pro…very annoying. I had not issues on PC

10

please share if you find a fix for this…even saving templates doesn’t solve the problem

11

has the update today fixed this?

M

12

for fks sake tried both 13 and 14 patches STILL NOT REMEMBERING NEW SCRIPTS have to recreate each time Last working version I have is 13.0.40
GET A GRIP STEINBERG AND TEST YOUR UPDATES

13

Very annoying, :frowning:

14

Hi,

Yes, Cubase 14.0.10 is supposed to fix this issue. But from the other threads, it seams it’s not the case for all users.

1 Like
15

For me this updated fixed it, but only if the detection unit is scripted correctly

I mean this thing here:
deviceDriver.makeDetectionUnit().detectPortPair(midiInput, midiOutput)
.expectInputNameEquals(‘SimpleDevice (MIDI IN)’)
.expectOutputNameEquals(‘SimpleDevice (MIDI OUT)’)

Previously in 13.40 Cubase would remember the correct Midi Ports that I selected the first time I created the midi remote and I could get away with not scripting the DetectionUnit. Now it only works if the detection unit is scripted so that is searches for the correct midi ports.

So for everyone who still has problems with the Midi Remote not being saved, check if you have a detection unit that is looking for the correctly named ports.

16

Note that most users facing this problem are not into scripting at all, they’re creating their remotes using the mapping assistant. When it comes to scripting, you are correct.

And the issue is acknowledged as stated here:

17

Hi I am using a qcon icon lite and it is not saving
how can i change the port name in the script I know nothing about programming is there some kind of text editor i could use to find and replace port names I need a step by step guide hopefully some guru can help us musicians who cannot program many thanks Mal

18

Could you please open a new thread with your case so that I (and others) can reply accordingly? This is needed because I would like to ask some question and that you can upload some files/screenshots I’ll ask for…

19

That’s not Mac fault. The same problem in windows…

20

Just to be clear, any chance that you’re using my script?

OR you’re talking about a midi remote of yours?

Is the MIDI Remote lost i.e. the file is missing, OR the ports are not automatically recognized? I’m asking because I notice in the forum various posts concerning this issue, and I’m not sure.