Kontakt 6 and 7 player not showing up in Pro Tools

I've seen this question asked a few places, but none of the solutions I can find seem to work for me. Hoping to get some help specific to my system. I just can't seem to get Kontakt to show up in the Pro Tools plugin list.

I'm running Pro Tools Ultimate 2023.9 on MacOS 11.4 with an Intel Core i7. Kontakt 6 and 7 both work as standalone and in Ableton 11 for me. It's just the free Kontakt player, as I'm trying to test the sampler with my workflow before buying more packs and whatnot.

I've ensured that the aax plugins are in the correct folder (Application Support > Avid > Audio > Plug-ins), I've given the NI products and Pro Tools full disk access, reinstalled multiple times, even tried it with a different version of Pro Tools (2021), and nothing works. I've tried literally every tip I've found online when others ask this question. Native Instruments doesn't show up in the plugin "manufacturer" list in Pro Tools, and Kontakt isn't anywhere in the plugin list. I've tried Instrument tracks, stereo and mono, and just about every other type of track just to make sure. At a loss at this point. Any other help or troubleshooting tips would be greatly appreciated.

Thank you!

Find more posts tagged with

Pro Tools

Kontakt Player

Accepted answers

sound_wayv

@Jeremy_NI @PoorFellow

Hey, I wanted to give you guys an update here. After beating my head against the wall I finally found a solution and it was different than anything I could find on the internet. I found that for some reason my system had two "Plug-Ins" folders. One in the normal "Library > Application Support > Avid > Audio" directory, and one in my "MacHD > Applications" folder. I saw that Kontakt was missing from only the "MacHD > Applications > Plug-Ins" folder, so I simply copied the aax plugin over and it popped up and works great as a Pro Tools insert now. No clue how that folder got created, but that was the fix.

All comments

PoorFellow

Sorry , I don't have much help to offer here myself and I am not sure exactly how to read the Avid charts with respect to other versions than specific mentioned but maybe you do ? , did you check the : Avid Knowledge Base - Pro Tools Operating System Compatibility Chart ?

Also did you try the Resetting the Pro Tools AAX cache on macOS ?

Quit Pro Tools.
In the Finder, press ⇧⌘G, or choose Go > Go to Folder in the menu bar.
Copy-paste the following path, then hit Enter:
~/Library/Preferences/Avid/Pro Tools/
Locate and manually delete the InstalledAAXPlugIns file.
Relaunch Pro Tools to start a full plug-in rescan.

Else I don't really have much notes on Pro Tools , so I will ask if N.I. Customer Care Mac expert @Jeremy_NI , could you please take a look at this ?

(Jeremy will not be here before Monday or later)

How to Enable Full Disk Access on macOS

Notes on Network Drives and Disk Formats

Compatibility of Native Instruments Products on macOS :

macOS 11 (Big Sur) compatibility
Kontakt 6 from 6.5.0 to latest (6.8.0)
Kontakt 7 from 7.0.11 to 7.8.1

sound_wayv

Thanks for the response. Unfortunately resetting the cache didn't work.

Jeremy_NI

@sound_wayv Please try the following.

Close Pro Tools

Delete the Kontakt plug-ins from this location: Mac HD > Library > Application Support > Avid > Audio > Plug-Ins

Open Pro Tools. Close it again.

Install Kontakt in Native Access.

Open Pro Tools. Did that fix the issue?

sound_wayv

Hi Jeremy, I tried that and it did not work. I'm also in contact (pun) with the support team and just sent over the support tool test. I'm happy to try any other ideas here, and I'll keep you updated if a solution is found with the support team.

sound_wayv

@Jeremy_NI @PoorFellow

PoorFellow

https://community.native-instruments.com/discussion/comment/192176#Comment_192176

Hey, I wanted to give you guys an update here. After beating my head against the wall I finally found a solution and it was different than anything I could find on the internet.

Great that you managed to fix the problem and thank you very much for sharing what were the solution. 🙂

I know only little about Mac but it sounds to me as this has to do with having upgraded the OS at some point or from having used some user settings. I am sure that Jeremy_NI is much more capable than I with respect to assessing the root cause 🙂

Quick links

Unanswered questions