Can't import samples in Kontakt when in Logic (on a M3 Mac)

maxfieldwh

Hi, I just installed Kontakt 7.7.3 on a brand new Macbook M3 on OS 14.1. Have been using Kontakt for years and am very familiar with Kontakt 7. I have granted full disk access to Kontakt 7/Logic Pro/Native Access/Daemon etc. I started my first new session with my typical workflow and couldn't import samples into Kontakt. I drag from my desktop or from the audio bin within Logic into the Kontakt mapping editor and nothing goes into the instrument or causes the creation of a new instrument. The usual little green circle with the plus sign in the middle never appears. I've tried aif/wav/mp3 so it's not the file type. At a total loss and afraid it has something to do with the M3 processor or some hardware issue since it's a fairly new machine. Any help appreciated!

Jeremy_NI

@maxfieldwh Little update. We couldn't reproduce the issue with a M1 on Sonoma. It seems the issue is not only tied to Sonoma but probably due to the new M3 chip (or a mixture of both). We don't have a M3 at the moment to test, we should get one soon and will investigate. FYI, We had some issues in the past with other M processors and these were fixed by Apple with OS updates.

maxfieldwh

One more data point: I CAN import samples as expected if I run Kontakt 7 as a standalone app. So it seems to have something to do with the way it interfaces with Logic. Anyone have any thoughts on this?

Jeremy_NI

@maxfieldwh We couldn't reproduce the issue with a M1 Mac. We've seen a few issues popping up with M3 processors and MacOS Sonoma with Kontakt and permissions. We don't have a M3 to test yet. I guess the best would be to make your instruments in Kontakt in standalone until we know more about the issue and Kontakt 7 is officially supported on Sonoma.

maxfieldwh

Ok, makes sense though a bit disappointing. How long would you expect it to be before there's official Sonoma compatibility?

Jeremy_NI

@maxfieldwh Little update. We couldn't reproduce the issue with a M1 on Sonoma. It seems the issue is not only tied to Sonoma but probably due to the new M3 chip (or a mixture of both). We don't have a M3 at the moment to test, we should get one soon and will investigate. FYI, We had some issues in the past with other M processors and these were fixed by Apple with OS updates.

maxfieldwh

Ok got it, thanks!