macOS M1: kontakt 6 crashes reaper

Dendriloquist · 2022-02-24T11:30:57+00:00

There was an error rendering this rich post.

Hello there,

I'm using the new macbook pro 16" m1 pro on the macOS Monterey.

Always when I open Kontakt 6 in Reaper, it crashes Reaper. No matter if I use Reaper(intel/rosetta mode) or Reaper(ARM).

Also now I can't even open the standalone Kontakt 6 app.

Is anyone else experiencing this?

Find more posts tagged with

Kontakt 6

Apple Silicon

Reaper

Comments

Jeremy_NI

Hey @Dendriloquist It happens for a few users. Could you post this file here ? The Kontakt team would like to look into it.

Mac: /Users/<your home folder>/Library/Application Support/Native Instruments/Kontakt/Db/kontaktdb2_56

Once you posted it, please delete it and launch Kontakt in standalone. It should rebuild it's database and then it should work.

Dendriloquist

https://community.native-instruments.com/discussion/comment/7145#Comment_7145

Hey Jeremy,

thanks for a really fast response!

so here is the file:

kontakt6_stinni.zip

there was also a kontatkdb2_56Lock, I put that with also in the zip file.

let me know if I should post this differently to ya.

Cheers for the help!

EvilDragon

Thanks for the file! You can now safely delete it and try running Kontakt again (it should work then)!

sevdahbaby

Hey, I am having problems with Kontakt 6.7 in Cubase 11 and Komplete Kontrol too - if I play a lot of notes on Grandeur piano with sustain pedal on, I get occasional clicks and eventually, KK and Cubase crash.

This doesn't happen in Kontakt standalone, I guess it runs natively on M1 when in standalone, and in Rosetta as a VST?

Here is my kontaktdb2_56 file:

kontaktdb2_56.zip

Best,

Milan

EvilDragon

Ah, the database file doesn't matter in your case. You at least have Kontakt running - your issue is unrelated to this one since it happens while Kontakt is running. This issue is about Kontakt not even being able to start.

Jeremy_NI

https://community.native-instruments.com/discussion/comment/7250#Comment_7250

AS @EvilDragon said, your issue is different, yhu should get in touch with our support agents here: http://bit.ly/NIsupport_kontakt

Quick links

Unanswered questions