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

This is really annoying ... Had been working just fine up until a few days go for me. Now it's completely borked!

 

The above solution does not fix it for me. Rebooting the Mac does...at least until Logic is quit then restarted.

 

As frustrating as it must be for you guys who are having this this problem, it must be 1000x more frustrating for the NI guys. I don’t have this issue (fingers crossed) so the NI must be going nuts trying to figure out what, if anything, you guys have in common, what among the thousands of things it could be that could be the cause, if it’s any one thing, and how to fix it. It may not even be in their control. Random cables, peripherals, app interactions, hardware malfunctions…. What a nightmare.

 

Also, its a problem that appears to have been introduced by Apple some time ago and it is also just as frustrating for non Apple users having to sit and twiddle thumbs for much needed updates and features to be developed but are on hold because of constant attention needed to support Apples constantly changing needs and wants, makes me sad to even own a mac.

 

That's a bit extreme Jester. updates and development has not been put on hold.

 

Actually they have, it was announced a few weeks ago that for the next 12 months focus must be mainly on “compatibility” issues. While stuff is always going on in the back, features isnt something we will see for another 12 months, like the last 12 months has also been just macOS and Logic issues so 2 full years of potential development that takes up. Also affects other software I am involved with as apple change a whole heap of things under the hood between major versions especially around security preferences, it screws everyone, and I use mac but really dislike the OS because of this as Apples focus has never been on maintaining compatibility, quite the opposite as almost "you want to work on our system, you will follow the changes we demand of you" mentality.

Anyway, OT.

https://www.native-instruments.com/forum/threads/komplete-kontrol-2-6-1-software-update.457467/

 

It turns out I have the both issues too (no transport after quitting Logic and no browsing after pressing undo). I was unaware of it because of the way I operate--Kontakt in Logic to better learn routing and KK standalone when I'm learning the features of Komplete instruments. So It could be that the problems are more way more widespread than NI thinks because a lot of users just aren't using the apps in a way that triggers them. I'm all up to date on all NI and OS and Logic with a 2020 iMac, btw. It turns out that the transport buttons and 3D controller are super handy. I can see why people are so annoyed that they go offline so easily. I'm hoping that NI has a solution and is being cagey because it will be addressed after the next big Logic update but can't talk about it because Apple is Apple.

 

"this works for me"

 

interesting... I thought mine was related to start of using loopback but I guess I could test the switching hypothesis as well on mine... Don't use chrome much though

 

Under View in Activity Monitor, do you have "All Processes" selected... it's curious that the Deamon should not show on some people's machines...

 

Interesting. I use Loopback too (I assume you mean the Rogue Amoeba app). Why did you start to suspect it was causing the KK problem?

 

After updating Komplete Kontrol and Kontakt 5 lately I seem to be having an additional issue on top of the main one. Now after everytime I record a region the connection to the keyboard seems to drop (the lightguide, browser, etc...). The only thing that works is midi input. I have to click on the little keyboard icon in the kontakt window to bring it back up. ugh!!

 

I just submitted an update to NI support. This time logic audio got locked up when I switched off loopback app whilst logic was connected to it, switched loopback back on, changed the setting to sound card again, then in the next project after that transport controls in komplete were no longer working. Did the daemon force kill action again and it's back to normal

 

I have an M32 hooked up. I found that I had 2 NTKDaemon processes running when Logic's transport controls failed. Of note, when I terminated just one of these processes from the CLI, it spawned another 10 or so of the same NTKDaemon. Perhaps Native Instruments engineering needs to set a limit on this daemon to only run once on any given machine.

I was able to get Logic's transport controls working again with the following steps:

• Close Logic Pro X completely
  
• Open Activity Monitor
  
• Search for "NTKDaemon" in the top right search bar
  
• Select all running NTKDaemon processes with the Shift key
  
• Hit the "Stop" button in the top left (looks like a stop sign with an X in it)
• Open the Logic Pro X project again
  
• Check to make sure only one "NTKDaemon" has launched in the activity monitor
• Press the "Track" button on the M32 keyboard once Logic has loaded the project

For any people new to this keyboard, the "Track" button on upper right side of the M32 keyboard is used to switch away from the "Plugin/Browse" modes, which are used with the Komplete Kontrol plugin. This "Track" mode must be enabled for the Logic transport, volume, etc to function.

 

The force quitting of the "NTKDaemon" method may work for some, but doesn't in my case.

 

I actually don't see that in my cpu tab

 

How's everyone going with this problem?
Any solid solutions? ...without having to fully re-boot

 

My solution was to return the keyboard. Worked great!

 

That "NTKDaemon" Forcequit works great for me. Much better than having to restart logic AND my mac.

It would be great if it worked 100%, but come on it's DAWs - nothing ever works great. Still better than assigning controls in cubase 20 yrs ago, and having nothing work then lol.

 

My solution is to just not use mac or Logic, also works great.