This is a free update to registered Kontakt 5 users. The update see the change of the 'add library' button renamed to 'manage library', which allows easy access to the Native Access application.ĥ.7.0 update fixes the issue of Kontakt crashing when attempting to duplicate a track within certain DAWs. $ENGINE_PAR_INTMOD_SUBTYPE would not workĢ1st September 2017: Kontakt + Kontakt Player Update V5.7.0.FIXED, nstruments created from scratch would not appear in the Maschine and Komplete Kontrol Library browsers.FIXED, Kontakt would crash when trying to load NKIs with too many automation assignments.FIXED, Kontakt 5.7.0 would crash when clicking the FX Engine button on EXHALE by Output.FIXED, Kontakt 5.7.0 would crash when loading Electro-Acoustic by Soniccouture.Don't expect it to ever happen.26th October: Kontakt + Kontakt Player Update V5.7.1
You are not considering how NI's databases are structured, the product pipelines, the differences between authorization schemes used throughout the last 24 years that NI has existed, that there were two or three different authorization tools used each with their own idiosyncrasies, that there are two different serial number schemes in play (any older product doesn't recognize the NA serials with letters).
It's not a new effect that requires CPU for calculating its DSP.Īlso I find it laughable that you think there's only one line of code supposed to enable this license backporting that you want. For instance, user zones implementation has nothing to do with CPU load, it is regarding how things can be dynamically mapped in the instrument through user interaction. Also, not all new features add to CPU load. Libraries that don't employ those new features have exactly the same performance as they had in previous versions. It depends on those new features being used at all in the first place. K6.2 has new features, yes, but that doesn't mean that it uses more CPU by default.
It is not at all uncommon to find the same situation elsewhere in IT world where separate major versions require separate licenses and having just the latest one does NOT enable you to use the older major versions. It's not about "lazy programmers" it's about how NI as a company decides to license their products. So, where is problem to add another row - if (user have licenced Kontakt) allow use any older version. See? In a one version there already is this comparison - if (the main number of version is the same as for licence) then allow using installed version. Yes, anybody can ignore updates and stay on first version of K6. For example, K 6.1 runs quite good, but K 6.2 have new features and of course it needs more CPU power. In NI case it's not possible and to have all running smoothly, we should buy new resources. Now if newest Cubase don't satisfy or is too hard for current resources, we can use older version that nicely fits in setup. They do that since the very beginning and it is worth it to do that. Was it so difficult to implement this feature in a world's best DAW? I don't believe. Not more! Any difficulty in development is made by lazy programmers. If (current user licence is for K6) then allow using K5. I am programmer and there should be only one row in code: I just like that anything asked is going to reduce to "not impossible".
At least one person understand this situation correctly.