Komplete Kontrol 3.0 Update - WORST UPDATE EVER!

Well - you could calm down a bit and just reinstall v2.9.6 - where everything works like it used to.

There is no need to even consider KKv3 unless you have the new Kontrol S Series MKIII keyboards.

If not - v2 is where youn should be - for a long while until NI straightens this mess out with v3.

VP

It may be time to switch to decaf. 😏

Welcome to the community?

Not always, my friend. Not always. With nearly 40 years of IT experience, the first 30+ of that being technical, I can say that updates should always be reviewed. This is true of OS updates, database updates (especially; OMG, those buggers can change the way things are rounded or sorted!), data center server firmware updates, the installation of security updates, and much much more.

It is only recently, with some OS updates such as Windows, Linux, Android, and iOS, where we all got trained to just put things on "autopilot". Well, some of us old farts STILL don't do that. When you brick a mainframe's processor or a smartphone because you didn't read the fine print....well, when you know, you know...right?

Now then, I will say that Native Instruments should have "forked" KK so that it would appear twice in Native Access...once as a "Legacy Komplete Kontrol" version, and again as a "New Komplete Kontrol" version, and the new one probably shouldn't even appear as an option unless that customer's profile includes a valid serial number for a MK3 keyboard.

Yes, there were numerous things Native Instruments COULD HAVE DONE to make this a smoother experience. But they didn't do it.

In my opinion, they just needed one of us cranky old IT codgers who cut our teeth on punched cards and paper tape to give them a woodshedding when they were planning to just start pushing 3.0 out to all NA users.

But they didn't. Or they had some cranky old beta testers who gave them that woodshedding, but were passed over for whatever reason.

At this point, it is what it is, and now you know.

And welcome aboard, by the way! 😀

Yep, same as what I said above. I think they could have done it in NA by creating it as a new entry. I know it breaks some rules, but just call it "Komplete Kontrol Version 3" and make it so it only shows up if a valid MK3 keyboard serial has been entered into Native Access. Hey, we all had to enter it anyway, right? So the info is in there. And then maybe rename the old one to "Komplete Kontrol Version 2"

If that gives some people naming convention conniptions (putting a version number in the name), then they could have just called one "Legacy" and the other one "New Generation" or "MK3", or something like that. And add a note for each one that it removes the other one because only one can be installed at a time.

Way back about 6 or 7 presidential adminstrations ago, I spent 5+ years of my career maintaining a "director" software program that would decide which database to send various requests to. We had 2 different databases with different genealogies from a prior company merger, and those databases just could not be combined with the small number of personnel we had available to do the work that would be needed. So this director software would be the little "traffic cop" that would look at each database request and then send it down the road it needed to go.

The director program was written in assembler, and I hated it with the passion of a thousand burning suns. But it worked for the business, gave me a world of IT technical experience, and also allowed me to support myself early in my career. Eventually, the company laid off a bunch of us and I was finally able to give that role to somebody else much farther up the chain. No, he didn't like it either, hehe.

But NI should have done this, either in NA or in the Komplete Kontrol code itself...or something like it. It may not be too late to get a wiz-bang dev to work this.

Always good idea in IT to review changelog prior to installing any update