Content Location not obeyed by installation in Native Access

ebtihal

I bought a new ext SSD and have moved/repaired the location of many libraries in the Native Access app. However, a few libraries are still pointed to an old location on another ext HD which has no remaining space, and my problem is that I can't relocate them. In NA/Preferences I've specified the path to this new ext drive as the default content location, but it seems this is only for future installs, not libraries I've already installed— am I right?

NA prefs.png

Because, e.g., when trying to update Kontakt Factory 2 Library, I right-click on its name in the Updates page to show its content location, it shows its previous path on that full HD.

NA old location.png

And I can't edit it, clicking on it just opens that location up in Finder. I tried deleting the folder for Factory 2 Library off that old location, to try and trick it, but it just tried to reinstall to that same location, which of course fails, as there's no space left on that old drive.

NA download fails.png

(Also, for some weird reason, Vintage Organs is failing, but I know that must have to do with the fact that I'm 60 and my heart and liver are old. Heh heh.)

I must be missing something, just can't see what. Thanks for any assistance, as obviously NI can no longer find it worthwhile to fund a support staff. : (
-Peter

Vocalpoint

To your first question - yes - changing paths is for future installs and has no effect on existing libraries.

Best solution is:

1. Get out of NA.
2. Move everything off the old drive to new.
3. Important: When moving old to new - ensure the folder structure remains identical (except for the new drive location so this:

(ideally) should go to something like this:

/Volumes/sample libraries 2TB/NI Libraries/Kontakt Factory Library 2 Library

That said - if I can make a suggestion - your content location folder names are excessively long and complex making this more difficult longer term.

Example: Here are my locations (On Windows 10) using Native Access 3.16+:

I find that NA really loves standards. And simple short "default" directory structures. If you install Native Access clean - you will see that all it's folders are standard - that is they all end in Native Instruments.

I have modded my "content" location ever so slightly. But the folder paths are all short and simple.

You might consider setting your new "content directory" on your new drive to something simpler (in Native Access) like:

/Volumes/Libraries/Native Instruments

and then let any future content you install (via NA) to naturally find a home as:

/Volumes/Libraries/Native Instruments/Kontakt Factory Library 2

/Volumes/Libraries/Native Instruments/Playbox

/Volumes/Libraries/Native Instruments/Vintage Organs

etc etc.

Simplifying these folder paths will make it much easier to manage.

I also get the feeling you might be using an old version of Native Access too. Some of your dialogs look outdated.

Good luck with the cleanup.

VP

Monochrome

When repairing (or locating) a library, you will need to choose its folder. Just picking the main path ("/Volumes/sample libraries 2TB/Native Instruments") won't cut it. It will complain and say "invalid path or directory" then.

Vocalpoint

To your first question - yes - changing paths is for future installs and has no effect on existing libraries.

Best solution is:

1. Get out of NA.
2. Move everything off the old drive to new.
3. Important: When moving old to new - ensure the folder structure remains identical (except for the new drive location so this:

(ideally) should go to something like this:

/Volumes/sample libraries 2TB/NI Libraries/Kontakt Factory Library 2 Library

That said - if I can make a suggestion - your content location folder names are excessively long and complex making this more difficult longer term.

Example: Here are my locations (On Windows 10) using Native Access 3.16+:

I find that NA really loves standards. And simple short "default" directory structures. If you install Native Access clean - you will see that all it's folders are standard - that is they all end in Native Instruments.

I have modded my "content" location ever so slightly. But the folder paths are all short and simple.

You might consider setting your new "content directory" on your new drive to something simpler (in Native Access) like:

/Volumes/Libraries/Native Instruments

and then let any future content you install (via NA) to naturally find a home as:

/Volumes/Libraries/Native Instruments/Kontakt Factory Library 2

/Volumes/Libraries/Native Instruments/Playbox

/Volumes/Libraries/Native Instruments/Vintage Organs

etc etc.

Simplifying these folder paths will make it much easier to manage.

I also get the feeling you might be using an old version of Native Access too. Some of your dialogs look outdated.

Good luck with the cleanup.

VP

ebtihal

Vocalpoint THANK YOU for this detailed message! Super well-laid out and easy to understand.
Yeah, that old path was convoluted, as it was made years ago when I was running out of space and needed extra space on a media drive quickly. I normally eschew long filepath names as much as possible.
But the new path is simpler, like what you'd suggested:

new lib location.png

and that just exacerbates the problem— now, at least NA sees that the library should be repaired…

NA repair.png

but telling it where the new path yields an error window that tells me the new path /Volumes/sample libraries 2TB/Native Instruments is invalid.

NA relocate lib fail1.png

-P
P.S. btw, I'm using Native Access Version 3.16.0 (e4a635d / 1.22.0.0), I just dl'd-instld it… shouldn't look old.

Monochrome

When repairing (or locating) a library, you will need to choose its folder. Just picking the main path ("/Volumes/sample libraries 2TB/Native Instruments") won't cut it. It will complain and say "invalid path or directory" then.

Vocalpoint

https://community.native-instruments.com/discussion/comment/196548#Comment_196548

Exactly.

You need to actually click on the location area and point it to the newly created folder structure you built.

And of course make sure the actual Kontakt library files are where you are pointing.

Do this for every library that is erroring out.

VP

ebtihal

Oh, weird, got it. I mean, it seems obvious now that you say it, but most other libraries I'd been re-directing could figure it out once pointed to the enclosing folder/directory.
Thanks, Monochrome and VocalPoint!