Kontakt 7 VST3 only shows in Ableton Natively on Silicon, and is missing from plugin list on Rosetta

Jeremymatthew11 · 2024-12-10T18:28:46+00:00

There was an error rendering this rich post.

Hello,

After migrating from an Intel MacBook Pro 2019 to a Mac Studio M2 Ultra, I am having an issue where the Kontakt 7 VST3 is missing from the plugin list in my DAW in Rosetta/Intel launch mode.

The plugin does not appear in Ableton, and any session launched from the past results in Kontakt 7 not being found - breaking all my previous sessions with Kontakt 7 instruments.

I did discover one work around that is very inconvenient, which makes me feel like there must be another way.

If I take the Kontakt 7.vst3 file that was installed on my MacBook Pro (previous computer) before migration and drop this VST3 into Custom VST3 Folder in my User Library of my new computer (meaning, I have both the latest copy of Kontakt 7 installed from Native Access 2 while also having my old computer's Kontakt 7 in a custom vst3 folder), and I tell Ableton to scan BOTH Vst3 folders (ie the custom and the system vst3 folders), then I am able to get Ableton to show the VST3 in the sidebar when in Rosetta mode. This seems really odd and makes me think that the Apple Silicon version of Native Access 2 installs a Kontakt 7 that only works natively.

Things to know/have tried:

I am running Mac OS Ventura, and I am fully updated on Kontakt, Native Access 2, and Ableton.
I have tried every method of rescanning plugins imaginable including deep scans and custom folders.
I have tried reinstalling Kontakt 7 and Native Access.

I hope someone has a solution, and thanks for your help!

Find more posts tagged with

Ableton

VST3

Kontakt 7

Accepted answers

All comments

Jeremymatthew11

I also just want to add that the reason why my workaround involves putting the old Kontakt 7.vst3 in a custom folder is so that it doesn't overwrite the new Kontakt 7.vst3 as they both have the same file name and I don't want to mix them up.

Jeremy_NI

Hey Jeremy, I have tried to reproduce the issue on a M1 with Ventura. It took a while to rescan all the plug-ins but the Kontakt VST3 is showing in Ableton Live 12 when in Rosetta mode. Are you also on 12 or is it version 11?

While the scan was running, the Kontakt 7 VST3 did not show for a while but after the full scan I switched off and back on the AU v2, AU v3, VST2 and VST3 folders, it was then showing up. I'm not sure if the switching off and on had a real impact or if it was just me being in the wrong view or wrong tag selected for the plug-ins in Ableton. This was done by sticking to the default plug-in folders.

So please give this a try, maybe only activate VST3 plug-ins for a start and do the following:

Make sure to give full disk access to Kontakt 7 and Ableton: How to Enable Full Disk Access on macOS

Keep your old VST3 file somewhere else on your computer.

Delete the VST3 file found in the default folder

Open Ableton, close Ableton

Reinstall Kontakt 7 with Native Access.

Open Kontakt 7 in standalone

Open Ableton

Click ALT+ the Rescan button up there, it will force a full rescan of Ableton.

Any progress?

Jeremymatthew11

Thanks @Jeremy_NI - it's funny. Whenever I have a Native Instruments issue, I always see your solutions on the forums - so you've helped me a lot in the past! Thanks for that!

Regarding this particular case, I am on Mac OS Ventura, have the latest Kontakt 7 installed, running Ableton 12. I have tried those things you mention, and it doesn't seem to make a difference. Full disk access is granted in System Prefs, and I've done deep scans. Still, the only way for Kontakt 7 to show up in for me in Ableton Rosetta mode is to put in the old Intel-based vst3 for Kontakt 7 from Time Machine into my system. Really strange, right?

This to me would have to indicate that Ableton is successfully rescanning (as kontakt 7 old version appears when I rescan), and that the issue itself has something to do with the Kontakt 7.vst3 file. However, I've of course re-installed using Native Access 2, so it couldn't be a corrupt vst3 file … (unless Native Access 2 doesn't replace the vst3 when reinstalling?)

Below is a screenshot of Ableton in Rosetta mode, which doesn't show Kontakt 7 VST's - only the AU. (Unless I drag in the old VST3 as explained prior)

Best ,

Also Jeremy

Jeremy_NI

@Jeremymatthew11 I'm glad that I could be of help! On this one, I'm just scratching my head…I've contacted you by email, my colleagues will need to have a deepper look in your system.

Christophe D

Hello,
I have a somewhat similar problem with Kontakt 7 VST3 which does not display in Ableton Live 12 Natively on Silicon, and is absent from the plugins list. On the other hand, it displays and works perfectly in Ableton Live 11.

What you need to know/have tried:
- I'm running Mac OS Ventura 13.7.2 on Apple M2 Max, and have updated Kontakt (7.10.7), Native Access (3.17.0) and Ableton (12.1.10).
- I tried all methods of rescanning plugins, including deep scans (Rescan + Option).
- I reinstalled Kontakt 7 and Native Access.

I will contact Native Instruments support and hope for a very quick response.

Christophe

Jeremymatthew11

@Jeremy_NI I found another lol - I'm relieved to know I'm not crazy haha

Jeremy_NI

https://community.native-instruments.com/discussion/comment/213507#Comment_213507

Let's see, I was checking your ticket, it seems you never got back to my colleague, his last reply was from December 17th.

brms87

Hi, I've had this same problem!
-Kontakt 8 vst3 doesn't show in the list, only AU.
-When (deep) rescanning plugins, I see Kontakt 8 vst3 appearing down in the screen as being scanned.
-However still it doesn't appear in the list.

A few months ago I discovered the workaround of putting the vst3 in another custom folder, and then it got recognized. But something weird happened with all my plugins yesterday (they randomly were put in the trash, another crazy thing), and suddenly this workaround didn't work anymore.

Not matter what I try now, Kontakt 8 vst3 won't be visible in the plugin list, even though I can see it is being scanned.

I hope someone can help..?

PoorFellow

https://community.native-instruments.com/discussion/comment/224162#Comment_224162

What sometimes helps people in a situation like this is to move the Kontakt plugins out of scanner range and then eventually reset the DAW to do a completely new plugin scan and then close/reopen DAW and close again then move the Kontakt plugin back to the VST3 folder in scanner range again then open DAW again to see if it can see plugin .

Jeremy_NI

https://community.native-instruments.com/discussion/comment/224162#Comment_224162

And Kontakt 8 in standalone is fully functional?

Have you tried to reset Kontakt's database, as shown here: Kontakt Crashes

Quick links

Unanswered questions