Komplete Kontrol VST2 missing after 3.0.0 update

1…4567810»

Comments

  • JesterMgee
    JesterMgee Member Posts: 2,929 Expert

    Honestly, unless you have an MK3 keyboard,. just delete V3 of the KK software and stick to v2. You are really not missing much at all (likely you will find you miss much more with V3 than in V2)

    Don't think of it as a downgrade to go back to V2, KK V3 is basically a completely different application as far as I am concerned. V3 should only be installed by those using MK3 or if they are willing to sit and spend hours testing each project for compatibility. If you rely on your setup for income and value your own sanity, just stick to v2 and maybe check on things in a year or 2 when KK hopefully matures a bit.

  • MyOwnShadow
    MyOwnShadow Member Posts: 3 Member

    Very true JesterMgee!

    Then again, I will first finish and export all newer projects to 24 bit, that I made, using V3. Because I do not know if those will function after the "downgrade"... But I will see this and unless NI comes up with a working version of KK V3, I will go that path.

    Thanks a lot!

  • Lovelight
    Lovelight Member Posts: 6 Member
    edited February 29

    What would be the problem for NI if the KK 3.x would still support VST2 ? Its really a pain in the ---for all projects made before this new version, can't see any logic in this not being backward compatible.

    Imagine if this would happen with MIDI 2.0.

  • decto
    decto Member Posts: 1 Newcomer

    just wanted to leave some hate here. I mean I could have read the release nmote, maybe they would have warned me. but I just updated, opened a project and bam, all the komplete v2 tracks gone inn abnleton... polugin is missing. great job!


    I also read that sdome DAW (Cubase) are able to switch from vst2 to vst3... so could be also abletoins responsibility, any way, I'm f.... and now I gotta find out how top get my old komplete back.


    Would be nice if NI would let us know, any links in here?

  • rdalcroft
    rdalcroft Member Posts: 193 Advisor

    Just reinstall the 2.9.6 installer.

    And everything will be back to normal.

  • mykejb
    mykejb Moderator Posts: 1,693 mod

    @decto You can get the last version of Komplete with VST2 support here - Komplete Kontrol Legacy Installers for Older Operating Systems – Native Instruments (native-instruments.com)

  • rdalcroft
    rdalcroft Member Posts: 193 Advisor
    https://community.native-instruments.com/discussion/comment/137437#Comment_137437

    Yes, sorry for not linking it.. Very lazy of me...

    Thanks @mykejb

  • FilmCompos3r
    FilmCompos3r Member Posts: 29 Member

    Obviously the solution here was to structure this so that KK2 could live alongside KK3 on the same computer.

    It's a much smaller tradeoff to no longer have the keyboard sync up with KK2 instances than to not have any access whatsoever to the patches loaded in KK2 once updated to KK3.

    What a mess.

  • Lionzinio
    Lionzinio Member Posts: 119 Advisor

    This doesn't solve the issue that the S1 keyboards are no longer supported in version 3, which essentially means there is no point in upgrading if you own any of these.

  • bobbyduracel
    bobbyduracel Member Posts: 37 Member
    edited September 8

    For months I've been scouring old projects and bringing them up to date, in preparation for a computer upgrade. I noticed in MOST of my projects, almost ALL instances of KK are seemingly invisible to Ableton. It resulted in a lot of work, mostly re-opening projects in Live 11 for the full KK instances to load. I brought all of the projects up to date, replaced missing instances of KK, etc… now after the recent update I have at least one project unable to locate KK again. No other plugins are having this issue, just KK. I mean, a dozen other VST companies are in my plugin collection and literally only KK is missing. What is NI doing differently? Whatever it is, please call U-he, FabFilter, literally anyone else in the game, and ask them for some advice. This is nonsense. It wasn't just after 3.0, it's been an issue for awhile. If they cannot resolve it, the only answer (in my world) is to stop using their KK software altogether in my productions. It's useless if I cannot rely on the plugins to load in 30 days, or it requires I take extensive notes and screenshots of every instance of KK with each instrument, patch, or custom parameters chosen… to ensure I can replicate it later. And yes, I do bounce things to audio at a certain point, but the idea that I'd need to do this immediately, after my first big session with KK inside of an Ableton project… no. that's silly, right?

    I should say RAUM and a few others are also having the same issue… meaning it's a global "NI Plugins" problem in great need of a solution.

Back To Top

Categories