Hi m.c
I just buy a keylab MKii 61 keyboard but when creating my midi remote in the lower zone it is not saved. That means everytime I open the project again I have to create it one more time.
With the MKii 49 it works fine.
Any idea ?
So, just to be clear, you now have two Keylabs (a 49 and a 61) connected simultaneously, and you want both to act as a remote, right?
While I’m expecting that saved remotes will be properly recognised in an upcoming version of CB14, in this particular case that you have, we may solve it earlier. Can you please post a screenshot of your Studio→Studio Setup→MIDI Port Setup? I want to have a look at the exact names of the ports of the two keyboards.
I want to use only the keylab 61. But when I creating my midi remote in the lower zone it is not saved. That means everytime I open the project again I have to create it one more time. When I use the keylab 49 it is saved.
So, you don’t have Keylab 49 connected at all, when you connect your 61?
Only the keylab 61 is connected.
Then it should work properly. You can post the midi ports screenshot as suggested so I can try to help.
Ok I see if I can do that tomorrow. Thanks in advance.
OK, I guess it’s the sysex identity query is causing the issue, since the Keylab 61 has a different identity response from the 49.
Here’s what you can do for now:
Using a text editor, open the file Arturia_Keylab_MK2_MC_Custom.js , which is located in the scripts folder, and close Cubase.
Press the find button in the text editor (perhaps the shortcut Ctrl+F will do it too) and search for this line:
.expectSysexIdentityResponse('00206B', '0200', '0562')
Just before the dot (.) place two slashes (//) and save the file. This line should now look like this:
//.expectSysexIdentityResponse('00206B', '0200', '0562')
Open Cubase, and let’s see if this helps.
Ok, now it works. Thank you.
But now i have it 3 times in midi remote see screenshot. Is it a problem ?
This is an issue presented some times in later versions of Cubase. It’s not causing a problem, but I (too) get annoyed by it. What happens if you go to the two of these three remotes in the UI, and click on “Disable Controller Script”? Do they return again upon a Cubase restart?
Ah, that’s fine then, don’t worry. Most probably it’s because of saved (cached) versions of the script in your projects. I think/hope in an upcoming Cubase update such issues will be solved.
In the mean time, you can try another thing:
- Close Cubase
- Navigate to ~your Documents Folder/Steinberg/Cubase/MIDI Remote/User Settings
- You’ll find a file there named similar (or identical) to this:
Arturia_Keylab_MK2_MC_Custom_0375F85DC35F291BA629076CFD9A185D_globalmappings.json - Delete this file.
- Restart Cubase.
There is no difference. Is something change with this last action ?
When we delete this file, we delete custom assignments to our script and its previous ports. Never mind, as mentioned, it’s an issue with the MIDI Remote itself, hopefully it will be addressed. It will still work as expected.
Ok. Thank you very much for your time.
1 Like
Greetings m.c.
Let me join the topic starting to thank you for this amazing effort and also for offering it to the Cubase community.
And second, congratulations!
Your script is the best out there for the Keylab series at the moment, IMHO.
I mean it.
Let me tell you I installed your script in fulimplementation, to work with a Keylab 61 MkII in Cubase 14.0.20.
I followed your installation instructions carefully (a very well documented file BTW, thanks also for taking time for releasing this), and everything seems to work as expected, but I’m experiencing some disturbing issues that maybe you can help me to resolve.
To begin with, when I load a project, even if I start.a new one, I have to create the control surface for the script, I does not load automatically. No idea of why.
Secondly, I have to press twice the “Mixer” pad in order to access that page going from another one (Insert, for instance), and once I do so, pressing twice, whenever the track Im in, it automatically changes to the last track in my project, ignoring the track I was in.
Is it intended to act like this, changing the track youa re working with to the last track of your project, everytime you switch to Mixer page?
I suppose it’s not, because when I’m in the Mixer page, while performing for some minutes, the MIDI track in Cubase jumps to another track unexpectedly.
I get the feeling is something related to my configuration but I checked the ports and everything seems correct following your document installation.
(Mackie Control and Generic Device ports assigned, loop midi installed, unselected tick boxes on midi port assignments, etc).
I even restored my Keylab to default setings to see if I can solve the issue, with no luck
Have you got any suggestions I can check to see what is going on?
None of this issues happend to occour when I try to use your scritpt in stripped down version.
Thanks in advance and regards.
1 Like
I don’t know if this will be helpful, perhaps MC will chime in.
Somewhere in this monster thread I had similar issues with Cubase 12 and 13. I also use custom port names.
MC put up a variant in a response to me that is numbered:
var currentVersion=“1.12.28.0”
When I got 14 I grabbed the latest version that is in the OP of this thread for a ‘clean start’ and had the same problems you describe.
I rolled it back to 1.12.28.0 and deleted the mkII 61 User Settings file so Cubase would make a fresh one (luckily I had backed up the remote folder ‘just in case’). This fixed the issue, as no matter what I tried with the OP version I kept having to redo the mkII to get it working, or in some cases I’d end up with several copies of the script running.
It’s been working well since rolling back…
I’m not sure if I have the *.midiremote installer file anymore. I see a few in my download folder but I have no way of opening them to see what’s in there or I’d repost it here.
If one scrolls back through all these posts it’s likely to still be here on the forum.
I’m mainly making this post in case it might help M.C. track down what, if anything was done differently in that 1.12.28.0 version of the script.
Here’s a zip of the directory as it appears in my “%Documents%/Steinberg/Cubase/MIDI Remote/Driver Scripts/Local/Arturia” directory.
Keylab_MK2_MC_Custom.1.12.28.0.zip (925.3 KB)
2 Likes
Welcome to this forum, and than you for your kind words!
This is a well known issue with the MIDI Remote generally, there are threads on this, and I think it will be fixed in the near future.
However, I’ve created a version of the script which can get us out of this issue, by letting the user define properly the MIDI ports used.
This script is pretty similar to the one uploaded by @Brian_Roland a post back, thank you very much Brian as always!
Here it is:
Arturia_KeyLab MK2 MC Custom.midiremote (922.9 KB)
And here’s what you have to do:
- Install this version of the script
- Open the folder of the script, navigate to the folder MyPersonalSettings and then open the file customMIDIPorts.js
- In the corresponding fields, place your own MIDI Port names exactly as they appear in the Cubase→Studio Setup→MIDI Port Setup
- Save the file to the root folder, i.e. NOT inside the MyPersonalSettings folder but a level up, and reload the script.
This shouldn’t happen. The Mixer page loads with a single press of Pad 1 (top-left). If we press it again, it will toggle the Mixer window visibility.
This is correlated to an issue of the MIDI Remote API: Whenever we change page (for example from Inserts to Mixer as you’ve correctly noticed) the selected mixer bank zone resets to the very first one of our project. I expect this to be fixed in the near future. However, since I found it, I inserted a workaround in my script which most of the time handles properly this problem. BUT, unfortunately this is not always the case, especially in CB 14. I’m sorry about that but we have to wait. As a side note, I handled this issue properly in a later script for the Novation SL MK3, where I’ve abandoned “Pages” and built up everything using “SubPages”. But I never had the time to re-code my script for the Keylab. IF in the upcoming versions of Cubase, this issue persists, I will seriously consider doing so.
1 Like
Greetings Brian.
Thanks so much for your reply.
Glad to know you have encountered this behavior as well and furthermore, thanks for providing the script version thank worked for you.
I directly imported the content of your zip file to the Midi Remote Location and I had to to test it.
For the records, it seems to work in my setup, and the erratic track jumps seems not present.
I will test it more for a couple of day and I will report if the sucees is complete.
If so, I will export this version of the script as a idiremote file in order to upload it here so everyone can access it, and also for our hist m.c in case he wants to work on it in future updates. (Thanks again for this fantastic development mate!)
Thank you once more for providing it Brian.
I will keep reporting.