Kontakt7 vs Kontakt 6 has nothing new to offer. Yes version 7 brings some new libraries, but other than that (and Library selection panel, which nobody really cares about) it has almost nothing new to offer.
Now - let's get to the major reason for this post header.
1) KONTAKT resides on super ancient technology and libraries which make implementing new features almost impossible.
2) KONTAKT still uses super unreliable SQLite database (which should be avoided for modern software at any cost)
3) KONTAKT uses raster fonts and raster images. None of them are salable and that creates tons and tons of problems with implementing Kontakt plugin GUI. There is practical no scalability. 90% of Kontakt libraries are unreadable on high resolution screens. They especially become completely useless on 4K monitors, because everything is to small to read and use.
5) Kontakt has no customization of fonts or colors ! It is hard to believe that in XXI-st century somebody would try to sell a software without a y least this basic customization.
On top of that default Kontakt color scheme is dark and hard to read. The MENU system looks like it is designed for Windows-95.
4) Kontakt has been embedded into Komplete Kontrol which is like stacking Russian Dolls (one into another). While Russian Dolls are super cute, this method of implementing software for KK devices (keyboards) is super poor, inconvenient, unreliable. It uses extra drive space, RAM and most of all adds unnecessary complexity and more points of failure.
5) Library implementation for vendors who paid NI Kontakt license and those who do not is also super inconvenient for the user. Why the user has to deal with two locations for the Kontakt libraries (not just one) ?
6) For some users internal Kontakt editor might be useful, but these days most users use DAW's for music production end editing. Internal Kontakt functionality for editing samples, etc is nice to have but not crucial and because of the super old and inconvenient interface most users use it only ins situations when certain minimal adjustments to the library is needed.
7) This topic has been discussed hundreds of times and for the last few years I do not see even one sentence or statement mentioning serious Kontakt improvements from NI.
For me as an average user (I spent only 50% of my time on a music production) KONTAKT becomes less and less usable. I am at the point where I am not going to upgrade my Komplete Kontrol libraries, because I tend to avoid Kontakt when I can. The simple reason is usability. The major turn-off for me is the fact the Kontakt GUI on 4K screens (which I use) simply sucks !
I have purchased several libraries (i.e from Spitfire Audio) which are fantastic for their sounds but are useless for their GUI. I had to ask for a refund and it is not the developer fault. It is NI Kontakt fault! It is impossible to make right GUI for Kontakt which looks great on 4K screen as well as on 13-inch laptop. The interface does not scale and that is VEDRY SERIOUS PROBLEM ! That is the major reason that more and more people try to avoid Kontakt and Komplete Kontrol.
It very much looks like nobody at NI works with 4K screens and has no idea that this resolution becomes a standard. I use 4K monitors for myriad of other tasks and would not purchase any software which does not scale properly on my laptop and my 43" desktop screen.
That is the reason to retire KONTAKT and rebuild entire software from ground up with a new fully scaleble interface. Great examples of well designed interface could be Arturia-Pigments, products from DEVIOUS MACHINES, IZOTOPE and many more. There are very flew plugins which still fall behind modern software technology. There are hundred (if not thousands) of libraries which rely on Kontakt and as one of the leading companies NATIVE INSTRUMENTS really needs to take a quick look at their dying software.
KONTAKT MUST RETIRE
Trying to add new libraries, adding new batch chanell creation feature or upgrading Native Access does not help if the main, the most wanted features are still gone.
Kontakt in its current state must die. Continuing the old scenario is like trying to reanimate 150 years old man (while it is time for him to go,...).