Some NI Libraries now updated to require Kontakt 7.6?

[zvenx]

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.

yep.. but to to one of my points.. If I have decided to stay at Kontakt 6, and I know they are at Kontakt 7 now... worse if I know they are now marketing nks2, the mk3 all with Kontakt 7.6 integration, I know for sure they not doing anything new for Kontakt 6 anymore.. I would not be updating libraries.
rsp

[mabian]

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?

Indeed, that could have been the solution... leaving the current NKIs as they are and deploying new ones like <libraryname>_NKS2.nki or something like that.
Maybe a bit cumbersome, but more elegantly respectful of backward compatibility (and users not willing to update or install K7 player)...

- Mario

[zvenx]

But you are taking out any self responsibility in that for your/one's decision to remain at a version that is no longer being developed.
rsp

[sacer]

I have Kontakt 7 with my Komplete 14 CE

The problem is Kontakt 6 works fine, and Kontakt 7 is buggy with xterme loading times. If it would only be a problem to update to a new major Kontakt, than wouldn’t be so frustrated.

[SLiC]

But you are taking out any self responsibility in that for your/one's decision to remain at a version that is no longer being developed.
rsp

Yes it seems fairly obvious that NIs new direction is a major release every year with very few new features but if you don’t update every year your version is obsolete and no longer supported…

[EvilDragon]

(besides buying K7, which was the ulterior motive all along i suppose)

No, that is not the ulterior motive. The motive is updating products to work with the new keyboards. This comes with certain requirements.

[EvilDragon]

Yes it seems fairly obvious that NIs new direction is a major release every year with very few new features but if you don’t update every year your version is obsolete and no longer supported…

"Very few new features"; have you actually looked at the size of changelogs from K7.0 to K7.6?

[sacer]

(besides buying K7, which was the ulterior motive all along i suppose)

No, that is not the ulterior motive. The motive is updating products to work with the new keyboards. This comes with certain requirements.

What’s the advantage of mk3 over the old mk2 Serie to destroy a running system for many users ?

[EvilDragon]

Nobody's destroying anyone's system. You're not forced to update the libraries. You decide yourself if you want to update. I think I'm done parroting this over and over now.

As for advantages, I mean all the promotional material already exists, check it out?

[sacer]

Yes it seems fairly obvious that NIs new direction is a major release every year with very few new features but if you don’t update every year your version is obsolete and no longer supported…

"Very few new features"; have you actually looked at the size of changelogs from K7.0 to K7.6?

Don’t get me wrong for my frustration, but if you would experience a loading time of 4 minutes with Kontakt 7 and Kontakt 6 needs only few seconds than you would also be frustrated.
The support had only one optimisation to delete xml files. Now Kontakt 7 takes only one minute instead of 4 minutes, but therefore I am missing many NKS libraries. But also this one minute takes 50 seconds longer than Kontakt 6.
So i don’t see not any one improvement from Kontakt 7.6 to Kontakt 6, if you have such an issue

https://community.native-instruments.co ... -launch/p1

[mabian]

"you're not forced to update" is a very weak assertion in my opinion... if you expect the user to not update in order to not break compatibility I think there's a big issue...

Seriously NI should find a better way to handle this kind of situations...

[sacer]

Nobody's destroying anyone's system. You're not forced to update the libraries. You decide yourself if you want to update. I think I'm done parroting this over and over now.

As for advantages, I mean all the promotional material already exists, check it out?

Yes I am not forced, but I have updated before reading this thread and now I can’t roll back. I have now been warned, that there will follow more librarie updates that will cause incompatibility to my system and I am now aware of these updates.
But I think you should warn your customers, it’s comparable to, we don’t offer 32 bit support or vst2 any longer. In this case, we don’t support any older Kontakt versions anymore

[EvilDragon]

Seriously NI should find a better way to handle this kind of situations...

And there eventually will be a better way to handle this, I'm sure. However NA updates run in their own schedule and roadmap and this situation could not be handled in time for release of updates. And so listing the version requirement change in the release notes is the only thing that was available to the instrument team at this point in time.

I do not disagree, this can definitely be improved. I'll make sure this reaches the right people.

[EvilDragon]

Yes I am not forced, but I have updated before reading this thread and now I can’t roll back.

What you still can do is contact support and ask for earlier version installers. Then you can roll back.

[Mace404]

Yes I am not forced, but I have updated before reading this thread and now I can’t roll back.

What you still can do is contact support and ask for earlier version installers. Then you can roll back.

If they don't expect us to just update libraries then can they make older versions public available so we can decide wich version to run? A dropdown with a version select would be lovely then.