The script is updated to 1.8.20.0.
The internal structure changed a bit, in order to resolve some issues with moving from one active project to another.
1 Like
Ok, mate, that’s very honorable of you. So again, thank you very much. Your work really means something to me. Keep it up and please apologize for me not checking the Cubase version before installing your script. That was a little awkward. Now it works great. See you later! 
1 Like
I don’t have the MKIII but this looks like some incredible work in the scripting that you’ve done @m.c, just from looking at your code !
I really hope we will see more features and developments on the MIDI Remote in Cubendo 13.
I was curious, for your Focus Quick Controls, when changing the focus to some other plugin, does the values on your displays properly update too?
I have my own custom setup, combining a Kenton Killamix Mini and a SoundFlow Surface for display, but for some reason I’m experiencing that the display values don’t update (I think they did in an earlier version of the Nuendo 12). Just curious if you’ve run in to this problem too?
Hello my friend, thank you for your kind words!
Yes, they do update based on the object in focus. There is a small trick here. Apart from the value bindings you really have to set also these, otherwise there are indeed occasions that the displays do not update:
fqcControl.mOnTitleChange
fqcControl.mOnDisplayValueChange
where var fqcControl=page.mHostAccess.mFocusedQuickControls.getByIndex(controlIndex)
It’s not enough to use the mOnTitle and mOnDisplayValueChange of the hardware control.
I have my comments here:
//the mOnTitleChange of knobs in fqc does not seem to be triggered properly, while in this subPage and changing focused plugin
//So, I had to add this
Give it a try and let’s see if it works for you too 
1 Like
Thank you so much. Yeah, looking through your script I did see that you were doing some triggeries with that, so I had a hunch you might be doing something extra.
My script is very different structured, so I’ll have to see if I understand it well enough to make it how you are doing it. Else I might have to try and program it from scratch again, more following your structure
1 Like
Please note that this particular script relied heavily on subpages, and I did it this way for just the fun of it. My other scripts are using mapping pages much more, perhaps you would like to have a look at them to.
just the fun of it.
Love it!
Ah yes, I’ve structured mine more in pages as well, so might make sense to look at those if you also fixed the display updating in those…
1 Like
Yes, the display works as expected there too. You can have a look at the script for the komplete kontrol mk2
1 Like
Wonderful. I’ll do so. Probably only in a week or two, as I’m too busy till then 
1 Like
The script is updated to 1.8.26.0 and this update is about adding functionality to our faders in the sub sections.
In the Instrument’s quick controls sub section, we can now have faders assigned to another set of 8 controls, giving as banks of 16 controls.
Same goes for the Inserts sub section.
In sub sections Focused quick controls, Pregain, Channel Strip, Sends, Instrument’s quick controls and Inserts, we can have our faders duplicating the parameters assigned to knobs (fader 1 will be assigned to the same parameter with knob 1 and so on).
These options are not enabled by default , we have to edit the mapOfGeneralSettings.js file, please read the Novation_SL_MK3_versionChangesLog.pdf file in the first post for which lines to change.
I must confess that I was a bit sceptical concerning this update and this is why I’ve made all these assignments optional.
The way I liked my controller was to have faders strictly controlling mixer volume, while knobs with their nice displays would control pretty much every parameter exposed.
However, earlier today, a very closed friend who also uses the SL MK3 asked me why not making use of the faders in the other sub sections. To her, using faders to control sends, eq and pregain levels, is more convenient and I can understand the point here.
At the same time, adding faders to our instrument quick controls and inserts sub sections, doubles the number of available parameters per bank. This is a plus, especially for more advanced users who teak a lot of stuff (I’m not anywhere near this one).
Finally while controlling parameters, some of them are better suited to faders (many users actually insist on this, and I think they’re right), so I added the option to duplicate the parameters which are assigned to our knobs.
The only thing that I had to add is the representation of these parameters to our displays. It is done, however when we enable this functionality in instrument quick controls and inserts, our displays now won’t show the knob icon, because I needed this space for the faders’ assignments.
Here’s for example how a bank of inserts controls will look when we enable the faders:
In each column we have set the first two rows to our knobs assignments, and the next two rows to our faders’ ones. Note that the first row displays the parameter name, while the second, the parameter value. However, we can “mix” the name and value by altering a line in our settings file and get this:
This one has the advantage that usually more letters of the parameter name are shown and the disadvantage that the output becomes less “clear”, at least for my taste.
And, of course, when we don’t use such options, we have the initial display with knobs:
4 Likes
Thank you so much for creating your script mchantzi.
I am currently on Nuendo 11 (will update to 13 when it is released) and I downloaded the Cubase 12 trial to try your script using my SL Mk3 and it works incredibly well :), I am now able to get a lot more use out of the keyboard than I could previously.
Andrew.
1 Like
Glad you liked it!
Thanks so much for your hard work.
I was wondering if we can use the same script for Cubasis.
Or if there is an easy way to convert it to be able to use with Cubasis on iOS?
Thanks.
Hi, as far as I know Cubasis doesn’t support the new midi remote api, so the answer is no unfortunately.
Again no, because I don’t even know if Cubasis supports such functionalities. I think that the idea behind Cubasis is to write on-the-fly sequences, and use the touch screen for editing, so I don’t think they have integrated complex midi manipulation in this app, but I’m not 100% sure.
OK, thanks for the info.
I might have to get a PC and Cubase :-0
Holy cow this is everything i have ever dreamt of when it comes to sl mk3 integration! Thank you so much
2 Likes
Glad you liked it!
1 Like
Hi M.C, it appears cubase 13 does cannot import your script. It states failed to import script archive. Not sure where i can go to see any additional log errors. I thought these were java script files, but opening it in nopad seems binary. Is there anyway to extract the files and see what changes i can make to give it a test.
Ok replying to myself. It worked the second second time. Not sure what the difference is as i did it the same both times.
1 Like
m.c
I must commend the deep integration you have created between the SL MKIII and Cubase. A remarkable effort ! To me, your program’s ingress into Cubase in some ways is even deeper than the Novation’s own integration with Ableton. I have both DAWs, and the difference is quite noticeable, to me.
Thanks for sharing such amazing program for free.
2 Likes