- #Komplete 12 ultimate instruments not showing up how to#
- #Komplete 12 ultimate instruments not showing up update#
- #Komplete 12 ultimate instruments not showing up manual#
- #Komplete 12 ultimate instruments not showing up windows 10#
- #Komplete 12 ultimate instruments not showing up windows 7#
#Komplete 12 ultimate instruments not showing up how to#
How To Build Your Own NES Classic Edition That Pla. I really hope this post saves someone the time and frustration this problem caused me. This also fixed the problem with new instances of the plugin in Live and Cubase. Load a library that was exhibiting the problem with the UI and/or keyswitches previously. (Kontakt will re-create this key with the default program settings the next time it's launched.) When you are asked if you are sure you want to permanently delete the key, click Yes. Now right-click the Kontakt 5 node and click Delete on the shortcut menu. With the Kontakt 5 node selected in the left pane of the window, select File > Export and save a backup copy of the registry contents. Launch regedit.exe and browse to this location in the registry: HKEY_CURRENT_USER\Software\Native Instruments\Kontakt 5. Make sure no instances of Kontakt are currently running, either as a stand-alone program or a plugin. So here's what I did to finally fix the problem: I had already been deleting the Kontakt-related keys under HKEY_LOCAL_MACHINE, but I had forgotten to check for anything under the user-specific portion of the registry: HKEY_CURRENT_USER! #Komplete 12 ultimate instruments not showing up manual#
On this working user profile, I ran Sysinternals Process Monitor while launching Kontakt and loading the Soniccouture instrument again, watching exactly what Kontakt 5.exe was doing- and this is when I saw it: Kontakt was using a registry subkey that I had overlooked previously, when I was doing manual post-uninstall cleanup of Kontakt.and this time it worked! Both the UI and keyswitches were now working properly! This told me it wasn't an installation problem, but rather something specific to my Windows user account. I launched Kontakt in stand-alone mode, and loaded Electro-acoustic.
#Komplete 12 ultimate instruments not showing up windows 7#
Here was the real breakthrough, though: After I switched back to Windows 7 I logged into a different user profile that I hardly ever use. I also ran Native Access to make sure all my plugins were the same version I was running in Windows 7, so this ruled out the specific version of Kontakt. #Komplete 12 ultimate instruments not showing up windows 10#
When I switched over to Windows 10 and tried loading some of the same libraries that were giving me problems on Windows 7, I found that they worked fine. I normally use Windows 7, but I have another boot partition with Windows 10, that also has Cubase and Native Instruments Komplete 11 installed.More about this in the "solution" section.) (Spoiler alert- there was ONE post-uninstall trace of the program that I was overlooking when doing this clean-up. Uninstalling/re-installing Kontakt didn't work- even if I manually cleaned up left-over registry and file traces that the uninstaller doesn't remove.
#Komplete 12 ultimate instruments not showing up update#
I installed the update but found that it did not fix my issue. I don't know exactly which version I had installed when I first hit the issue, but I checked Native Access and saw that there was an update available (5.6.8).
Updating to the latest Kontakt version didn't help. It was only when I added a new instance of Kontakt to a new or pre-existing project that the issue occurred. I even had a couple of projects that used Soniccouture Electro-Acoustic (the instrument I was using when I discovered the whole problem) which loaded and played fine. The problem only affected stand-alone mode and new instances of the Kontakt plugin in a DAW, not plugin instances that had already been saved in existing Cubase projects. Here's a quick list of things I observed over the next several days in my quest to solve the problem. It wouldn't display the instrument UI at all, and since Cubase was unusable, the only way to exit it was to kill the process in Task Manager. In Cubase, after opening a new instance of Kontakt and selecting a library, Kontakt would spend some time loading samples, but then would eventually freeze, locking up Cubase entirely. It was even worse in Steinberg Cubase 9, though. When launched as a plugin in Ableton Live 9, Kontakt behaved just the same as in stand-alone mode. I then tested Kontakt in my two DAWs to see if results were any different. Again, all UI elements of the instrument were displayed on-screen at once, and none of them were usable.
0 kommentar(er)
