Feedback - Komplete Kontrol 3.0

I have not said a word about wanting to alienate anyone.

I have however laid out the initial prioritization, and the things we intend to work on next.

Hopefully, people are able to read those posts of mine, and engage in a dialogue about that roadmap. The passion of our users is incredible, even when it borders on the aggression you've noted. It's why I wanted to join the team, and why I'm here now.

You're describing the differences between best and bad practices, which I agree with.

Similarly, I don't put much stock in the user surveys I've seen. What you describe as what we should have been doing is exactly what we have been doing (and only a small piece of what we've been doing).

Some things are subjective, and matters of opinion. Some things are a function of where we're headed. But overall, I do believe where we're headed to be ultimately a better place.

 I'd like to repost again a summary of the main feedback, and next steps.

• We've made a major tech transition, partly to allow for us to build more things users want (e.g. resizing)
• We have not yet brought everything forward, and where not, I've explained why (e.g. prioritize the most used features first, and then continuously improve). I don't expect that all users necessarily like the prioritization, but all deserve to hear the explanations I'm providing. We're all human, but I think there are constructive ways to exchange facts and feelings, and thank those of you who're doing so.
• The main complaints as of now are:
  • RESIZING:
    • What: we have transitioned to a UI framework that allows us to support HiDPI and resizing. We focused on supporting host content resizing, as this was the most hotly requested feature.
    • Feedback: users also want to see browser resizing, and KK shell resizing.
    • What next: we plan to take on browser resizing as a next priority (Kontakt 7 already does this). KK shell resizing remains an open question, as there are interdependencies with the host content, which itself already resizes.
  • BROWSING:
    • What: we implemented the new visual browser seen in Kontakt 7
    • Feedback: some users use the browser to organize samples they then drag/drop into hosted content (e.g. a granular sampler) and are no longer able to do so.
    • What next: we plan to add a way to import samples from the new browser into host content
  • SCANAPP:
    • Feedback: some users are reporting hangs or crashes with specific content. Note that we tested with 10s, 100s, 1000s of products, but the variables are exponential, and issues can occur.
    • What next: we will look at the bugs filed against specific reports, and also some general improvements (e.g ability to exclude from list).
  • MEMORY USAGE:
    • What: the new Qt user interface framework unlocks a lot of possibilities (some already realized, like scaling and resizing) but is more memory intensive than previous (which was fixed bitmaps).
    • Feedback: some users are reporting an increase in memory usage too great for their needs
    • What next: we will continue to profile and reduce memory where possible - this is not one specific thing, but a general effort you can look for in release notes
  • TAGGING:
    • What: we implemented the new visual browser seen in Kontakt 7
    • Feedback: since the new browser does not yet support the full user tagging workflow, people who make use of this tag editing capability (especially on behalf of preset communities) are stuck on KK 2.9 until support is added
    • What next: we plan to add tag editing capabilities and eliminate the regression in the coming months.

Note that despite my transparency, the one thing I'm not at liberty to say is exactly when each feature mentioned above (and others that crop up) will ship, just yet. But what I can say is that the browser resizing, scanapp and memory topics are things we're starting work on this year, amidst other topics specific to the new keyboard (Play Assist on device, MIDI templates on device, Accessibility support).