Bug Transport buttons issue with Logic Pro X (KBDSW-6814)

Hey Elliott,
I'm not sure what post from 2015 you found around the internet regarding similar issues and how many users were affected, if you have any links to share, please do. This peculiar bug started to affect a lot of users when Logic 10.5 was introduced in May 2020.

 

Good evening Jeremy,

I will go back 1 step from my very upset post on Sunday and will stick with NI / the keyboard a bit longer for mainly two reasons:

1) Though I'm really unhappy with the non-working Hardware, I do like the quality of the sounds that NI offers under their Komplete Kontrol - though it isn't yet working in Logic as it should.
2) The good and professional work that you, Jeremy, do here in the community forum.

Anyway I will not go for any further NI products like the ultimate bundle, as long as the issue is not fixed.
I really hope that this will happen soon and bring a stable integration with Logic as it is advertised.

Question: Since I just purchased the Keyboard I might be able to return it to the retailer and get it replaced with another one.
Do you see any chance that an exchange of the hardware might solve the issue?
Are there any M1 users running LogicPro without this issue that you are aware of?

Not sure if this is any useful, but I observed that the loss of transport controls happens not only after closing and re-opening LogicPro, but also if the Computer goes to rest. Even if LogicPro was never started during the session, if I start it the first time after the computer went to rest/snooze once, the transport controls will not work. (Only after a complete restart again).

I have other Daemons for USB / Thunderbolt devices running, like Logitech Options for Keyboard and Mouse, as well as the LG-OnScreen Control for the screen. Might there be any conflict with one of those?

The NTKDaemon does not show up at all in my activity monitor, so that this partial work around is not an option for me.

Again, I really hope this issue to be fixed soon, as well as getting the possibility to use the Keyboard without running LogicPro under Rosetta.

If it is likely that the NI team will give up fixing it, please let me/us know ASAP, so that there is a chance to send the keyboard back to the retailer before the right to do so expires.

Thank you Jeremy for your communication work here.

 

I'm not positive but I think it's working better now(?). I think the transport/mixer functions will work in Logic as long as I don't quit Logic in between launching projects. If I quit and restart the app then the transport is dead. But, I think this is an improvement....

 

I haven't been able to get in the studio and work until today, so I'll be testing and will report back. Thanks for continuing to work on this issue.

 

It appears there is no end in sight for this bug. I have about a week left to return my keyboard and will be doing so if there isn't some sort of update in the next few days.

 

Jeremy @ NI 2015 thread is regarding plugin disconnecting, looks like is now referred to, or resurfaced as "known issues with Logic pro 10.6". the issues look the same, and the overall stability for Logic doesn't appear ever solved. https://www.native-instruments.com/forum/threads/logic-pro-10-2-and-komplete-kontrol-issues.261035/

This newer thread from 2019 is specific to transport issues.
https://support.native-instruments....ntrol-M32-not-working-with-Logic-Pro-X-en-us-

Thanks!

 

Any updates?

 

Unfortunately, I have to report back that the problem is still present. Bug is not resolved for me.

 

Hi all!
After the update, exactly 2 sessions worked.
At the next launch of the logic the transport buttons of my S61Mk2 did not function.
Now even the solution of technical support with stopping NI services did not help...
Restart mac only.

Environment:
iMac (Retina 5K, 27-inch, 2020)
MacOS Catalina 10.15.7 (19H524)
Komplete Kontrol 2.6 2021-03-09
Komplete Kontrol S61Mk2
Logic Pro 10.6.0

 

Reading 2015 thread again, solution was removing other control surfaces and installing KK first. The auto detection in control surfaces worked fine, and transport works as expected! For now at least, I hope

Support should be more clear about these solutions. Not trying to mix the transport and focus issues, but they seem related. thanks!

 

I would like to say that I'm having the same issue. Unfortunately, I've only used this product a few times during the return window; otherwise, I would have returned it to get a different midi controller since that is what I'm left with at this point.

I have updated the firmware, used the NTKDaemon advice, and made sure everything was running correctly, and my system still continuously crashes when using the A61 as a DAW Controller. So I have to untick that little box and use my brand new DAW/Midi Controller it as an overpriced midi keyboard. Not so Bueno.

IMHO This is certainly a software issue that the software engineers must address to provide a solution. Otherwise, they should recall these keyboards and stop selling them as DAW controllers compatible with Logic X or at least provide a disclaimer they are not fully compatible with all versions of Logic X since it seems the problem is intermittent depending upon the user. If they have issues duplicating the error, they should remote in to watch the issue live on someone's computer. I mean, that's a thing, right??? For a company with such a clean appearance and overall great products, this is disheartening. Perhaps the marketing team should give the product support team some tips?

I'm really disappointed, to say the least, although I am happy with the Sound Library I've purchased. Where is the solution for overall customer service and satisfaction for the Logic community of users? I'm hoping they will at least provide a hack to resolve the problem until they find a permanent fix.

 

Angela Jackson there is a fix that should be put in place as an update soon regarding transport I believe. Not sure if support is allowed to share it but temp solution involves using a beta NIHostIntegration agent file.

Do you have more info on your system that is crashing? Logic? Version of KK? Do you have other control surfaces in Logic? What little box are you talking about. If its crashing logic entirely, sounds like you may need fresh install or review of the KK configuration, and control surfaces in Logic. If you have multiple control surfaces in logic, delete all of them and then turn on and auto detect your KK controller first. Cleared remaining track sync issues for me.

I understand your pain so why I'm curious. Take the notes seriously that this isn't broken for everyone and that the integration should work for you.

 

Hey Angela,
This Logic integration bug doesn't induce crashes, please get in touch with us through this typeform so we can check your particular problem :
http://bit.ly/NIsupport_KKontrol

 

Why is NI not acknowledging the issue when so many of us are see this? My computer is brand new and everything was renewed except the Maschine and Komplete Kontrol S88. Please fix this ASAP. I cannot believe that this issue cannot be replicated by NI.

 

Hey Suresh Raja, We acknowledged the issue. It is still being worked on. Unfortunately it is a very difficult issue.

 

I have the same Issues BUT, my A61 Controller does not appear in the controller surface menu, the only native instruments option is the S61 .
no transport controls ,but the stand alone apps work with the keyboard.

 

Hey Tyrone,
Then the issue is a bit different than the bug in this thread, please get in touch with us through this typeform : http://bit.ly/NIsupport_KKontrol

 

Same issue her. Transport buttons suddenly do not work anymore and only a reboot of the Mac solves the problem.
Hardware: Komplete control s66 with Logic Pro X 10.6.2, MBP 16“ with Catalina

 

I posted this issue a while ago, but since then I have had ZERO problems when I follow a certain procedure. I am using a new S61 keyboard. For me, this is the status:

Playback and all other buttons work just fine when I do this:
1. Startup my Mac fresh.
2. Start Komplete Kontrol standalone app.
3. Power up keyboard.
4. Start up Logic.

Playback buttons stop working when I do one of the following:
1. I open Chrome and a lot of tabs and go back and forth to Logic.
2. I use some other video/audio app for a while, like Zoom, then go back to Logic.
3. I've kept the computer on for many hours (>6) working in Logic.
4. Open and use demanding programs while keeping Logic running.

In all these cases, rebooting the computer and going through initial sequence solves it every time.

Having the KK software and being able to jump through sounds is kind of a huge deal, so I'm quite happen to reboot every once in a while. I am working 6-14 hours a day in the studio and it's a real timesaver.

 

I have the same issue, why hasnt NI sorted this out?