Kontakt 8 Plug-in Mode Interface Problem in Reaper

Soumneal · 2024-12-08T12:24:42+00:00

There was an error rendering this rich post.

Hi everyone. I recently purchased Exhale and set it up with Kontakt 8 as a plug-in on my Reaper to sound my pre-written MIDI. Worked fine for a week, but then the interface on plug-in mode opens graphically corrupted and its controls are mostly unresponsive (can select sounds on the side pane only). Standalone mode looks ok.

Tried different files, resets, new tracks etc. Other plugins (Roland Zenology Lite) work fine. Tried the article "Kontakt Crashes" as well, no change. I'm very new in computer music, would appreciate it if anyone has any idea how to solve this. Thanks.

Win 11 Home, Ryzen 9, 32GB Ram

Find more posts tagged with

Accepted answers

Soumneal

Ok, I updated my Reaper to 7.28 and seems like problem is solved now.

Thank you…

All comments

Jeremy_NI

When you open Kontakt in standalone, make sure to select an ASIO driver as output, a wrong driver selected there can sometimes give broken GUIs (I know it seems weird but it's true!)

Click on the NI logo of Kontakt when in your DAW. Is it the same version shown as in standalone?

In case that didn't help, get in touch with our support here: https://bit.ly/NI_support_kontakt

Soumneal

https://community.native-instruments.com/discussion/comment/196703#Comment_196703

Thanks Jeremy, will try and get back here.

Soumneal

https://community.native-instruments.com/discussion/comment/196703#Comment_196703

Hi again,

I select my audio interface in both. Only, when the standalone is open with the interface selected, the DAW can't find the interface. Same for the standalone if the DAW with the interface is open.

The versions are the same.

Tried this which basically says the same as interfaces, still no chance 8(

https://support.native-instruments.com/hc/en-us/articles/16302613738525-My-Kontakt-Library-Loads-with-Broken-Graphics

Kontakt reaper problem 4 standalone and reaper.png

Jeremy_NI

Please get in touch with our support.

Soumneal

Ok, I updated my Reaper to 7.28 and seems like problem is solved now.

Thank you…

Quick links

Unanswered questions