Komplete Kontrol Plugins not loading
Answers
-
i DMed you to ask what you wanted screenshot of but you never responded, thats on you for not making it clear to me what you wanted screenshot the first 2 times.
0 -
The last two entries here are not required.
Not sure why they are there.Drop them and rescan. And confirm that your Kontakt 8.vst3 is in the second entry location.
VP
0 -
I also made two different threads for two different issues, one for Komplete kontrol and one for maschine. as those are two separate programs.
0 -
Kontakt 8.vst3 is indeed in the secondary location, scanned, and still same issue persists.
0 -
The issue is clearly the same if your plugins are where they are supposed to be - yet are not showing up.
Saw something similar here a few weeks back and it ended up being Sequoia holding up the show with its hard core permissions AND allowances of network access for practically every file ever installed.
You will need to get NI support on this.
VP
1 -
Sounds like typical apple not wanting users to have control lol. I contacted support on Sunday night but still no response, if i did get a response right away by NI staff i probably would've never made a post.
0 -
No support on Sunday. As long as you logged a ticket you will hear back.
VP
0 -
I was using the text support bot and it created a ticket for me (on sunday) but I never received a email confirmation or nothing like that.
0 -
That is normal. You will get an update from support when they dig into the ticket.
VP
0 -
Ah okay thank you, much appreciated for your help
0 -
have you also allowed all apps to the local network as shown here:
Iknow @PoorFellowalready posted it but maybe you missed it
0 -
Ive already seen that and made sure that everything i have is turned on for local network. sadly nothing changed, thanks for the input though :)
0 -
Okay, so, somehow I fixed it. Here's how
I moved ALL The different plugin files I have (EXCEPT for Native Instruments Plugins) in the directory
— /Library/Audio/Plug-Ins —
to a temporary location ( example: moved the different plugin folders to my desktop, Made sure not to mix the vst/vst3/au plugins all in one file, separate back-up folders )
I came to this answer out of pure luck, i asked google gemini a bunch of different questions/prompts, and the most recent answer was
———
"Isolate the Plugin Scan Issue (The "Divide and Conquer" Method):
The most effective way to pinpoint a problematic plugin or a scan issue is to temporarily remove plugins from your scan paths.
- Create a Temporary Plugin Folder: On your desktop or in your Documents, create a new folder called "VST_TEMP_DISABLED".
- Move Third-Party VSTs/AUs (Temporarily):
- Go to
Macintosh HD/Library/Audio/Plug-Ins/VST/(for VST2s) - Go to
Macintosh HD/Library/Audio/Plug-Ins/VST3/(for VST3s) - Go to
Macintosh HD/Library/Audio/Plug-Ins/Components/(for AUs) - Crucially, only move third-party (non-Native Instruments) plugins from these folders into your "VST_TEMP_DISABLED" folder. Do NOT move any Native Instruments plugin files (like Kontakt.vst3, Massive.vst, etc.) at this stage.
- Leave only the core Native Instruments VST/AU plugins in their original locations.
- Go to
- Reset Maschine/Komplete Kontrol Databases Again: Perform a fresh database reset for both Maschine and Komplete Kontrol as outlined in previous steps.
- Restart your Mac.
- Launch Maschine (Standalone): Let it perform a full scan.
- If it loads successfully and Kontakt instruments work now: This strongly indicates one of the third-party plugins you moved was causing a conflict or hanging the scan.
- Now, gradually move the third-party plugins back into their original folders, say 5-10 at a time.
- After each batch, restart Maschine (or Komplete Kontrol) and let it rescan. The point where it breaks again will identify the culprit plugin.
- Once identified, check if that plugin has a known incompatibility with your macOS version or Maschine, or if it needs an update.
- If the issue persists even with only NI plugins: This points more strongly to an issue with how Maschine or Komplete Kontrol is interacting with core NI plugins or a deeper system-level problem. Proceed to the next steps."
- If it loads successfully and Kontakt instruments work now: This strongly indicates one of the third-party plugins you moved was causing a conflict or hanging the scan.
This seemed to work for me in this instance, hope it helps someone else because ive tried to solve it for three days ( basically every-hour I wasnt sleeping or working was trying to fix this problem, what a headache ) Thank you so much to everyone who has responded to help me come to this fix.
2 -
Good - so the next question is what path do you have set for VST3 plugins in Komplete Kontrol? Obviously it should match the system VST3 plugins path. Have you run a complete plugin scan in the standalone?
0 -
It worked because essentially it has reset the plugin blacklist - this is what I would have suggested if it was certain you did have the right VST3 path setup. However there was probably no need to do 90% of the above - overkill. Just removing the offending plugins and putting them back was what probably did it.
0
Categories
- All Categories
- 18 Get started
- 1.7K Hang out
- 68 See latest news
- 896 Tech Talks
- 4.6K Native Access
- 17.9K Komplete
- 2.2K Komplete General
- 4.8K Komplete Kontrol
- 6.4K Kontakt
- 1.1K Reaktor
- 408 Battery 4
- 930 Guitar Rig & FX
- 470 Massive X & Synths
- 1.5K Other Software & Hardware
- 6.4K Maschine
- 8.2K Traktor
- 8.2K Traktor Software & Hardware
- 56 iZotope
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators