• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Komplete Kontrol S-series MK2 Owners Discussion

C

Coopaz

New member
I have been using a Komplete Kontrol S88 MK2 with Studio One since version 5. x or so (now using Fender 8.0). I had a great integration experience and found all features worked as advertised as far I as could tell.
Somewhere along the way, around when Komplete Kontrol SW version 3.x came out things went off the rails. I lost most of the DAW integration, except for transport control. Even integration with the Komplete Kontrol VST got out of whack, where the KB display would no longer show the plugin corresponding to the selected track in SO. I tried reverting to KK version 2.9.6 and did not get relief. When using 2.9.6, much more of the DAW integration worked, including in the Mixer mode on the KB, but the display was blank in mixer mode, even though the control pots adjusted track volume and the solo/mute functions worked, albeit with no illumination of the buttons.

KK version 3.5, of course provides all the new display/browsing improvements on the DAW screens, but allows no DAW control from the KB, except transport control.

There is probably more information to give to detail my varied experiences, but after having read through many threads here, I thought a fresh discussion on experiences of users of Studio One/Pro and the KK S-series MK2 KB would help some of us who own or are considering buying a used one.

What thoughts and experiences with KK versions are people having?
What functionality is working on the various combination of versions?
Has anyone managed to restore pre-KK3.x functionality, either by reverting to 2.9.6 or tweaking in 3.x?

Other questions welcome. Also links to other threads, please.

Fender Studio Pro 8.0.1/Komplete Kontrol S88 MK2/Windows 11/Komplete Kontrol 2.9.6 and 3.5
 
You'll get more informed responses from actual owners like Lokefly and Vocalpoint, but as a follower of this forum, they've consistently said their KK S-series Mk 2 keyboard controllers were working great through at least S1 7.2; perhaps they haven't switched to V8 yet.

If, as you suspect, your integration only became compromised after switching to V8, well, that brings up another issue—why there seems to be a high degree of difficulty getting other manufacturers' controller keyboards properly integrated with Presonus/Fender software. As things now stand, any change on either end seems liable to put things out of order.

At the risk of repeating myself from other threads, neither the mk3 keyboards from Arturia or NI integrated properly with V7; and other keyboard workstations which can double as keyboard controllers—like Roland Fantom and Yamaha Montage/MODX—can't properly integrate with V7 or V8 as things now stand.

Coincidentally enough, Ari, our forum moderator and Fender Berlin developer mentioned in another thread earlier today that various software and hardware manufacturers are constantly working with each other to improve the user experience. It would be helpful to know a little more from him why S1/FSP has been behind the curve on some of these developments and whether we can expect the situation to resolve positively at some point.

Please note than I'm not minimizing the effort it takes to iron out the process of handshaking. Or placing all the blame on Fender Berlin. But a lot of us use NI and Arturia keyboard controllers. It would be really helpful to have a few words on this matter. Thank you for considering this request.
 
When they first came out, I bought a S61 Mk1 and fell in love with it.
Because of my connections and affiliation with NI, they sent me a demo S61 Mk2 of which the screens both crapped out in 3 days.
They sent me another one a few weeks later and it lit up but refused to communicate with my system, no integration, no transport, etc.
I sent both of them back and still have my Mk1 happily crusin' along.
I just learned to navigate quickly to the current instrument/track and never looked back.
 
Thanks for the notes Mr. E! I might not have been clear, but my troubles aren't related to V7 vs. V8. They were coincident with the changes in Komplete Kontrol from 2.9.6 to 3.x. I know this is a SO forum, but I'm hoping to find a similar user to hear their experiences.
 
I've just had a complete meltdown of KK/Kontakt 8.8 on my home setup - needing a total reinstall of everything, including 4Tb of libraries... Desperately hoping the same issue hasn't affected my studio setup as the 30mb/s internet would make that extremely painful!

My S88 Mk 3 barely talks to S1/SP; it'll do the basic Mackie stuff but no more. I'm now doubtful that we'll ever get the functionality that came with the v2 firmware for the S Mk3, and which makes it an absolute pleasure to use with Cubase or Logic. However, my Nektar Panorama T6 and Aruba work very well with both S1 and SP, and also play reasonably nicely with Kontakt (especially within Nektarine) - I just wish Nektar would make an 88-key weighted keyboard in the same tier as the S Mk3 and Keylab Mk 3 (no, the Impact LX88 Mk3 is not that product!).
 
Coopaz said:
Thanks for the notes Mr. E! I might not have been clear, but my troubles aren't related to V7 vs. V8. They were coincident with the changes in Komplete Kontrol from 2.9.6 to 3.x. I know this is a SO forum, but I'm hoping to find a similar user to hear their experiences.
Click to expand...

I have yet to move to SPv8 - but v7.2.3 is as rock solid as ever.

Over here with my S61 MKII - there is no sign of KK v3.x whatsoever. I refuse to install that version - period. v2.9.6 however - continues to rock and has all control fully enabled.

I am in the middle of planning for a new DAW build - which will include a new S61 MKIII (which is still sitting in it's box over here). And yes I will finally give KK v3.5.x the time of day.

To be completely honest - I maintain that an S61 MKII AND KKv3 - are a poor match. I am also convinced the only way to get any semblance of "correct" operation with KK v3.5.x (in any way) is to use it with a MKIII board.

These two were built in concert and I still think these two are the only combos that really get tested. Cannot see NI spending any extra time with a MKII while testing KKv3. Yes - they claim that KKv3 "supports" the MKII - but that does not mean that support is deep. It is basic at best.

Bottom line in all my experience for the last 5 years - if you want the very best from a MKII IN any version of Studio One/Studio Pro - stay with KK v2.9.6 - period. Works for me.

VP
 
TimC340 said:
My S88 Mk 3 barely talks to S1/SP; it'll do the basic Mackie stuff but no more.
Click to expand...

Did you install the Hardware Connection Service v2.07 from Native Access?

This is critical to have any chance at a full working MKIII with supported DAWs.

VP
 
Yes, I have that. Nevertheless, the interaction is still pretty much basic Mackie - with the added limitation of few physical controls. OTOH, the interaction with KK is outstanding. It's the only keyboard I have in my studio, so I haven't found myself too restricted by its limitations. My Nektar stuff is attached to my computer in my house, and - until my new studio is complete - that's the way it'll stay as my shed is too small to accommodate much more than it has squeezed into it already. My Icon P-1M combined with a Stream Deck XL does all the control interaction with S1/SP that I'll probably ever need so, if the v2 firmware update never happens for Studio One/Pro, I won't feel too hard done by!
 
TimC340 said:
Yes, I have that. Nevertheless, the interaction is still pretty much basic Mackie - with the added limitation of few physical controls. OTOH, the interaction with KK is outstanding. It's the only keyboard I have in my studio, so I haven't found myself too restricted by its limitations.
Click to expand...

Well - I am unaware of any sudden "limitations" to using a MKIII/KKv3.5.x combo with Studio One v7.2.3 OR v8 at this time.

Unless Fender has suddenly caused it's standard Komplete Kontrol support to regress to the point of nothingness - you should have the same level of integration as before.

There are TONS of S1/SP8 users out there with MKIII boards attached. If there was rampant outcry of "Mackie" like vibes out there with KKv3.5.x - pretty sure we would have heard that by now.

Another QUESTION: Did you "upgrade" to SP8 and allow it to simple "migrate" all your S-Series controller settings?

I had a situation back when I believe I migrated from v5 to v6 and simply "let" the S1 installer do its thing. Once v6 was finally setup - I distinctly remember my S61 - doing exactly next to nothing in there. I spent hours messing around until I finally just deleted the external instrument entry and READDED the board again. It immediately snapped back to normal.

This was one of the only times I ever saw the Studio One install "migration" process go off the rails so it might be worth trying to over there.

VP
 
Last edited:
Like Vocalpoint, my S2 (49 MKII in my case) on S1, v7.2.3 is solid. I never had time to change any firmware or drivers. Currently, my equipment, controllers, guitars and amps are in another state. Lol. So I won't be able to attempt any changes. I will tell you, from my using the MKII, creating/deleting recorded tracks, mixing, and navigating around the DAW hands-free is like nothing else I tried. Of course that is within the KK eco system. I did hear of said conflict with v3.x on what I thought was with the MKIII, but I'm honestly not that close to those issues. As it stands, I'm likely going to hold with S1 v7 for a while and see what shakes out. It's seriously important to have stability, but I'll keep my eyes on this very good thread going forward.

My hopes would be that we all get what we're looking for. Particularly, Vocalpoint, who purchased a MKIII and is in the dumps, until Hamburg (I'll say) get a fix on the latest update, because as I understand it, the Other DAW's comply with the latest fix. Or NI complies with the latest other DAW's. Like I said, I'm really not in the know. Sort of from the "if it works, dont fix it" camp. But that's really sad when someone steps up their gear and is left high and dry on somebody's non conformance.
 
I had Cubase 15 on trial over the last 2 months (the trial has expired now) and the integration with the S Mk 3 was excellent - and leaves me excited for how it might be with SP8 when the v2 NI firmware is eventually enabled by Fender, if that actually happens.

The current level of integration is (and always has been) pretty much the basic Mackie protocol - DAW transport, track level and pan controls, and receipt of banks of 8 track levels at a time. As this page tells us, the only DAWs that get a greater depth of integration are Logic, Ableton and Cubase/Nuendo.

It may well be that the integration of the Mk2 with S1/SP is more comprehensive, but I don’t have one and never have. Obviously, the Mk3’s integration with KK (standalone or in the DAW) is very comprehensive indeed, and is a delight to use.
 
It's my understanding that with the Mk3, you can simply stay in Kontakt 8, or some relevant instrument like for example FM8 and have the ability to select NKS selections. In other words, not have to stay with Komplete Kontrol. That's a worthy upgrade when the time comes.
 
lokeyfly said:
It's my understanding that with the Mk3, you can simply stay in Kontakt 8, or some relevant instrument like for example FM8 and have the ability to select NKS selections. In other words, not have to stay with Komplete Kontrol. That's a worthy upgrade when the time comes.
Click to expand...

Yes, that’s correct - anything that runs in Kontakt 8 is fully controllable by the S Mk3 from within Kontakt, though not everything is necessarily mapped. Some instruments are far too complex for that! But you can make your own maps.
 
TimC340 said:
Yes, that’s correct - anything that runs in Kontakt 8 is fully controllable by the S Mk3 from within Kontakt, though not everything is necessarily mapped. Some instruments are far too complex for that! But you can make your own maps.
Click to expand...
Sweet. Might have to upgrade to MK3 when my MK2 display finishes its death spiral.
 
BobF said:
Sweet. Might have to upgrade to MK3 when my MK2 display finishes its death spiral.
Click to expand...
Going down that path begs a question: how is buying a controller keyboard which has never lived up to its promise (unless you happen to work in Cubase) from a company mired in insolvency proceedings, when neither that company nor Fender has pledged to iron out handshaking challenges, a sounder decision than moving into an apartment with bedbugs?
 
MisterE said:
Going down that path begs a question: how is buying a controller keyboard which has never lived up to its promise (unless you happen to work in Cubase) from a company mired in insolvency proceedings, when neither that company nor Fender has pledged to iron out handshaking challenges, a sounder decision than moving into an apartment with bedbugs?
Click to expand...

Upgrading to MKIII does not change the integration that we already get with a MKII within S1/SP8. That continues as normal - but yes the "additional" integrations that the MKIII v2 firmware provides - remains unresolved. But this has nothing to do with the recent financial news.

At last check (and I check often) the specs were published, DAW partners and Ni are/were dialoging - and I still believe this one is currently is Fender's hands to do something with.

VP
 
The capabilities of the Kontrol S keyboards (Mk2 or Mk3) are not affected by the current financial travails of Native Instruments, though I wouldn't rush to buy a new Mk3 until there's some clarity over whether there will be long-term support. Those of us who already have an NI keyboard will, I'm sure, continue to enjoy them until such time as they no longer work or the whole scene has moved on (as it inevitably will). However, I'm reasonably confident that NI will survive this in some form or other, and that long term support will be assured once more.
 
Really thankful to find a vibrant conversation in this area (especially VP!).

I had SO v6.x running with some version (2.x) of KK for some time. At some point stepped up to KK 3.x and the associated firmware upgrade.
That is likely where the troubles started. I've tried to roll back to KK 2.9.6, but still end up with the symptoms described (e.g. KB display doesn't follow the track selection in SO, Mixer mode is blank screen). I'm trying to understand what vestige of the 3.x upgrade may still linger in my system to prevent KK/SO from working together as they did in the past. Is it the firmware (0.59 vs. 0.6)? Or is there an additional driver or hardware service (beyond the Windows "Uninstall" processes) that I need to delete to truly bring the system back to pre KK3.x?

Also, thanks everyone else for the supplemental MK3 comments which are outside the scope. :D They may come in handy down the road.

I also want to mention that in spite of all the NI insolvency talk, they are trying hard to provide support on this with pretty good interaction (but, alas, no solution yet).

C (hoping to be well-known member, some day).
 
I am also a KK MK2 user. I don't find myself using the integration much, however, but when I do, it does what I want it to so. Honestly, I need to sit down and really play with it to figure out how it will help my workflow. Currently, for the most part, I record my tracks, then use automation after the fact that do all the fancy stuff. Yes...I know. It would be so much easier to use the KK Integration. I'm just SO used to doing it the way I do it, I almost think it would take more time to learn, but I have been happy with the results so far when I have tried it.
 
You must log in or register to reply here.
Back
Top