Question about 'Import Content' GUI/Kontakt 7 issues & features

Shutara

Hi,

I believe this hadn't been emphasized enough, but I've got some serious personal issues with how you decided to handle the Import Content section of Kontakt, and i'm shocked that this was not addressed (unless it was in Kontakt 8, but for now I see no point paying for such irrelevant upgrade compared to the state of K7, sorry). Anyway, back to the topic:

• why can't I expand this list but have to scroll this tiny window, that can't even allow for 4 rows at once? You literally have 50% of the window wasted by spacing out the content unreasonably.
  

Had I more time to play with this, I bet with little effort the UI could be redesigned to allow for more clear view and more functionality alongside, instead of a "clean UI" that serves little purpose and wastes lots of space. Hope you can see it the same way I do. And for the love of God, if not changing the UI itself, why not allowing us to scale it up at least 0,25-0,5 to allow more libraries to be seen. We can't use Kontakt's background when this window is open anyway. Anyway…

• Multiple times I have come across the issue below, and I literally had no said path on that list (which is a pain to look through if you have - guess what - more than 4 libraries).

In the current state, handling 3rd party libraries is sometimes just pure frustration.

• Each time after you open new Kontakt instance, it resets the default path you start with, when trying to add a new custom library, making users navigate back to where they store their libraries, wasting additional seconds. How is this user friendly?

Ending on a more hopeful note:

• when will we be able to use custom tags/groups for presets, not just "favorite"? Like…there are over 20k presets in my library, how am I supposed to flawlessly switch between working on different projects where I spend most of my time scrolling through presets instead of building my own categorization, not just having 100s of favorites that only partially alleviate this problem?

There's probably much more I'd like to address, but I don't want to derail this topic any more than necessary. I'd appreciate acknowledging this and hopefully putting more effort on the UX in the following years, instead of jamming in more automation-based tools, which need of existence is rather debatable.

I don't know how much you care about your customers at this point, but it's saddening to see almost no meaningful development in the software other than new libraries and paid updates on top of already buggy/unoptimized software.

If you're still reading it - Thank you and kindest regards from just another user that feels let down with the road NI has taken after the acquisition.