Midi Remote jumping and forgets my mapping

[Beyon1]

Hi everyone

I’m fairly new to Cubase and I’m trying since hours to map my controller.
I have a couple issues, that I just can’t figure out on my own.
I have an arturia mkII and i’m using the script from m.c. from this forum as base.
I had a hard time, doing a script from scratch so I’m changing the mapping of the script from m.c. At first it worked perfectly fine, but after a while i run into some issues.

When mapping my functions to my inputs, cubase barely let’s me do that. When selecting my input and the function the map button is flickering on and off and I have to constantly press the input on my controller and the mapping button. It switches/ flickers between greyed out and active.

Cubase forgets some of my midi-buttons mapping. The mapped functions stay with faders and sliders but with the function mapped to buttons get lost after switching my controller on and off.

What bothers me more, is that suddenly cubase started to behave weird. When selecting a track it always jumps to the folder, where the track is in. This only happens, when I have my controller plugged in, so it has something to do with my mapping.

I’m also wondering, if I can map the jog push (i think its called that way, the big knob over the display), to right mouse button. So I can select stuff with it.

I’m a little frustrated, since i thought it would be a lot less time-consuming and easier than it turned out. So I’m glad for any inputs.

[m.c]

Hi, and welcome to this forum!

This script was not designed to be altered using the MIDI Remote Mapping Assistant.
The changes have to be done by editing the mapOfCommands.js file that comes with it.

But before we start tweaking, did you actually get to use first the script as is, before trying to remap things, so that you can first know what is capable of, and then proceed with changes? Apart from the commands, its structure is based on Steinberg’s concept for pages, that is, we have a mixer page, quick controls, strip channel, inserts and sends. I don’t really see why to alter these particular pages.

At the same time, note that you can always create a second midi remote surface by using the USER pages of the Keylab MK2 in which you can add assignments not already provided by the script. This is actually what I do as well, when I have some components to add, for example I did this for the control room.

@Beyon1

Cubase forgets some of my midi-buttons mapping.

PLEASE, don’t map things this way. This script is not a simple one, and if you remap things with the assistant, you’re just breaking the functionalities provided.

@Beyon1

if I can map the jog push (i think its called that way, the big knob over the display), to right mouse button. So I can select stuff with it

No you cannot, midi remote does not provide such functionality. That being said, for each mapping page, you can see the function that the jogPush is already connected with. The function depends on the context of the page.

@Beyon1

When selecting a track it always jumps to the folder, where the track is in

This is happening because of a command inside the script responsible for reassigning mixer zone banks when we change pages. I will provide you with an altered version for not having this issue.

@Beyon1

I had a hard time, doing a script from scratch so I’m changing the mapping of the script from m.c

I wish I had created a more user-friendly script for coders, but as it is currently, it is not the best way to get you started with scripting. It was designed to cover my own workflow and there’s a lot of complexity so it’s just a not good option (to not say horrible) to begin with, when you want to script. It’s a good option as an all-in-one solution replacing the original Arturia’s MCU integration. I would advice you to start with something simpler, such as the SimpleDevice provided by Steinberg and add to that, again, if you feel you need to have your own custom script.

At the same time, if you see things that you think should be improved, or added to the script, you can always post at the wiki thread of the script, I would be happy to read suggestions that could add value for you and other users.

Arturia Keylab MK2 Custom Midi Remote Script ( MKII )

Hi there, I’m happy to share with you my own script for the Arturia Keylab MK2 (I personally own and tested a 49 and a 61-keys, but I have to guess that the script is working for the 88-keys too). For a start, follow the instructions in the attached pdf file (just import the attached script from the relevant Cubase’s window, if already familiar with this) After finishing with import, you should now see inside the newly created folder (apart from the script’s file and additional ones), a file n…

[Beyon1]

Hi!
Wow, thank you for your response.

Blockquote
But before we start tweaking, did you actually get to use first the script as is, before trying to remap things, so that you can first know what is capable of, and then proceed with changes? Apart from the commands, its structure is based on Steinberg’s concept for pages, that is, we have a mixer page, quick controls, strip channel, inserts and sends. I don’t really see why to alter these particular pages.
Blockquote

Yes, I actually tried it, but was a little overwhelmed with all its functionality. So I thought I make a new Page and map it myself, since I wanted to map specific functions, like i had it before in ableton. To be honest, the script is just to complicated for me. I can not understand how it’s set up.
I was not aware, that it was coded. I thought it was just created within cubase.
There are just to many things that I don’t understand. Like buttons which show up as not mapped and then do something anyways. Some light of my controller light up, even they are not mapped.

Now I tried to delete the whole script. But somehow, cubase remembers what i did and I can not install it. Im not sure either how this is possible. I deleted it within cubase and from the folder, it was saved to.

I just wanted to have a simple set up for my controller. But im now som 25+ trying to get it to work, as I was used to, but just do not get there.

I have now mapped my desired functions to subset 3, and it works in a way I can live with.

edit: I thought it’s not jumping tracks anymore, but it jstu started again out of nowhere^^:)

[m.c]

@Beyon1

I just wanted to have a simple set up for my controller

Ah, in this case, I wouldn’t even be using my script.
You can setup the original implementation by Arturia as instructed here:

KeyLab MkII - Tips & Tricks

Then, you can actually use the USER mode of the Keylab, and create a remote control (using port1) and perform your assignments there.

@Beyon1

Like buttons which show up as not mapped and then do something anyways

Interesting. In the UI of the MIDI Remote I almost always show what is assigned to what.
For example here’s the mixer page:

We can see in the first row of five just below the buttons, the “Select” assignment. It’s used for selecting one of the eight tracks of the mixer bank.
The other rows’ assignments are recalled using the Pads one to four (counting from the bottom left) and the select buttons.
And so on, for each page, we have assignments shown in the UI, when of course they exist.

@Beyon1

I thought it’s not jumping tracks anymore, but it jstu started again out of nowhere

Not sure I understand, sorry. Didn’t you delete my script?

[Beyon1]

hi, thanks again for your reply.
Yes, again, i messed things up. I havent noticed that your commands just show up in the large window. In the small window, when hovering over a input, it states “no mapping”.

But I figured out that, it only added my functions and did not overwrite your function.
I don’t use mackie control, because it does not let me assign my desired functions of cubase.

why I’m still trying your script? Well veryone is talking good things about it, so i thought maybe it’s a good way to go
Initially I wanted to create a mapping from scratch like cubase is showing in a video. But when doing this, it does not pick up the signal from each input with midi learn. So I could only assign some knobs but not all of them.

I guess i will try tomorrow again, if I find a solution.

[m.c]

@Beyon1

I haven’t noticed that your commands just show up in the large window. In the small window

Yes, you have to have a proper zoom level to see the assignments.

@Beyon1

i thought maybe it’s a good way to go

Well, it is, as long as you want the same things as others

@Beyon1

But when doing this, it does not pick up the signal from each input with midi learn. So I could only assign some knobs but not all of them.

This is very strange actually, I haven’t experienced something like this.

@Beyon1

I guess i will try tomorrow again

If this is your very first days with the Keylab and Cubase, I would recommend that you give my script another day, without any tweaks at all, so that you can get a better feel of how things work with it. Then, say, you need some assignments changed in some pages. Let me know, and I will help you, no worries

[Beyon1]

Thanks again!

Blockquote
Well, it is, as long as you want the same things as others

That’s actually what i meant to say

Blockquote
This is very strange actually, I haven’t experienced something like this.

Maybe it is a good idea to message the support. Now when trying again with midi-remote it gets all signals, but then does not execute the function, when using the controller.

[Beyon1]

Hi again

Today I tried again and got a little used to your script.
At first it worked quite well, but suddenly the keyboard stopped working. I have no idea why. All I did was plugin an aux into my arturia. Since then it started to behave weird again.
Also I had to deactivate your script and activate it again, because when turning on my controller cubase hasn’t recognized it. Sometimes during use it suddenly stops working and I had to turn it on and off multiple times.
Something must be off here. I thought Arturia’s hardware is fully integrated with cubase.

Do you know what could be the issue here?

[m.c]

@Beyon1

Do you know what could be the issue here?

This is most probably a case described in other topics as well:

MIDI Remote connection lost when powering on new MIDI Device

I have an AKAI MIDIMIX setup as a MIDI Remote (not from a script). It sometimes seems to loose its connection and it took awhile to see the pattern. Here’s what I can reproduce here Start with my Komplete Kontrol S61 powered down Launch a Project in Cubase Verify that my MIDIMIX is functioning as a MIDI Remote Power up the S61 Verify the S61 can play a VSTi Confirm that the MIDIMIX no longer functions as a MIDI Remote

My “solution” is to always power on my midi devices before starting Cubase, and then don’t power off any of them or add a new one. At the same time I have set my usb-hub power saving setting for Window to OFF:

Settings→System→About→Device Manager→Universal Serial Bus Controllers→USB Root Hub→Properties→Power Management→UNCHECK the “Allow the Computer to turn off this device to save power”.