Feedback - Komplete Kontrol 3.0
Comments
-
So this may come across as a long read - but I want to be as clear as possible, and perhaps provide some tiny insight to those on this thread, which wasn't meant to be a "HEY WHAT THE F" but more feedback on some issues.
@Matt_NI Really appreciate the willingness to engage and respond - that's a big improvement on interaction with users from NI.
I also think it's fair to separate user experience from user journeys. For those that don't know what a user journey is; it's mainly utilised when desinging software. For example, a user journey might be:
"As a user, I want to delete presets in the Komplete Kontrol browser."
or
"As a user, I want to display either presets, or the plugin with the press of a button."
Using user journey's you can prioritise in development, sometimes into Must have, Nice to have, or Not essetnial. This thinking helps define how software is developed, and I will admit, apps/executables are way different to my experience- software platforms (although I work with a team who code, and I design).
Firstly, I can understand when some things are less important for different development sprints; and where they might appear in subsequent sprints. I hate sprints as a designer, but understand why they're used and for the most part, they work as intended.
I think, where Matt's hit the nail on the head here, is that we're power users on this forum. I might be quite unhappy with some of the omissions forn KK3.0, because User Journey prioritisationn has led to some poor user experience. But as power users, we might use more of what's not implemented as yet, while the average user has a great expreience.
The quesiton I would ask of @Matt_NI is what kind of interaction was had with users at the design stage? Did NI speak to the average user and power users, one of those groups, or not at all? It just feels like some of these things were easy wins to be had.
The reason I say this, is that I understand the need to bring all software, wherever possible under the same tech stack. Uniform browser experience is probbaly the biggest hurdle to developing multiple software lines in tandem, rather than in silos, as teams move from one project to the next.
At the very least, there's a lot that can be learned for an upcoming update to Maschine, where you cannot simply implement the new browser, because to do so would change the excepted norms of workflow and display from every major DAW out there.
4 -
Quite beefy - Windows 11 - Core i7, 64GB, plenty of available CPU and memory.
However, I'm guessing this might be a database issue. For the same actions in the Kontakt 7 browser, zero slowdown. In Maschine, zero slowdown. In KK, with a newly rebuilt database upon insttall, slowdown depending on the number of products in a brand category.
I only have about 50% of my libraries installed, but I've a feeling if I had all of them, it would be longer, given some of the brand investments.
I'll do a bit more testing today, and see if I can narrow anthing down.
0 -
Also still no effect version which is getting silly really - how are we supposed to be using fx without actually being able to use them as a fx or even automate them in a DAW - in practice this means if you want to use fx in KK you always have to record directly to audio
3 -
Everything the OP mentioned. I'm still looking at the library through a pinhole. Really, really disappointed.
0 -
Not yet, apparently, but confirmed as planned in the AMA. This is a gamechanger, for me.
1 -
I've had a positive thought on this fiasco.
Kore 1 -remember what happened?...it too was an unmitigated disaster and NI turned it completely around. They basically withdrew Kore 1 software totally and then came up with Kore 2, one of the greatest software they have ever made.
So NI, have the humilty to withdraw and try again.
2 -
Yeah would be for me too - long awaited - hopefully not as long for it to happen
1 -
Is there away to get back to 2.9 SW version?
I using REAPER, Ryzen 9 (last gen), 64gb ram DDR5, 4tb SSD, never got any issues with KK SW 2.
Yesterday I update it to 3.0 and it crashes ALL my projects, no matter if I use 1 instance or 50 instances of plugin.
I run some tests, with a blank project and discover KK 3.0 it just can't handle any Arturia Synths without crashing!
Sometimes it crashes even with only NI plugins
Standalone KK 3.0 not having problems, but when I load a synth inside VST3 version, it's crashing REAPER about 1 or 2 minutes of browsing and selecting presets...
2 -
Yep I have this issue as well
0 -
"Is there away to get back to 2.9 SW version?"
See here:
Komplete Kontrol S series MK1 keyboards End Of Life — Community (native-instruments.com)
Cheers
VP
4 -
Links to 2.9.4 are at the top of this thread
1 -
Thanks to both you and @Vocalpoint Up 'n' running like nothing happened ;)
2 -
Thanks a lot, revert to 2.9.4 😈
1 -
Ad Hominem and misleading comments are never helpful. Matt is not, in my opinion, "smooth talking". Throughout theses threads he has been polite and professional. I am happily using KK3.00 with no problems whatsoever.
0
Categories
- All Categories
- 18 Welcome
- 991 Hangout
- 56 NI News
- 494 Tech Talks
- 2.6K Native Access
- 12K Komplete
- 1.4K Komplete General
- 3.1K Komplete Kontrol
- 4.1K Kontakt
- 1.4K Reaktor
- 307 Battery 4
- 639 Guitar Rig & FX
- 331 Massive X & Synths
- 800 Other Software & Hardware
- 4.2K Maschine
- 4.9K Traktor
- 4.9K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators