Komplete Kontrol loading issue, apple silicon or vst2 to vst3
Answers
-
not all libraries work with kontakt 7-8
0 -
Because you are looking in the mac hd/ user /library/application support / audio/ plugins
You want Mac hd/ library/ application support/ audio / plugins
0 -
The path of the libraries is stored on .json files at:
C:\Users\Public\Documents\Native Instruments\installed_products
Open json file with notepad and manually fix the location or other info.
Or, do this:
1 -
I get that msg because of super 8 r2 , but it tells me it’s super 8 r2 that’s causing it , been meaning to uninstall it , but the other day I unchecked it in the plugin manager ( maschine ) rescanned and it still shows up , maybe it’s the reaktor version , but , I can’t find another super 8 to uncheck
Also noticed I have multiple (3) vst3 versions of v collection X listed in the plug-in manager, and plugin lists , also some air plugins , hybrid
I deleted my locations and added them again , rescanned, but they’re still there , so Ive switch to AU
0 -
ok I’ll check that out, I pointed that out , because I got mallet flux the other day , which says kontakt 6 is needed , and I’d recently uninstalled kontakt 6 , and native access made me install it again , so I can understand why people still have the different versions installed
0 -
If K6 can play it, then K7-K8 can play it too.
The other way around is not possible of course.
And it can be fixed, easily!
So, no, usually i can't understand why people keep older versions. From my experience it only make things more complicated, since the software try to understand with which version should it opens a file (among other things). But in this case, i will make an exception.
The confusion rises from a simple fact. While versions 7 and 8 have distinct names, version 6 simply mentioned as "Kontakt" (on a plugin level). Why they do not just use "Kontakt" always?
Without numbers or anything else._______________________________________________________________________________________________________
To developers: The common sense says you don't change the name just because a new version is coming. It's silly and creates unnecessary incompatibilities.
A good example (to be avoided) is FabFilter Twin. What a nightmare! It was Twin 2 now it becomes Twin 3. Old version removed from stores, then you open DAW and of course it can not find the "Twin 3" plugin in your older projects (since you make them with version 2), while if you just kept the name as "Twin" and not this stupidity (Twin 2, Twin 3), none of this will ever happening.
So here i am, spending precious time to re-create my projects with the new version. It's beyond annoying!
For me this is a sign that a developer do not care about commitments and obligations to his customers, only cares to make more money. And make no mistake, such "incompatibilities" are rarely by accident. In many cases they were designed on purpose to create more (unwilling) customers.1 -
Well, the folder on my external drive called NI Libraries. A folder name shouldn't be an issue right?
And in that folder there are some libraries with the name Library at the end but most do not, so none of these names should cause any issue by loading libraries.
All works fine now, so which info is wrong?
0 -
If all works fine, then no info is wrong! 😉
0
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 62 NI News
- 785 Tech Talks
- 4.1K Native Access
- 16.6K Komplete
- 2K Komplete General
- 4.3K Komplete Kontrol
- 5.7K Kontakt
- 1.6K Reaktor
- 380 Battery 4
- 846 Guitar Rig & FX
- 429 Massive X & Synths
- 1.3K Other Software & Hardware
- 5.8K Maschine
- 7.3K Traktor
- 7.3K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators