Komplete Kontrol S-Series MK2 Custom Script For Cubase 12

mchantzi
mchantzi Member Posts: 11 Newcomer
edited May 26 in Komplete Kontrol

Hi there, I'm happy to share my personal script for the Komplete Kontrol S MK2 inside Cubase 12, using Steinberg's new Midi Remote API.

Komplete kontrol script for cubase

It currently covers Mixer, Focused Quick Controls, Instrument Quick Controls, Inserts, Sends, Channel Strip, and some commands sets.

I've uploaded details and the script's file in Steinberg's subForum for midiRemote, here:


https://forums.steinberg.net/t/komplete-kontrol-s-series-mk2-custom-script/848132


Hope it may be useful to some of us :)


Minas

Tagged:

Comments

  • LostInFoundation
    LostInFoundation Member Posts: 1,782 Expert

    Very generous by your side. Once again, NI is lucky to have users so generous to make the job they should do

  • mchantzi
    mchantzi Member Posts: 11 Newcomer
    https://community.native-instruments.com/discussion/comment/69429#Comment_69429

    Hi there, thank you for your kind words!

    Now, the way I see it, and since tools as the midi remote API by Steinberg and other ones for other DAWs as well, are designed to help users to customise the controller's behaviour based on their personal workflow, I'm not 100% sure whether NI should really get into this, since they do have an integration which pretty much covers the basic (and generic) needs.

  • LostInFoundation
    LostInFoundation Member Posts: 1,782 Expert
    https://community.native-instruments.com/discussion/comment/69459#Comment_69459

    I can in some way agree. But when you build products, giving some instruments to allow less experienced users to use them at least with the main DAWs should be something companies have a look at, in my opinion. Even because in this way they could suggest what, in their opinion is the best way to use X with Y. An user templates follow this user needs, not the general needs.

    But I see your point 👍🏼

  • mchantzi
    mchantzi Member Posts: 11 Newcomer
    https://community.native-instruments.com/discussion/comment/69460#Comment_69460

    It's true that the way a company visualises its own products' functionalities should be exposed by their implementation, 100% agree!

  • Griswold3
    Griswold3 Member Posts: 10 Newcomer

    Hey guys I’m curious. Does something like this exist for Studio One? If so maybe you could point me in the right direction.

    Thanks!

  • mchantzi
    mchantzi Member Posts: 11 Newcomer

    Hi mate, I know almost nothing about Studio1 on this aspect (though I have a licence for it, but just didn't have the time yet to really dive into it), but I do know it has its own scripting language (most probably javascript). Other than that, I'm totally clueless, perhaps a google-search might be of help :(

  • LostInFoundation
    LostInFoundation Member Posts: 1,782 Expert
    https://community.native-instruments.com/discussion/comment/69539#Comment_69539

    S series has already a quite good integration with Studio One. You can find Presonus original script in the list of controllers in Midi setup, under Native Instruments

  • D-One
    D-One Moderator Posts: 1,469 mod

    wow, cool!!

    I'm confused about what's happening here tho... The "DAW Integration" (the one that shows the meters instead of regular MIDI MODE) is not supposed to be editable in any way, how did you achieve that?

    Renaming the .DLL (so it's not loaded) causes it to not load and somehow be freely editable?

  • mchantzi
    mchantzi Member Posts: 11 Newcomer
    https://community.native-instruments.com/discussion/comment/71249#Comment_71249

    Hi, once we remove/rename the original dll, it's just not getting activated, thus not controlling the daw port. So, this port is now free and we can use scripting to talk with NIHIA by using it. Now, NIHIA is responsible for updating the controller's UI after it receives by us the appropriate sysexes/ccs for the UI's elements of the controller :)

Back To Top

Categories