Feedback - Komplete Kontrol 3.0

Memory usage has gone up - but not to the extent that we expected it to be problematic - so if those reports persist this will be something we'll continue to look into. As mentioned elsewhere, we fixed major memory leaks during the beta process (the point of beta being to catch and prevent such things).

One precursor to a dev talks type blog post would be this: part of our tech transition involved a move to Qt (for non technical folks Qt is software tool for creating graphical user interfaces). This sets us up to continue to deliver on a lot more of the user requests our older frameworks couldn't accommodate. Qt is a little more memory intensive, wherein lies the tradeoff.

This is not something we're able to reproduce - that would be a major bug.

Could you PM me some system configuration details - I'd love to sort this out and see if we can obtain a repro on our end.

Yeah - we have other things to do first like Accessibility, Play Assist and MIDI template management on-device (K MK3 only), and assorted UI/UX improvements (continued resizing support, tagging, other things as noted in this thread). The priority of these things is not changing. They're next up.

However, beyond that, we have channel-strip improvements on our radar, which includes things like FX work. The priority of these things could change up or down.

We have a fantastic team, hard at work. Company ownership is immaterial: to make money a majority of existing and new users must be happy, and to be happy, they must enjoy using the products.

This new release has already been adopted by far more people than those who've come to offer constructive criticism (and in many cases done so simultaneously in other forums, by way of being heard). There's a lot to be said for Komplete Kontrol 3, even if it doesn't yet have everything everybody wants.

And with regards to the constructive criticism, since the thread evolves and not everyone reads everything, I'll throw some reminder / placeholders of what's come up so far:

• Topic: resizing
  • We added support for HiDPI and host content resizing as part of a major UI framework overhaul. This was the highest priority, as it benefits the most users given that KK is a host of content.
  • We're going to move on to browser resizing next. This was the second highest priority, when it came to the topic of resizing. It exists already in Kontakt, so will come to KK in due time. After this, we focus on many continued UI and UX improvements on the new framework.
• Topic: tagging within the browser
  • KK3 has less tagging capability than KK2.9. This is known. It's because as we transitioned to the new browser, not all capabilities were yet prioritized, and yet implemented. Why? Very few people use those features, so the effort up front wasn't warranted. Most users consume the presets as they are.
  • But it IS something we plan to do. It's more acute for a librarian like product such as KK, as opposed to say, Kontakt.
• Topic: drag and drop from within the browser
  • If people use samples with KK, it's most of the time to load directly with the Sampler and Audio module. Very infrequently is it to drag samples into a hosted content product (e.g. a granular sampler). The former is still possible, the latter is not, which is unquestionably a regression.
  • It's a known issue, again, as the capability has not yet migrated to the new browser due to it being a lower priority.
• Topic: memory usage
  • The new UI framework is more memory intensive. This is a net benefit, but based on some of the feedback it seems we need to continue efforts to reduce memory usage, especially for larger session formats.

Those are, I think, the biggest topics of contention.

I think it's reasonable that users who want to see more sooner on resizing, for example, or don't appreciate the regressions over 2.9, are frustrated. Their use cases are in the minority and weren't prioritized for the initial launch - something I'm being very forthcoming and transparent about, as well as the path forward. 2.9 is also available in this thread, so nothing ventured, nothing gained, but also nothing taken away.

All to say: this is far from horrible. If you have specific details, and constructive feedback, this is the forum in which to air them. If you want to complain in general terms, that doesn't really help those of us –like me– who are here to be part of the solution.