Using Komplete Kontrol causing my DAW (Reaper) to freeze every 5 minutes

12346»

Answers

  • cheesesteeak
    cheesesteeak Member Posts: 3 Newcomer

    You can add me to the list of Reaper v7 users with up to date NI products who is experiencing the Komplete Kontrol bug. Please fix it. I very recently bought a Kontrol S49 Mk3 keyboard that had EIGHT dead keys on it on arrival. Amazon replaced it quickly but that still was a bad experience. I've been using Kontakt for years but had never really used Komplete Kontrol before. One of the reasons I bought the S49 was to start using Komplete Kontrol. Between the keyboard and KK, my two latest NI experiences have not been fun.

  • nvaleri
    nvaleri Member Posts: 6 Member

    Pretty pretty please fix this bug! Still using KK 2.9.6. Are you just waiting until we all abandon Reaper for another DAW? 🤣 I'm on Windows and I know others on Windows are having this problem as well. Macs less so or not at all. How many of you guys are using Nvidia graphics cards? Maybe that's the issue? Would love to get some kind of workaround and move on to the new KK. Just bought Maschine 3, Kontakt 8 and GR Pro 7 and would love to have my KK interface look as tasty as those. It doesn't have to be full DAW support, it just has to not crash! Thanks.

  • Vocalpoint
    Vocalpoint Member Posts: 2,727 Expert
    edited December 1
    https://community.native-instruments.com/discussion/comment/194740#Comment_194740

    If you are still using KKv2.9.6 - you already have the best KK available. (IMHO)

    Unless you actually own a MKIII board - KKv3 is not an upgrade or a requirement. It is still buggy and still missing the feature set (standard layout, sub banks and sample Drag and Drop) of v2.9.6.

    Not to mention it's lack of stability (as you can see in this thread) and of course it's speed and ease of use.

    Just a thought.

    VP

  • nvaleri
    nvaleri Member Posts: 6 Member
    https://community.native-instruments.com/discussion/comment/194790#Comment_194790

    Lack of stability for Reaper or other DAWs as well? It seems as though if we could get some kind of workaround or define what the conflict is we could get this working. It would be ideal for the bug to be fixed but some of the issues were resolved by tweaking settings that aren't directly controlled within Reaper (running as a Separate Process, etc). I just wonder if there's some stupid setting (in an Nvidia control panel, for instance) that is causing the issue. Wouldn't be the first time. Resizing the plugin UI for Arturia plugs seemed to trigger crashes most frequently for me with KK v3.x, but now other plugs seem to be affected too, like MassiveX. So again- is it a particular build of Windows? Is it particular to Nvidia cards and drivers? I wonder what other thread participants experiences are.

  • Vocalpoint
    Vocalpoint Member Posts: 2,727 Expert
    edited December 1
    https://community.native-instruments.com/discussion/comment/194830#Comment_194830

    KKv3 has oddball issues with many DAWs - it is easy to find all sorts of posts on the boards here.

    This one however I believe is only a Reaper issue - which is still - as many prior posts in this very thread remind everyone - is not an officially supported DAW for NI. And it does not appear to affect every user.

    If I were a Reaper user - until a fix is actually deployed - I would stay on KK v2.96 and save my energy for more constructive things.

    Again - KKv3 is not a required element for anything unless you own a MKIII board - then you really have no choice.

    VP

  • nvaleri
    nvaleri Member Posts: 6 Member
    https://community.native-instruments.com/discussion/comment/194836#Comment_194836

    Don't worry I've got lots of energy to spend on unconstructive things. Thanks for your input, though!

    Anyway- I am currently running Windows 24H2 and the latest version of the Nvidia Studio driver for my RTX 3090. Does anyone have a similar configuration?

  • Vocalpoint
    Vocalpoint Member Posts: 2,727 Expert
    https://community.native-instruments.com/discussion/comment/194839#Comment_194839

    One thing that is known is that 24H2 is not really prime time yet but given that other Reaper users are having this issue and do not have 24H2 - makes it unlikely to be related.

    Not sure on any nVidia connections whatsoever.

    VP

  • nvaleri
    nvaleri Member Posts: 6 Member
    edited December 1

    The errors I'm getting in Event Viewer are:

    The description for Event ID 258 from source NIHostIntegrationAgent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    NIHIA.hwpage: MixerGenericBase::setUpProperties(): ID already exists

    The specified resource type cannot be found in the image file

    AND

    The description for Event ID 258 from source NIHostIntegrationAgent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    Server: onConnectionDropped: NIHWKompleteKontrolMK2-D20E2F9E0114

    The specified resource type cannot be found in the image file

    Maybe a red herring, who knows? I did realize that stability did improve somewhat when I do a HiDiPi override in the settings of System vs Application. But ultimately, yeah- 3.x is still unusable in Reaper. I played with antialiasing settings and some of the Advanced UI tweaks in the Reaper prefs but wasn't able to find a workaround. Oh well!

  • Erwinew
    Erwinew Member Posts: 73 Member

    How many of you guys are using Nvidia graphics cards?

    Same problem with updated KK 3.3.4 and latest REAPER on Windows 10 Pro and 11 Pro 23H2 with several different NVIDIA GeForce graphics cards and tested with latest NVIDIA drivers. Running over 100 VST3 plugins from different manufactures in our studio without any problems for many years with REAPER 6 and 7.

    Maybe that's the issue?

    REAPER crashes with all KK 3.x.x versions. We think the problem is located in the KK plugin fileKomplete Kontrol.vst3. Only NI can debug and analyze this.

  • nvaleri
    nvaleri Member Posts: 6 Member
    https://community.native-instruments.com/discussion/comment/197836#Comment_197836

    Thanks for the info re: Nvidia! It's too bad that NI has deprioritized this. They seem to misunderstand their user base pretty frequently. The non-inclusion of Maschine support on the KK MK3 boards out of the gate where they said "There just weren't enough people using the Maschine integration on the KK MK2." Now they're like "Yeah, there aren't enough Reaper users to prioritize this." Not sure how they're doing their market research but I definitely have never gotten a survey asking how I use their products. I know there's anonymous reporting but certainly doesn't seem like there's enough data to support their claims. Oh well, we'll just wait for them to fix their ******. What else can we do but complain?

  • Erwinew
    Erwinew Member Posts: 73 Member
    edited December 15

    I know there's anonymous reporting but certainly doesn't seem like there's enough data to support their claims.

    Correct. In our studio environment computers are not connected to the internet and survey is disabled for privacy reasons. NI cannot accurately know how which DAW's are used by customers as nobody asked us.

    What else can we do but complain?

    As there was no progress for more than 1 year, we decided to skip all NI Black Friday deals and ignore "free NI giveaways". We decided together with our production manager to invest in hardware and software from other competitive brands which works fine with REAPER.

    What we expect from NI: A clear table with supported features what customers can expect. As an example, Softube did an excellent job with creating this table for Console 1 which is of course fully supported in REAPER:

    https://www.softube.com/console-1-compatiblity-chart

    If there is a problem, Softube replies professionally and at least try to help as part of support.

    You can check our accounts where no new NI products were purchased this year as a result of this thread. A difficult decision, but necessary.

    @Matthew_NI Can you give us an update? Is there finally some good news to share we're still waiting for?

  • DIRK ROMBAUTS
    DIRK ROMBAUTS Member Posts: 1 Newcomer

    Same issue here. I am one of the many "victems"

    I can still run the version 2.9.6 with the MK2 but in the long run this is no solution.

    So please Native Instrument guys, solve the problem and let us make music without frustration.

    I love the keyboard ( still KK S 88 MK2) but this issues make me doubt and look for other options.

Back To Top

Categories