Reply to thread

Message: [QUOTE="Queen, post: 90655, member: 27"] Native Access installs Kontakt content to the Shared folder on macOS and to Public Documents on Windows, and both of those sit on your system drive. Nobody chooses that. It is simply what happens when you paste in a serial and click through. Oracle asks for about 5GB, which is nothing. That is the trap. Five gigabytes is small enough to ignore, so you ignore it, and then you do the same with the next library and the one after that until your boot drive is full of samples and your projects load slowly for reasons you cannot pin down. The decision costs thirty seconds before the first install. Afterwards it costs an evening. [HEADING=2]The three location settings are not one setting[/HEADING] Open Native Access, go to Preferences, then File Management. You will find three separate paths, and people routinely assume they are the same thing. Download Location holds the installer files, the temporary junk that arrives before anything is unpacked. Application Location is where standalone software goes, and NI's own guidance is to leave that one alone, since moving it invites stability problems for no benefit. Content Location is the one that matters, because that is where Kontakt libraries, Reaktor instruments, and Expansions actually land. Point Content at your sample drive and leave the other two as they are. One rule to respect while you do it. Never set Downloads and Content to the same folder, because NI documents that as a cause of failed installations, and the failure looks like a corrupt download rather than a settings mistake. Change these before you install anything. Native Access applies new locations only to future installations, so [B][URL='https://goldmidi.com/community/threads/teletone-guts-moog-roland-korg-for-oracle.51865/']the 5GB of sampled hardware Oracle installs[/URL][/B] will sit wherever the setting pointed on the day you activated it. Everything already on disk stays put until you move it by hand. [HEADING=2]Repair is the button that means relocate[/HEADING] Say the library is already in the wrong place. [B]Moving a library to a second drive[/B] is a documented procedure, just one hidden behind a strange label. Close Kontakt, close your DAW, close anything touching audio or MIDI. Move the library folder to its new home with Finder or Explorer. Open Native Access, go to Library, then Installed, then Kontakt, find the entry, and click Repair. Click Repair again in the window that appears. A Locate window opens, you click the folder symbol, browse to the folder in its new location, and confirm. You get a success message and a Done button. Repair sounds like something you press when a thing is broken. It is also the relocation tool, and that naming trips up more people than the process itself. On Kontakt 6 and earlier the flow runs the other way around. You move the folder, launch Kontakt, and Kontakt throws an error saying the library content was not found, with a Locate button in the dialog. You browse for the folder from there. Worth knowing why copying alone never works. The browser entry is a registration in a database, not a live scan of your drives, so Kontakt keeps looking at the old path and reporting content missing no matter how neatly you filed the samples. [HEADING=2]Cheap storage shows up as dropouts, not as bad tone[/HEADING] NI's performance guidance is blunt about the hardware. An SSD gives the best results, because Kontakt streams samples off disk while you play rather than loading everything into memory first. The thing to avoid entirely is a cloud-synced folder. Dropbox, iCloud Drive, and OneDrive all want to reconcile files in real time, and NI specifically recommends against real-time syncing, suggesting you sync only when the application is closed. A sync client rewriting sample files underneath a running instance is a fault you will spend hours misdiagnosing as a plugin bug. If a slower drive is what you have, the relevant control lives in Kontakt's own Options window under Memory. There is an override for the instrument's preload size, which sets how much of each sample is held in RAM before disk streaming takes over. NI recommends leaving it at default, and that advice is sound, but knowing the knob exists is useful when a specific setup misbehaves. Lower values lean on the drive, higher values lean on memory. The other lever is the Max voice parameter in the instrument header. Oracle is polyphonic, so a held chord with a long release can stack far more voices than you think, and trimming that number cuts CPU load directly. Ten voices covers most parts. Twenty covers almost everything you would actually play. [/QUOTE]

Name