Komplete Kontrol 3 - Slow previews (KBDSW-7936)
Answers
-
My old Mac Pro is well configured, thank you :)
It is still quite powerful and very stable, besides I regret that macOs 12 is gradually abandoned by NI in many of its new updates (except for traktor pro 4, thank you, but that is not the subject here). I do not intend to replace it before it burns and dies, but I am used to work on "old" OSes and to freeze a perfectly stable configuration for my needs. I say this because this KK 3.3 has probably broken this stability (at least for me).I do not see the connection between your Windows / Ableton 11 and my macOS / Ableton 12. Different systems, different versions..
I insist on the fact that before KK 3.3.3, I never encountered any stability problem or slowdowns on Ableton 10 / 11 / 12 for years with KK 2 and KK 3 before 3.3 updates.
I think it's mostly an optimization issue on the NI side.
Since I downgraded to 3.2.1, I no longer have the bad slow KK browsing experience (which was the same with S49mk2 or with the mouse or keyboard navigation only) BUT I also realized that Ableton 12 (and version 11 that I just tested too) is way more faster in general, when opening/working with multiple KK instances, when switching tracks, or whatever, I no longer have slowdowns or big CPU spikes for simple tasks in my projects like I had with 3.3.My Mac heats up much less, the fan runs slower, in short everything is smoother for me with 3.2.1, so I stick with this version.
0 -
Is anyone of NI able to respond to the slowness issues of komplete kontrol? Is it a known issue? Will it be solved in the next update? Please repond!
0 -
I just tested with Kontakt 7 on my library, this tool works really fine is really fast, just as I expect Komplete Kontrol to react. This comparison proves the responce problem is definitely in de Komplet Kontrol software itself.
0 -
Hi @Jeremy_NI any update bug fix release been 4 months since this was last reported.. i use in Cubase 14 and so slow..
0 -
The fact this thread has a ticket number attached, and NI responded in the previous page that this is confirmed and logged would suggest yes, this is a know issue and I am sure they will/are looking into it.
Just because an issue is confirmed doesn't always mean they can fix it immediately and as their track record has shown when it comes to fixing certain issues (especially issues that don't affect thousands/millions of users) it can take considerable time to address…. if you are lucky.
2 -
I would like to encourage anyone having this issue to post here some details about the system used, like the operating system, komplete kontrol version, daw (or standalone), and amount of presets available. This may be helpful to identify similarities.
0 -
KK version 3.3.4 has been released.
Anyone verified if there are any improvements regarding browsing previews?
0 -
Doesn't appear to be fixed. Smh.
0 -
Hi @Jeremy_NI!
Do you have any updates?0 -
Just downloaded the new Komplete Kontrol version 3.3.4. The response when browsing the presents is now even worse than before. Is now 2 seconds per preset between selecting the preset and hearing the preset sound! Komplete Komplete Kontrol is komplete useless at the moment. I hope NI will take this problem seriously now. I am now forced to switch to other software to be able to select presets for my music designs in a smooth way. That can't be NI's intention.
0 -
@Don Neo KK version 2.9.6 and 3.2.1 has been reported to work. I personally run KK 2.9.6.
Anyone tried this if the legacy version still will work?
0 -
Also hard drive type. And just as useful to know where it isn’t a problem. For me this is not an issue on M1 Max, 2Tb SSD, 64GB system memory
1 -
To Be honest they have beta testers and they don't listen to what we post on the forum.. funny how no announcement of the update or bug fixes.. I'm sure there a new video coming with a new Shiney controller coming.. I bought kontrol mk3 on day one to never use it ...sad situation
0 -
It's been acknowledged as a bug but it is entirely possible the cause of the bug has not yet been identified. Bugs can be elusive when they are not happening everywhere or on a lot of systems and this one does seem very system specific, so maybe none of the beta team are experiencing it on their systems, or some are but there is as yet no clear pattern? Identifying the cause of a bug is hard where it is not happening consistently on a range of systems and where there is no clearly identifiable pattern that would help in pinning down the cause, and from there possible solutions. For example there has been speculation it is related to KK version, but certainly that is not the case for me, not could it be attributable to number of NKS presets as I probably have more than most people on this forum :) So there must be more at work than those 2 variables alone. Getting some clear data as to the hardware and software combo on affected systems is really important.
2 -
So where do we post this and/or how do one sign up for beta testing?
0
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 735 Tech Talks
- 3.9K Native Access
- 15.9K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 364 Battery 4
- 817 Guitar Rig & FX
- 416 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.5K Maschine
- 7K Traktor
- 7K 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