Why can't you fix Native Access?

David Macklem · 2023-10-08T03:36:52+00:00

There was an error rendering this rich post.

Seriously, though.

It's been broken a long time now. Every single time I open it (Mac), I have to go through a 12-step process and use Terminal.

Like.... will it EVER be fixed?

Don't reply with a cut/paste fix. WE KNOW HOW TO FIX IT.

If you have to cut/paste your response, please cut/paste the response about WHY you can't fix it.

Find more posts tagged with

Native Access

Comments

James Steele

It may not be an ideal solution, but if you were experiencing the issue where each time to run it you have to enter credentials and have it install helpers or support files, etc. a workaround I found is to find the app NTKDaemon.app in <hard drive>/Library/Application Support/Native Instruments/NTK/ and drag it to your dock so you can launch it from the dock. Then, what I do is any time I need to run Native Access I click NTKDaemon on the dock (it won't bounce for whatever reason to show you it's running)... count to four... then launch Native Access. I then won't usually have to go through the installing of helpers or whatever again.

I found what appears to be causing the problem is NTKDaemon.app is supposed to run in the background when you first start up your Mac, but the app seems to be unstable and it quits itself spontaneously. When the app isn't running is when you get prompted for credentials, etc.

PoorFellow

https://community.native-instruments.com/discussion/comment/98989#Comment_98989

At some point Native Access had a some what similar problem where a 'work around' / 'temporary fix' was to set the service to delayed start on Windows. I don't know if MAC OS have a similar functionality or if it will even help but it is something that you could check out.

At PC it meant that the startup in the background were delayed by 30 ? - 60 ? seconds , though any actual numbers may depend on system resources and system load !

Kymeia

I don’t know what the problem is but I have been using NA on Mac for as long as I can remember and have never had a single issue so it may well be a problem with your system setup rather than NA per se

David Macklem

I see Kymeia. It's my system setup that is wrong. Thank you. Very useful.

Kymeia

https://community.native-instruments.com/discussion/comment/99178#Comment_99178

What would be useful is trying to identify the reasons it works on some systems but not yours. To solve a problem you first have to identify where the problem lies, clearly if something is working on some systems but not others there is indeed some difference between those systems where it is working and where it is not. If you want people to help you then you need to be more specific about the problem you are experiencing and your system setup

LostInFoundation

I think the OP was calling NI to their duty (fixing issues many users are experiencing), not a request for help.

He even stated clearly he knows how to fix it…just wants the program to be working correctly and not in need for workarounds.

It doesn’t seem like a wrong request to me

Kymeia

https://community.native-instruments.com/discussion/comment/99197#Comment_99197

I'm not saying it is, just that it helps to be a lot more specific about which problems are being experienced than just saying 'fix it' because not everyone is having to go through a '12-step process and use Terminal' just to get NA to work, to me that sounds like there is a difference between systems that don't need this and those that do and identifying what that is is the only way NI are going to be able to 'fix it'

LostInFoundation

https://community.native-instruments.com/discussion/comment/99200#Comment_99200

Are we talking about the same issues MANY users have already reported from MONTHS and therefore NI is already more than aware of?

Kymeia

https://community.native-instruments.com/discussion/comment/99207#Comment_99207

It’s not really possible to know without more information. I’ve seen a number of issues raised over the years, not all the same by any means, some have been fixed already, some not. I don’t think I have heard of anyone having to go through a 12 step process and use terminal just to get NA to open so I would suggest it would be useful to understand what is going on there in order to begin to see how to address the underlying cause. That is just a basic approach to troubleshooting software issues, you can’t fix anything, including problems in NA, without being able to identify what exactly is going on.

Kaldosh

I must admit the NTK Daemon on my system is also the culprit and randomly decide to start or not.

Kymeia

https://community.native-instruments.com/discussion/comment/99222#Comment_99222

yeah I’m still not really sure what that thing even does or why it is needed - however it is a good example of something that seems to affect some systems and not others (not mine for instance) and as you say even then it works sometimes but not others. If we really want NI to fix it once and for all we need to figure out why it works on some systems but not others and under which set of circumstances the “random” glitches occur

James Steele

https://community.native-instruments.com/discussion/comment/99226#Comment_99226

What it appears to do is launch a process you can see in Activity Monitor called "NTKDaemon." From what I can tell that needs to be running so that Native Access can log you in automatically when you launch it. I have observed instability in that process and watched in the Activity Monitor as it has spontaneously terminated. It appears that if the NTKDaemon process is not running, when you launch Native Access, you will be prompted for your credentials and helper installed, etc.

You can test this yourself by running Activity Monitor, finding the NTKDaemon process, selecting it, and then clicking the little circle with the X in the middle at the top of the window which will stop this process. After you stop it, if you launch Native Access, I'm pretty sure it will ask you for your login, etc.

Kymeia

Thanks - I’m sure I read it was supposed to be for Sounds.com integration, which obviously isn’t a thing anymore, maybe it has multiple functions?

As I said I have not experienced any instability with it personally which makes me conclude the instability on some systems must not be intrinsic to the process itself but only within certain environmental variables yet to be determined. That’s why it’s important to get that information to help track down the causes

James Steele

https://community.native-instruments.com/discussion/comment/99516#Comment_99516

Yeah... well not sure what exactly to do about that. I bought my Mac Studio M1 Max brand new and it shipped with Monterey. I did a clean install... carried nothing over. Now on Sonoma. I beta test for a number of companies, but this issue has persisted though all the aforementioned OS versions and a pretty streamlined system. To be honest, I'll use the workaround. I simply don't have the inclination nor massive amount of time that it would likely take to try to track down why the NTKDaemon process spontaneously terminates. Unfortunately, just not enough hours in the day, and again... the workaround is palatable.

Kymeia

I’m not on Sonoma yet but I have a M1 Max too, so our systems are similar. Bugs like this are infuriating to track down the causes.

Quick links

Unanswered questions