I have made my own midi remote “script” for my Arturia controller. That works without any problems. The only unusual thing is that it makes 2 copies in the MIDI remote tray.
I also have a script that I downloaded from the web for my Novation 49 SL MKIII. That apparently is coded as a script, and honestly, it is very deep and advanced, so I would rather not try to recreate it.
The problem with this script is that it disappears every time I start Cubase projects so I must re-connect it. I can notice a difference from an older Cubase version: now the midi control stays in the same state as when I close Cubase. Before the bugs with the Midi remote showed up, my Midi controller would reset to a start position when it was idle which was the same before and after Cubase was running.
I have been searching the forum for answers and it seems many people are experiencing the same problems and offering very few or no solutions.
I picked up someone mentioning that making a midi remote inside Cubase was different from making a coded script. Also, there seemed to be a solution mentioning that the problem is related to what port Cubase expects the midi remote to connect to. And that person suggested that he “just edited” the script.
So I guess I have 1 question: can anyone help me with this? I am going crazy doing this re-connect before starting to work every time.
Currently I’m hyper busy, still, I promise that by the end of the week I will post an updated version where you can easily alter the midi port names because this is most probably the issue you’re facing.
Hi and sorry for the late reply. Today I have some time to work on this.
Could you please post a screenshot of your Studio→Studio Setup→MIDI Port Setup? And please let me know if you’re using the full script option, i.e. using loopback MIDI ports too.
It works fine for me here on my Mac in all Cb13 and 14 versions. And from what I see in your MIDI Setup, a) the port names are the ones queried by my script so it should work just fine, BUT b) I see you have another (?) remote in the other SL MIDI Port? Other than that and not relative, you should really take the InControl port out of the “All MIDI” ports.
that is confusing me on the mac. I must select 2x input ports and 2 output ports to activate the script. I thought that I only needed to do that with the advanced mode? on my pc I only did 1 input and 1 output but same result. I only have the 49 SL mkIII and a Faderport 16 connected
It is only needed in the advanced mode correct.
Please open the file mapOfGeneralSettings.js and check for the value of the variable strippedDownVersion. If it is set to 0, reset it to 1. Reload the script afterwards.
ok very weird. The value was already 1. so I kinda gave up. I deleted (once again) all the files from your script. Downloaded you latest script in the original post that you linked to and imported it. Now it is working. And now I didn´t even have to pick port.. so god knows what is going on I downloaded the same script like 2-3 weeks ago
thanks for chiming in and thank you so much for an excellent script! much appreciated effort. I was thinking I would make my own, but so much better to get into your workflow
I really wish I did know 1 thing: I have added a few key commands on free pads. I would love to have it show a color like when you press F3 for the mixer . is that possible or only via coding?
You’ve added them using the custom pages I have setup (the free assignable)? If so, not it’s not directly possible. However, I can always add for example a pad color settings file for the custom pages, if again, we’re talking about the same thing.
yes I think so on the pads you can press 1 button for the mixer, 1 for the channel and 1 pad for opening the instrument on the active channel. they are down and to the right with a few free pads on the left. I love to have a shortcut for adding tracks and zoom to locators. I can add the zoom to locator’s command, only missing the colored pad to indicate there is a command there like on the others assigned
Wait, what you describe looks like the original colors I have set for the mixer/channel settings etc. When talking about the “left” pads, are you perhaps talking about my “shift/ctrl/alt/fn” pads?
These pads are powerful, since they offer us a way to use the other pads for multiple actions.
If you open the file mapOfBindings.js, you can review and change whichever function you want. At the same time, you can change the color of the corresponding pad (excluding the state buttons mentioned).
Let me give you an example.
If you open this file, you’ll see an assignment to “Shift” (that’s actually Pad 9 counting from the top-left corner of pads) + Pad 1:
You see that I have assigned it to the command Hide Muted which belongs to the Channel and track visibility group of commands. At the same time, you see that I have setup a color for this pad (to red). So, if you want, you can alter this assignment to something more important for your workflow and also change the color of this pad (when we hold the “shift” pad).
