KUDOs On New Komplete Kontrol 3.40 2/20/25 Update

DunedinDragon
DunedinDragon Member Posts: 1,067 Guru
edited February 20 in Komplete Kontrol

I've been waiting for this one so I wasted no time in updating this release and giving it a once over as all of my projects are at least 90% KK based in Ableton Live 11 on my Windows 10 computer.

First the update in Native Access was pretty quick and simple and done in just a few minutes. I then ran KK standalone and loaded a couple of my key instruments and saved presets. No surprises there after the update and all worked well and fairly quickly and everything looked fine as far as my S88MK3 display and responsiveness.

Next I loaded up a couple of different Ableton projects that are all or mostly all KK based most with 6 to 8 various instruments. The first one took a bit of extra time while some of the tags got updated. After I tested it a bit I saved the project, loaded a new project to clear the cache, then loaded the same project to verify load time. It's definitely faster than it was, but not amazingly so, but certainly better.

I went on to test a couple of other projects and never again got the notice of tags being updated so that apparently was a one time situation related to Ableton. Pretty much the same load time, not blazingly fast, but manageable. Pretty much all of my projects contain various different instruments depending on the project along with a couple of additional plugins from other vendors such as Spitfire Audio and iZotope plugins like Neutron 5. All loaded well, no hiccups an all performed perfectly.

I didn't have the time to really check out the keyboard in detail but it all looked right and performed well. When I get more time I'll dig into that.

I just figured with all the complaints it might be nice to let you guys know there's still some of us out here that appreciate all your efforts. Good Job!!

PS: Please pass this along to your product team and let them know we appreciate their diligent efforts.

Comments

  • JesterMgee
    JesterMgee Member Posts: 3,226 Expert

    If only they could also fix long standing issues like the sub bank display problem……….!!!!!!!!!

  • david tee
    david tee Member Posts: 1 Member

    very slow. i added vst 2 wont show only vst3

  • Skijumptoes
    Skijumptoes Member Posts: 149 Advisor

    I saw you mention this elsewhere and got told to put it into a separate thread, so i looked for it, and found an older thread was closed so no longer open for discussion.

    So any idea what the deal is on this currently, i.e. Is it something they are looking into?

  • JesterMgee
    JesterMgee Member Posts: 3,226 Expert

    Yeah, this is the issue. Make a post about the problem, it gets closed so maybe I will just have to make a new post each week about it because from experience I know that if issues are not highlighted constantly, they get pushed aside and this is an issue NI created from day 1. They are aware of it, there are now several tickets in the system and last update from Matt was they have it logged but it’s low priority, I assume because it does not directly affect their own products. Could be years (or never) for a fix.

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,805 mod

    The issue is known, filed, and on the backlog, but not as high in priority as the other stuff currently in focus.

    @Skijumptoes it is also the case that @JesterMgee makes a point to hijack a great many unrelated threads (relevant only because they happen to mention KK) to remind us all that this request is not yet addressed. It's his judgement that this is an effective way to make a point.

  • Skijumptoes
    Skijumptoes Member Posts: 149 Advisor
    edited March 23

    Ok thanks, it's only a minor issue for me but I can appreciate why it's a big one for @JesterMgee given the time put into all those NKS libraries.

    I was more confused as to why he was being told to make new threads when there's existing ones that could just be kept open, surely that would prevent the need to 'hijack' threads?

    Just letting you know how it looks from a neutral perspective, I don't want to cause any trouble but as I noticed the issue I would've posted on that original thread, and was unsure what to do on the matter as didn't feel it was grand enough to make a new thread for. :)

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,805 mod

    I too can appreciate why it's an issue; it's something we intend to get to. It's something people would benefit from for sure. Time is finite, and it's not there yet.

  • JesterMgee
    JesterMgee Member Posts: 3,226 Expert

    TBF Matt, this is not some attempt at just "hijacking threads", there are issues stemming back far before you joined the team, issues which have been acknowledged, but now on top of that work in progress there are NEW issues, like threads being closed on the subject and lack of any useful info being posted on the Beta forums to even know if the issues we report are even still known about or being ignored.

    NI have had a long history of ignoring users which they have openly acknowledged numerous times and it is still an issue in some areas (granted openness on the forums is far better and you guys are commended on that front). I have been (or was) an active Beta tester for 9+ years until recently where, due to complete and utter lack of feedback/action in that program on anything outside the scope of delivery, I have pulled my input back as I don't like wasting my time. I have submitted issues, videos, repro reports and sat patiently for even some kind of "thanks for the report, we will strive to get these issues fixed", waited patiently for years for any kind of fix, doesn't seem to do any good in that department. Almost every other developer I send issues to has addressed them without issue where possible within a single update cycle. Knowing the slow pace of development and the fact importance isn't paid due to it not affecting directly NI products, I KNOW it will take years to fix even some of the most simple issues (if ever).

    So yeah, when nothing happens (and this is not just me personally, most others will just give up and move on) maybe posting a subtle dig, in applicable threads (not just in random threads) might gain traction or at least keep then topic relevant, I have to try something since nothing in the past has really worked. If it is annoying, means it is doing what I hoped it would, making the issue constantly known and hey, maybe just through frustration someone will open Visual Studio and spend the 6 minutes to code a fix, then I can move onto the next challenge as I would LOVE to not have to endlessly remind of this issue and would at least like to install v3 to test it but it's highly crippled at the moment, it's now been 1.5 years so yeah, I agree it's getting old…

    I will refrain from posting in threads and instead make a video soon of the issue and just keep it as a front page topic and post my constant requests for updates in there. Who knows, maybe this time someone can even sticky it in the "known issues" section…

Back To Top