Can MK3 Keyboards be used in plugin mode with KK 2.9.4?

I received my MK3 88 key today, and updated all firmware etc with no problem. Transport controls in Logic are all fine, but I'm unable to use the browser or plugin modes with 2.9.4, either in KK standalone or within Logic.

Do I have to update to KK 3.0 for this? I'm hoping not, as that'd be a big problem with the CPU spike / instability issues I'm having,

Find more posts tagged with

Comments

RobertDorn

Yep, you’re doomed, use your MK3 keyboard just as any other brand keyboard with 2.9.4 or get non stop cpu spikes with 3.0 . I’d choose the first because you’re at least able to continue your work.

mattse

Nah, I think I'm better off returning it in that case, and continuing with my MK2. Once NI hopefully have the software sorted out I can maybe try again.

I'll give it a day of further testing on 3.0 before making a decision (e.g. rolling back the Kontakt version to 7.0, in case it's that which is causing the slowness/spikes), but I can't justify wasting countless hours trying to get the software to function, when it's blatantly an issue for a significant amount of users.

What a faff!

RobertDorn

https://community.native-instruments.com/discussion/comment/101852#Comment_101852

This is what I probably would have done in this case. Happily enjoying my mk2 with kk2.9.4 and actually I won’t be opening native access anytime soon since the last 3.0 Komplete kontrol I accidentally did caused quite some headaches over here. This whole mk3 hardware with bricked firmware issues all over this forum combined with kk v3.0 causing cpu spikes -and even if it doesn’t still being 3 steps backwards with the UI compared to v2 where users have to switch between browse and instrument windows- is quite a thing. And now that it’s out, the NI team members are going on Holliday one after one, because they worked for over a year on this release . Well , good luck to all the customers with their broken setups, oh myyyyy goodnessssd 🙈🙈

JesterMgee

I am sure (cautiously hopeful) v3.0 will improve however as it stands, it is far off the mark from being both reliable and an improvement in functionality/usability over V2 as it would seem from the many posts about it.

The issue people will face adopting a new hardware + software package on day 1 is issues. Seldom do things work perfect at v1.0 (which lets face it, the new v3 KK is basically a complete rewrite and is a new v1.0 of the software) and the unfortunate track record NI has it can take YEARS to address issues (if ever) so it's a game of "do we place some faith in the new team that they can deliver" or "best to just send it back and revisit in the future" . I am personally of the latter and at the current stage, no features in the new MK3 are appealing enough to me to make me want to use v3 of KK over v2 for a list of reasons.

If you already have an MK2 keyboard i'd say stick with it for at least 6 months and watch the space to see if things improve along the lines of what people are asking for and the issues reported are being addressed.

mattse

Cautiously hopeful tends to be my outlook and I think I was perhaps too hasty in the MK3 purchase. The MK2 / 2.9 combo works very well and efficiently on my system and I can't really afford to downgrade my workflow with the updates, based on 3.0 being improved/fixed in an unknown amount of time in the future.

Quick links

Unanswered questions