![]() macOS 10.13 / Windows 8 or earlier), you can download an older version of Native Access from here. Once installed, Native Access can be found in the following directory: Note: If using an older OS version (e.g. ![]() Of course, with moving libraries, you will have to redirect Kontakt itself to any changed sample and instrument locations, as well as potentially batch re-save. You can user KONTAKT to create sophisticated sample-based virtual instruments, process their audio signals with powerful DSP structures, build complex performance setups with extensive modulation routings, and gain access to a vast range of creative third-party sample libraries. Native Access is an administration tool for product activation, installation, and updates for all Native Instruments products. My mantra for moving libraries is to still open these first in Kontakt, and make sure those are displaying (not knowing about the new “hide” box stumped me as well at first), then close that out and run Komplete Kontrol in stand-alone to rescan its data base (which can also be done manually in its preferences). The above has now become the new “step one” in a three-step routine I use for keeping all the relevant Komplete Kontrol (and sometimes Maschine) instruments and libraries accessibly if/when using my Komplete keyboard, but also, mainly, when using Kontakt in my DAW. And, per the prior advice, finding the associated p-list files may be necessary for problems, though I personally have only ever done this when removing unused NI products entirely. In short, all of the above is what NI suggests not doing, i.e., moving something once installed, but it all seems logical to me. I think there may even be a rescan icon in NA, but I'm not at my computer to double-check this. I can click on any product and it will show its associated path for future updates. Relaunching Native Access then updated those respective paths in the interface. ![]() So, I moved each respective NI product in and out of these designated NI User folders, then deleted the original locations (on that, I moved things temporarily to the trash until I was sure the new locations are recognized). I agree: NI needs to update this to be an option, and I recall them mentioning they were looking into.īut I suspect it can simplify things to create and name a new folder for “User,” though I am not certain if there is a unique ID associated by NI upon installs, as I already had three NI established locations to begin with for moving things around. I actually had three different locations already establish, on three different drives, from the older Service Center method, but the bulk of things were getting installed onto the new “default” path NA determined. FWIW, I have managed to divide up the NI stuff onto three different drives - and have Native Access now recognize each of these designated paths.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |