What does NTKDaemon service do?
Comments
-
Did you give up? Any progress to report?
2 -
So Q4 last year has well and truly come and gone and you havent talked to us about this "lifecycle" of NTK Daemon, which is a concern to many of us. What do you mean open on startup? Start up of computer, NA or what? We want to know exactly WHY this thing needs to be active on our systems at all if we're not using NA. At the very very least we should have an option to turn it off if we want to. Anything that runs in the background and we aren't allowed to know what it does, is like a virus.
Im on NA1 and Activity Monitor (MAC) has no reference to it running. Im doing just fine on NA1, and Im STILL hearing of people fixing stuff by managing to locate a NA1 installer.
3 -
It's rather hidden away in a 14 page long thread, but Matthew just talked about all things NTK Daemon in more detail here:
0 -
Well, really all I do is link to this post from @Hayo_NI where he explains what it does.
0 -
TL;DR to the link Matt shared above, the NTK Daemon handles all product management stuff. This includes the downloading, installing, and activating of your products. Native Access is the window that you can interact with to choose what task you want it to run.
I wanna stress that NA1 is going to be deprecated by february 2025, and if you have any new products, they already do not appear in NA1.
2 -
And I wanna stress that programming the deprecation of a working program (and not making new products appear on it) while not being able to provide a working and viable solution for ALL users is really a bad move.
Maybe by February 2025 we will all be happy to use NA2 because it will be a perfect program (…), but if that will not be the case, NI is going to definetely be deprecated
After remembering you that
"Should Native Instruments for whatever reasons no longer be able to fulfil its obligations to deliver the activation key, it will provide the Licensee with a key which ensures the continued use of the software independent of changes of the computer."
As stated in your EULA when I bought my products (I don’t mind if you canceled it afterwards)
0 -
Is the NTK Daemon ever going to stop scanning my VST3 folder for ages when I open an app?
1 -
Yes I know all this already. Its not what Im wanting to know. What I want to know about is:
"we plan to address the NTK Daemon lifecycle"
What did you mean by this? I'm not alone in this. We want to know why this thing has to run on our systems when we are not using NA. We want to know if you will allow us to turn it off. My situation is this: I have K14 UCE and its been fully paid for and authorized as you know. Right now I have no need to even go to NA and havent been there for some time. There is no good reason then for something to run on my system all this time and for something Im only going to use briefly.
Agree with LIF. And to this day theres still people getting solutions by getting NA1 and there's still massive problems all over the board people crying out that they cant download stuff on NA2 or NA breaks their system or whatever.
Im also not in favour of something updating automatically. With the problems NA2/3??? is giving, and STILL having to ask AND WAIT for a response on a one on one basis to get older installers, is gruelling. Then theres the nightmare of dealing with googledrive, with unending failed downloads, and again, Im not alone. This is a chaotic situation for those of us who've been put through the wringer.
Please answer those things you said you would.
Please! there's more to it than your instruments we've chosen to use which we really enjoy and appreciate. It all means nothing if you force us into a situation we didn't agree to when we bought our products.
Right now, Im literally petrified of screwing up my system if I update KK, NA, or Kontakt. Quirks aside, my system is running pretty good and thats the way I want to keep it. The truth is Ive been in STANDBY mode for the better part of 2 years waiting for these products to deliver stability and promise. I still cant see the light at the end of the tunnel if the forums are anything to go by.
1 -
I can completely understand the frustration of you and others here so please do not misunderstand my intentions here , I am merely trying to inform.
What I want to know about is: "we plan to address the NTK Daemon lifecycle" What did you mean by this?
About the life cycle then Hayo_NI is a programmer and often refers to the N.A. project using programmers terms. So I think that Hayo_NI is referring to "Program Development Life Cycle (PDLC)" , and here he is referring to the making an "organized plan for breaking down the task of program development into manageable chunks, each of which must be completed before moving on to the next phase." . Meaning that Hayo_NI and the team are going to find out what N.A. to deal with next and the priorities of it all. Hayo_NI and the team has been on sort of a fixed track having to deal mostly with tasks that without discussion needed to be done. E.g. dealing with subscription integration , unification of iZotope , P.A. and N.I. product installation and transforming of the installers (including also Locate All). And after dealing with that then Hayo_NI and the team will be able to make new plans.
STILL having to ask AND WAIT for a response on a one on one basis to get older installers, is gruelling.
I tried to address this issue over here in a comment to the N.I. CPO and received no response on that. But I would like to point out here in this thread that while Hayo_NI is having to take the flak for it here from e.g. you then that is really not the decision of Hayo_NI. The downloads and lack of same are issues that is determined by company policies set by management. Hayo_NI is more of an engineer than a captain on the ship.
Agree with LIF. And to this day theres still people getting solutions by getting NA1 and there's still massive problems all over the board people crying out that they cant download stuff on NA2 or NA breaks their system or whatever.
I completely agree with you and LostInFoundation with respect to the points made about N.A. 1 and older software. And I personally think that N.I. have some (more) hard decisions to make and they need to make up their minds how they are going to handle all of this. I hope that they will somehow allow people to use their old software, but I sort of expect it to swing over to that there will be declared more EOL of products both with reference to general OS use but also because it will be impossible for N.I. to establish a real limit with respect to what to allow and what not to allow. E.g. it is not just a question of DRM of the EOL apps themselves but also a question of the DRM of the libraries and expansions which will result in a twirl into an uncontrollable spin that will have no end.
Anyway , I am not trying to exonerate Hayo_NI or trying to let him of the hook so to speak but I think that people need to try to understand that there is only so much that is actually up to Hayo_NI to decide here , the rest is decided by upper management.
2 -
PoorFellow Anyway , I am not trying to exonerate Hayo_NI or trying to let him of
the hook so to speak but I think that people need to try to understand
that there is only so much that is actually up to Hayo_NI to decide here
, the rest is decided by upper management.Unfortunately there is no way anyone can communicate with upper management and if it is the same as at most places I've worked, upper management don't communicate very well with their staff either. So, it's lose, lose and any messengers get shot. For years now, NI's attitude to its customers has been bad, and it only seems to be getting worse as the scanning fiasco(s) are proving.
Unfortunately, only they can make it better and that's only going to happen if they cared enough to actually want to and there's very little evidence of that……………………..
0 -
Thankyou for what seems to me is a well thought out and respectful response, recognizing genuine grievances as opposed to being accused of needless ranting, whinging and moaning like we've had here.
Your explanation of lifecycle makes sense. What I should've done though was quote the whole sentence.
"We've discussed lately that we plan to address the NTK Daemon lifecycle
at the end of this year, including whether it needs to open on startup
every time. "THATS what we want to hear about.
Again, we all really enjoy those products we've chosen to buy. But it can't end there when people are genuinely upset and angry through extended periods of downtime because of issues.
The thing is there is a lot of dovetailing with who deals with what in the NI team. The user base can't be expected to know who these people are and they're not accessible anyway. We basuically have to cry out to who we can. Probably the best example of dovetailing would be NA - which overshadows everything because everything has to go through it before it will work. When it is faulty it affects everything. Perfect example from me, if NA was all I hoped it would be by now, I wouldn't have had to (try) to use googledrive which ended in months of utter frastration from multiple failed downloads/wrong downloads/endless backing and forth with support wasting their and my time. I absolutely abhor being directed to google who I work very hard to avoid, let alone have an account to log in to to make something work. Would LOVE to see NI have everything in house.
So, this is why Hayo probably cops more flack, from frustrated people, because NA is a HUGE undertaking for sure. The irony is we dont need it much.
It would be nice if there was more presence from the NI team on here and people do appreciate Hayo's appearance. Even though I've pressed this point about NTKDaemon for a long time now, and there's been many words written all over the forum, its still has grey areas we want to know about.
1 -
"Even though I've pressed this point about NTKDaemon for a long time now, and there's been many words written all over the forum, its still has grey areas we want to know about"
You guys do realize that NTKDaemon most certainly contains proprietary licensing and authorization code and functions - and "grey areas" simply may not be up for discussion here (or anywhere) for obvious reasons.
Don't be too disappointed if little more than has already been revealed - can be said about it.
VP
0 -
I'm pretty sure that a lot more could be said without giving away anything secret. If it is doing something that greatly affects user usage, as it currently is in some cases, surely the user should be told ways of minimising the 'damage' or release the product once the damage has been minimised. I mean to a great extent we can already see some of the things it is doing in Process Monitor, and they tend not to make the greatest of sense which only tends to make people nervous, apprehensive and very suspicious……
Are they really thought to be desirable reactions????????
0 -
"Are they really thought to be desirable reactions?"
In the grand scheme of (potentially) thousands of users (most likely 10's of thousands) - 99.99% of whom do not come here or even know this forum exists - I think it is very fair to say nobody really cares one way or the other.
Can't really even picture a typical working musician or composer - like say - Hans Zimmer - sitting there in his studio today - using his copy of Kontakt or Komplete Kontrol - working on his next blockbuster score and worrying about NTK Daemon.
He is after all - using the same NI tools that we all use.
He probably has better things to do.
VP
2 -
I guess the thing that grinds at me the most here is there are users that treat the NI development group as if they're their personal support staff and should prioritize whatever bug is afflicting them. That's simply unreasonable. @Vocalpoint makes a very valid statement when he says there are thousands of users, a lot of them in this forum, using the same set of software as those having problems, and using it successfully with no problems.
That doesn't diminish the need to discover what's happening with anomalous bugs afflicting a number of users, but in ANY professional commercial product the very nature of software development requires discipline and regimen in planning all changes to the software base code. And a lot of that regimen is about prioritization and centers around the number of people it's afflicting and NOT the one's complaining the loudest.
If you truly want a bug like that fixed your outlet is the customer support group. At least there they will have a chance to collect all the details about your specific setup which will give them a better chance of isolating what's causing it, then they can press forward with the analysis and planning to address the problem.
2
Categories
- All Categories
- 19 Welcome
- 1.3K Hangout
- 59 NI News
- 694 Tech Talks
- 3.6K Native Access
- 15K Komplete
- 1.8K Komplete General
- 3.9K Komplete Kontrol
- 5.2K Kontakt
- 1.5K Reaktor
- 349 Battery 4
- 778 Guitar Rig & FX
- 400 Massive X & Synths
- 1.1K Other Software & Hardware
- 5.2K Maschine
- 6.6K Traktor
- 6.6K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators