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

2456

Answers

  • Erwinew
    Erwinew Member Posts: 73 Member
    edited March 19

    @karsai Thanks for your suggestion. Now I found the "Run as" option as you suggested (before loading the plugin).

    Unfortunately, the "Run as dedicated process" makes it even worse: The window opens in a few pixels as you can see in the screenshot below:

    REAPER_KK_run_as_dedicated_process.jpg

    When closing/reopening the Komplete Kontrol window, the window state returns to the same small window as in the screenshot. None of the "Run as" options is an improvement.

    I did not test the new KONTAKT 7 Player to give any comments. I'll keep your browser suggestions in mind.

    @rdalcroft Thanks for your suggestion. This thread is related to the original post, but I'm the firstone who posted a fully reproducible testcase. Unfortunately, nobody answered the questions from @Jeremy_NI yet, so I can imagine there was no follow-up.

    But are you running MSI Afterburner and RTSS (Riva Tuner) for monitoring Temps, ect..

    I don't have this installed.

  • Erwinew
    Erwinew Member Posts: 73 Member

    @Jeremy_NI Please find a fully reproducible testcase below with the information you requested earlier:

    I've upgraded REAPER 6.8.1 to 7.11 and purchased a license a couple of days ago. Now I discovered that Native Instruments Komplete Kontrol 3.2.0 VST3 freezes the REAPER GUI in a matter of seconds/minutes. See screen capture below.

    Easy to reproduce:

    1. Create a new project + new track and load FX Komplete Kontrol 3.2.0
    2. Load Analog Dreams and select preset "1984"
    3. Move a few buttons in Analog Dreams
    4. Select the track volume knob to switch Komplete Kontrol window focus to REAPER
    5. REAPER GUI completely frozen -> "Close the program" like "End Task REAPER"

    Project is not saved and lost!

    Note: "Analog Dreams" always freezes REAPER and is 100% reproducible. Other effects like some piano's may or may not reproduce this problem.

    Most of the times after loosing focus of the Komplete Kontrol window and switching back to REAPER:

    • Windows 10 Professional, latest 22h2 updates installed
    • REAPER 6.8.1 -> Not reproducible with clean portable edition
    • REAPER 7.11 -> Fully reproducible with clean portable edition
    • Native Instruments Hardware Connection Service: 1.5.5
    • Native Instruments Komplete Kontrol 3.2.0 VST3 in REAPER: Problem
    • Native Instruments Komplete Kontrol 3.2.0 native host application: Not reproducible
    • Native Instruments Kontakt 7.8.1 Player: Not reproducible
    • Native Instruments Kontakt 6.8.0 Full: Installed, but not tested
    • Reproducible without a USB/MIDI keyboard connected to the PC
    • Not reproducible with other DAW's, so this seems to be a major issue in REAPER 7.


    Komplete Kontrol 3.2.0 release notes:

    Cubase Flicker And Crash When Focusing On Another App and Back Again

    Maybe this issue is also applicable for REAPER.


    Already reported by multiple users in November 2023 on different forums, like:

    before loading Komplete Kontrol as a track FX, if you set "run as" either a dedicated process or separate process, Komplete Kontrol / Kontakt 7 instruments seem stable.

    None of the "Run as" options work in REAPER 7.

    Untitled Image


  • karsai
    karsai Member Posts: 50 Member
    edited March 19

    hi

    Run as dedicated process in reaper 7: That small pic is normal, it indicates the process is on, but it should come up a textbox saying click here to see the GUI and when you click it, the instrument will open in a separate window. SOmetimes it is not open but it is on the bottom of the screen in the taskbar closed, so you have to click it to open it

    Sometimes it is open behind the reaper window so you cannot see it until you go there.

    If none of these apply I have no more ideas. I wish you luck, maybe the NI people can have some ideas.

    Istvan

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 13,047 mod

    @Erwinew Thanks for the detailed repro. It turns out the bug was already reported and filed under this reference: KBDSW-7859. It's been forwarded to the developers.

  • Erwinew
    Erwinew Member Posts: 73 Member

    @Jeremy_NI Thank you very much for your reply. I look forward to a fixed version.

  • Erwinew
    Erwinew Member Posts: 73 Member

    Not fixed in updated Komplete Kontrol 3.2.1. Still waiting for a fix.

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 13,047 mod

    Bug still under investigation.

  • blitze
    blitze Member Posts: 19 Member

    Just adding my 2 cents.

    Have Massive X, Diva, Hive and Zebra freezing Reaper when run through Komplete Kontrol. For Massive X it seems to be a 5 minute time out thing but for the U-he VSTi's is can be tweaking the synths via their interface or doing a scaling change of their UI. Notes still play but Reaper freezes and requires termination. KK can be run as a seperate process or dedicated process but automatic or native process is a no go.

    All VSTi's are fine as stand alone plugins in Reaper outside of Komplete Kontrol. Using x64 VST3 plugins version. Windows 11 Pro with Reaper x64 v7.14

  • Erwinew
    Erwinew Member Posts: 73 Member

    KK can be run as a separate process or dedicated process but automatic or native process is a no go.

    Correct: Major issues when running KK as `Separate process`:

    1. The KK window size is lost after opening/closing the KK window.
    2. Real time response of all VU meters decreases dramatically.
    3. Increases CPU and graphics load.

    All VSTi's are fine as stand alone plugins in Reaper outside of Komplete Kontrol. Using x64 VST3 plugins version. Windows 11 Pro with Reaper x64 v7.14

    Correct: The issue is confirmed and located in KK and not REAPER or VST3 plugins. Only Native Instruments can fix this.

  • Erwinew
    Erwinew Member Posts: 73 Member
    https://community.native-instruments.com/discussion/comment/145106#Comment_145106

    Is there any progress with fixing this annoying issue?

  • Erwinew
    Erwinew Member Posts: 73 Member
    edited June 8

    @Matthew_NI We're still waiting for an update on this known bug reported since November last year.

    When can we expect an updated Komplete Kontrol to work with REAPER 7?

  • Erwinew
    Erwinew Member Posts: 73 Member
    edited June 10

    @Jeremy_NI Can you help us further to fix this bug in Komplete Kontrol which crashes REAPER? How can I contact Native Instruments support?

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 13,047 mod

    @Erwinew If it's the bug mentioned here (KBDSW-7859) the bug is already filed, it's now in the hands of the developers, support can't be of more help unfortunately. It's still in their backlog, no ETA for a fix at the moment.

    For any other query or support request regarding Komplete Kontrol, that would be the link: https://bit.ly/NI_support_Kontrol

  • Erwinew
    Erwinew Member Posts: 73 Member

    @Jeremy_NI Thanks for keeping track of this bug. Can you ask the product owner to raise priority to release a fix? Crashing a DAW is a critical issue and I encounter this daily since I purchased the S88.

    Thanks.

  • BIF
    BIF Member Posts: 987 Guru
    https://community.native-instruments.com/discussion/comment/159010#Comment_159010

    It's pretty much "all hands on deck" for the MIDI Templates fix right now.

    "Raise Priority" maybe can't be done until MIDI Templates update hits general availability. Maybe at that time, some team members can be freed up to do other things.

    My commendation for a really well-documented issue, though. That's always helpful. But they probably just need time away from the big issue (MIDI Templates fix) in order to be able to peel off some team members to work other issues.

Back To Top

Categories