Komplete Kontrol S-series MK2 Owners Discussion

[TimC340]

No, as I understand it there are some elements of the keyboard's interaction with Studio One that may need the OSC protocol to be live as well. However - and I may well try this and see if it works! - if you install the keyboard as an MCU controller unit, with no reference to it being an NI device, I believe it should control the DAW within the limits of the MCU protocol - though I wouldn't put it past NI to have put a filter within the system that translates MCU to NI-speak, and which needs a translator either in the keyboard or in the DAW!

Basic MCU was the exact process by which the Behringer X-Touch was installed - though Studio One allows you to name the controller - and basic MCU on that device works just fine (and is more capable than it's sometimes given credit for). It's also the process by which a StreamDeck can be made to control the DAW via LoopMidi; those who have the Sideshow FX StreamDeck Studio One profile will know exactly how comprehensive the control set is, and that it also has a degree of plugin control all through Midi, with no secondary scripts required in Studio One whatsoever.

No-one's arguing that NKS isn't a marvellous system, and that as pretty much an industry standard it isn't a great thing to have. And the extensions to it that the v2 S Mk3 firmware offers in supported DAWs are excellent, and I very much hope we see them enabled in Studio Pro.

 

[Coopaz]

Hi Gang,
Original Poster here.
Lots of deep thoughts shared here on the future of NKS, MCU, Fender and all. Thanks.

I was just trying to find someone who might have had experience with the original problem stated:
In my projects, as I change tracks, the KB display, controls and LEDS stay on the last instrument I loaded. When the KB is in Instance mode, it shows no tracks, not even the one just loaded via the KB. Also, in mixer mode, the display is blank. There are a couple of additional symptoms I can share if someone thinks it will help with a diagnosis.
.
I've tried switching between KK version 2.9.6 and 3.5. Both give the same results.
All systems worked at some time in the past when I was running SO 6.x and KK 2.9.x.

Does anyone have any experience like this or know what measures I might be able to take to restore my system back to where a fresh install might work like new? I have followed a couple of uninstall processes, but think there must still be some vestigial driver, db file or other that keeps these symptoms recurring.

Thanks in advance.

 

[Vocalpoint]

I was just trying to find someone who might have had experience with the original problem stated: In my projects, as I change tracks, the KB display, controls and LEDS stay on the last instrument I loaded. When the KB is in Instance mode, it shows no tracks, not even the one just loaded via the KB. Also, in mixer mode, the display is blank. There are a couple of additional symptoms I can share if someone thinks it will help with a diagnosis.

The one and only time I have ever seen this exact behavior is when I upgraded from v5 to v6. The Studio One process is supposed to "pick up" all existing setting and migrate them from one version to the other INCLUDING all external instrument references.

When I fired up v6 for the first time after the upgrade - I saw the identical behavior as you are describing - KK staying on the loading instrument and never changing no matter how many instances were loaded or which track I clicked on etc.

The only way I fixed it - was to dump ALL references to the S61 in external instruments (in S1) and add them all over again - including a deep clean of the Komplete Kontrol software.

Tip - in you case - if you have ever attempted to install KK 3.5.x and did NOT completely remove KK v2.9.6 beforehand - I can tell you system is probably messed up on a lower level. These two versions can never co-exist and installing them together is not supported and guaranteed to give you trouble (per NI).

If it was me - I would deep clean your DAW starting by removing all external instruments, removing KK (ALL version), and maybe even using the NI deep clean tool to see if any other remnants are laying around. Then start over by reinstalling KK v2.9.6. Then readd the S61 as a new External Instrument in SP8

Extra Power Tip: If you really want the S61 to behave - how you start it up (and when) is critical as well. In all my use of Studio One - the golden rule is - ALL hardware must be powered on (and ready) before ever launching S1/SP8. If you are doing this in other way - that also could be contributing to your issues.

Let us know how it goes.

VP

 

[Coopaz]

The one and only time I have ever seen this exact behavior is when I upgraded from v5 to v6. The Studio One process is supposed to "pick up" all existing setting and migrate them from one version to the other INCLUDING all external instrument references.

When I fired up v6 for the first time after the upgrade - I saw the identical behavior as you are describing - KK staying on the loading instrument and never changing no matter how many instances were loaded or which track I clicked on etc.

The only way I fixed it - was to dump ALL references to the S61 in external instruments (in S1) and add them all over again - including a deep clean of the Komplete Kontrol software.

Tip - in you case - if you have ever attempted to install KK 3.5.x and did NOT completely remove KK v2.9.6 beforehand - I can tell you system is probably messed up on a lower level. These two versions can never co-exist and installing them together is not supported and guaranteed to give you trouble (per NI).

If it was me - I would deep clean your DAW starting by removing all external instruments, removing KK (ALL version), and maybe even using the NI deep clean tool to see if any other remnants are laying around. Then start over by reinstalling KK v2.9.6. Then readd the S61 as a new External Instrument in SP8

Extra Power Tip: If you really want the S61 to behave - how you start it up (and when) is critical as well. In all my use of Studio One - the golden rule is - ALL hardware must be powered on (and ready) before ever launching S1/SP8. If you are doing this in other way - that also could be contributing to your issues.

Let us know how it goes.

VP

Thanks, will drop a note when I get a break between projects to try all this. Cheers!