Feedback - Komplete Kontrol 3.0

Yeah, every time I have asked about this I get the NI "Radio Silence" so unless I missed a reply which is possible as I have notifications for this site off and I now only check in when I check my morning emails, I have a dreadful feeling sub banks have joined Kore.

Hmm.. Sample Drag+Drop?? Oh my!

Gonna latch on to this small bit of words that is the first indication (I think) that something may be "officially" brewing with a change to simultaneous viewing of found presets and active instrument .. to facilitate Sample Drag+Drop.

Does it mean this? Or would there be some other way to facilitate Sample Drag+Drop?

I want the simultaneous viewing for other reasons (richer preset auditioning) rather than for Sample Drag+Drop. But I'll take this ability by whatever reason makes it happen.

Hey, she will get back at you. Maybe by dragging you out to a performance of "The Nutcracker" with your in-laws, when what you REALLY want is to see the Christmas shows of either Trans Siberian Orchestra or Mannheim Steamroller. So carry on with the noisemaking, good sir; carry on!

Hmmm.... well, perhaps institutional purchasing takes a break...

But the masses? Bring on the toys!

Hi I have just signed up to this community sadly out of frustration with KKv3 browser that I have just updated to through NI Access and in the hope that NI will rethink the UI for this vital piece of sw.

As mentioned by many folk, the searching for, browsing, auditioning and installing of instruments/patches in V3 is a big backward step in comparison to v2. I won't repeat all the reasons as they are well presented in so many other posts, but just to say that usability has taken a big backward step. In simple terms, from a composer/producers point of view it now takes me much longer to find the 'right' sound . . . and my previous workflow has been severely slowed down.

Surely the primary role of the browser is to enable me to find the right sound quickly and efficiently with as few mouse/keyboard inputs as possible. I do wonder whether NI undertook any user testing of the V3 release as this primary function is now worse than that of v2.

Sorry NI, but there it is. Time to fix this backward step and quickly please.

Yep, I guess every MK2 owner is currently very disappointed about the current situation, hoping that KK3 will be usable very soon. The more important it is now that we - the customers contributing to this community and giving feedback about the currently insufficient KK3 abilities - are pulling on the same end of the rope.

We simply have to make clear to NI that asking for the return of important - but obviously cancelled - KK2 functionality, like well-established operational features, viewing and management options etc. isn't just a joke or a dedicated wish to Santa Clause, but an essential requirement to keep us working smoothly. There's no need to put such stumbling blocks in our way. Customers should be entitled to proceed with their daily business in an acceptable way, using actually supported and updated NI software. In other words, it is simply expected that any recent release of a particular application/plugin - like KK - is keeping essential functionality intact instead of dropping it. This especially includes the requirement to keep fostering the previous (but still not obsolete) MK2 keyboard's NKS abilities and workflows to their full potential while natively supporting the new MK3 keyboard with its specific NKS2 attributes. That's a no-brainer. Nothing more or less is to be claimed here.

The argument that any MK2 owners, who are not happy about missing KK3 features, should keep on using KK2 instead, is falling flat. For MK2 owners, seriously being concerned about their music business in the future, there would never be a good reason to invest in a new MK3 keyboard, as long as all the abandoned KK2 features haven't been actually re-implemented into KK3. Why? Simply because of the fact that it's not possible to use both, MK2 and MK3 hardware in parallel in one's studio setup without giving up on very essential functionalities and workflows already established in the past, especially when working with the MK2.

KK2, necessary for utilizing all these well-known MK2 features and effective views has been shelved by NI earlier than expected, and KK3 was incomprehensibly introduced as an incomplete replacement for it, but unfortunately tailored to satisfy MK3 keyboard owners only, as it seems. There's nothing in between for existing NI customers to choose from, not even for a transitional period. After all, NI has made sure that any parallel operation of KK2 and KK3 within the same studio environment - and its simultaneous use within any DAW - is quite impossible. Either this important aspect has been overseen by NI, or it has been ignored intentionally. To our surprise, KK still claims to be the same product (but as everyone can see it isn't by far yet).

The logical consequence is to push for the only feasible solution there is for this problem, namely to make the KK3 application/plugin compliant again with all previous MK2 use cases and workflows; in the same way as this is natively foreseen to be introduced for the new MK3-specific attributes. Not sure why existing users should suffer from bad compromises and should regularly have to act as supplicants for things that are actually their right, namly to be taken seriously and finally heard. NI should give us a perspective by telling us some planned milestones for KK3 improvements, going exactly in the direction people are expecting it to go. If only promises are made, but week after week is passing by without observing any progress, these kind of customer complains will never end.