Some NI Libraries now updated to require Kontakt 7.6?

[EvilDragon]

All things considered, this is a fail from NI. Most developers archive older patches in a subfolder if they make drastic version changes - a perfectly neat solution. Sounds like NI have done this for some products, but not bothered for others (and we have no list of which).

Only Analog Dreams, Ethereal Earth and Hybrid Keys have a v2.0 NKI (due to a completely different internal structure, to bring them up to date with the v2.0 framework).

Others will all get overwritten patches.

The reasoning here is not to clutter Maschine/KK browsers with duplicates upon duplicates of patches. This gets especially complicated with snapshots.

[rasmusklump]

Ah, now it's the user's fault... Classic.

[zvenx]

Especially when you know you don't have the latest version of the required software.
rsp

[funky lime]

So you're just confirming that what he says is a fact and that the user needs a workaround after the update. You know not everyone using Kontakt is reading this thread or this forum right? Or should people rely on random forum people to be able to load instruments?

No, people should just read release notes and not mindlessly click Update.

yeah that's a nice idea and all (and i happen to agree wholeheartedly that people should not update without a good reason), but the case here is that people are being permanently "punished" for one small misstep and have no way of recovering from that misstep (besides buying K7, which was the ulterior motive all along i suppose). regardless of however small or first-world you might consider the "punishment," it's the principle of it that matters.

so when someone gets burned and your "NI insider" response (going by your reputation and by the fact that you sometimes refer to NI as "we") is simply to suggest that they are mindless, it's not helpful at all. it's just kicking someone while they're down.

[zvenx]

I somewhat agree with most of what you are saying, funky lime.
Whilst I do think the user who blindly clicks on update all has a personal responsibility to read the release notes before doing so, especially when they know they aren't on the latest Kontakt for instance, I think NI indeed needs to at least this one time provide a solution.

What I don't agree with is the no way of recovering part.. ED has at least twice said what that recovery solution is..
go to any project you have that you used the nki unaltered and resave it with a name that will ensure you know that is the version you will use.. like Noire Felt K6 or something...

I updated yesterday, on both mac and pc, and actually one of them warned me and offered me the option of not warning me again.. I don't remember if this was pc or mac, but both should warn me.
rsp

[funky lime]

I somewhat agree with most of what you are saying, funky lime.
Whilst I do think the user who blindly clicks on update all has a personal responsibility to read the release notes before doing so, especially when they know they aren't on the latest Kontakt for instance, I think NI indeed needs to at least this one time provide a solution.

What I don't agree with is the no way of recovering part.. ED has at least twice said what that recovery solution is..
go to any project you have that you used the nki unaltered and resave it with a name that will ensure you know that is the version you will use.. like Noire Felt K6 or something...

I updated yesterday, on both mac and pc, and actually one of them warned me and offered me the option of not warning me again.. I don't remember if this was pc or mac, but both should warn me.
rsp

yes that works if you've got that. what if someone bought Noire, a kontakt 6 library, a few days ago. and then this update dropped, making it library K7-only. and they don't have an old project?

especially when the official Noire page, as of two minutes ago, still lists the requirements as:

(Version 6.0.4 or higher)

the communication is inconsistent

[zvenx]

True...


I am curious to know which versions would a reinstall in NA, install.. No, not curious enough to try it myself because well I have Kontakt 7.
rsp

[mabian]

About the clarification requests mentioned earlier yes older projects with K6 will load even after the libraries have been updated because the project data contains the original nkis. And no, if you want to load the updated libraries for new projects inside K6 this is what won't work at all.

In other words, the updated libraries can now be used in newly opened instances of Kontakt only when Kontakt (full or player) version used to load them is >= 7.6.

- Mario

[zvenx]

Yss but ED'e request is to change this part, which is clearly nof true and if someone only reads that post and jumps in they will miss the parts where ir clearly is not true.

So, let me understand well... let's say I have some old projects with those libraries loaded in K6.

Then, If I load these projects after updating the libraries they won't open any longer in the original K6 instances hosting them in the project? I truly hope they haven't done this for real... that would be a huge shoot in the foot.

rsp

[mabian]

Yss but ED'e request is to change this part, which is clearly nof true and if someone only reads that post and jumps in they will miss the parts where ir clearly is not true.

So, let me understand well... let's say I have some old projects with those libraries loaded in K6.

Then, If I load these projects after updating the libraries they won't open any longer in the original K6 instances hosting them in the project? I truly hope they haven't done this for real... that would be a huge shoot in the foot.

rsp

Ok fair enough...I can edit the original post, doing it now...

- Mario

[Funkybot's Evil Twin]

No, people should just read release notes and not mindlessly click Update.

That's wishful thinking! Next you'll want people reading terms and conditions.

I learned a long time ago: you can't force people to read instructions/warnings and most just won't do it. Never build a process that relies on that.

[sacer]

So you're just confirming that what he says is a fact and that the user needs a workaround after the update. You know not everyone using Kontakt is reading this thread or this forum right? Or should people rely on random forum people to be able to load instruments?

No, people should just read release notes and not mindlessly click Update.

I have no bad experience if I update any other brand. In worst case, there is a bug and you can roll back, or the developer needs some time to get rid of the bug. In case of NI or Apple you should be aware, that a update can destroy a running system. It’s the same experience when apple kicks 32 bit compatibility or leaves the old intel hardware behind. A lot of paid software doesn’t work anymore. I have a windows 11 system, that never gets bothered with any incompatibility to old software.
Your message is clear - don’t buy NI when you are looking for reliable software solution.

[noiseboyuk]

Why would the library disappear from the library pane?

Ah good, so it's just (for some) unloadable nkis, not the entire library becoming invisible in K6.

The point absolutely stands though that if you are removing access for an entire Kontakt version the developer should be archiving the original nkis. If third party developers can do it, why not NI?

[noiseboyuk]

Bonus thought on the above - if you go in eyes wide open, then copy the instruments folder first somewhere, then update, then you can manually put it back in their own subfolder in instruments.

[zvenx]

Why would the library disappear from the library pane?

Ah good, so it's just (for some) unloadable nkis, not the entire library becoming invisible in K6.

The point absolutely stands though that if you are removing access for an entire Kontakt version the developer should be archiving the original nkis. If third party developers can do it, why not NI?

Now this point, I fully agree with.
rsp