Native Access Error: "Path is invalid" when trying to locate an existing expansion

2»

Answers

  • neilyhype
    neilyhype Member Posts: 9 Member

    What third party library are you referring to? What does Kontakt 8 have to do with London Grit? Are you aware of Native Instruments expansions?

    Please be honest with me. Do you have a clear understanding of the issue that I've mentioned?

    I am not being rude. I just want to make sure that we are on the same page.

  • neilyhype
    neilyhype Member Posts: 9 Member

    I just bit the bullet and redownloaded it instead of trying to use the 'locate' function

    london grit installed.png

    Here is a screen shot of the expansion folder

    london grit folder.png

    Here are 2 screen shots from Native Access

    london grit installation path.png london grit installation path right.png

    I have other expansion with the same issue as well. I guess I have to waste bandwidth to redownload them again. It makes me ask the question. Why does Native Instrument have a 'locate' button beside the expanstion in the first place??

    Here is how the locate feature looks beside another expansion:

    bumpin flava.png
  • Uwe303
    Uwe303 Moderator Posts: 4,696 mod

    Ok then redownload is maybe the way to go. I tested also with the london grit expansion and moved it, I could locate it without any problems, moved it back located again and it works all like it should - really strange, I honestly don't know what's going on

  • victorp.sg
    victorp.sg Member Posts: 211 Pro
    Answer ✓

    Normally, if you keep your NI Content on external storage and reformat your system boot disk to do a fresh installation, you can use the Relocate feature of Native Access to point to the actual location for Kontakt Libraries only. Expansions, unfortunately, will have to be re-installed.

  • BertTRP
    BertTRP Member Posts: 2 Member

    Coming back here only now after having opened the topic.

    A huge thank you to @neilyhype for having gone through the excruciating process of having to fight through the endless set of useless requests of @Uwe303 and above all @Mert_NI to read out and follow pre-cooked solutions that are clearly not addressing the problem raised here. I can understand you might need to give it a try to make sure that who is experiencing the issue has properly done research before throwing it here asking for help, but 2 pages of basic and non-aplicable knowledge base links before you even try to replicate the issue yourselves?

    What frustrated me? We clearly specified "expansions" from the beginning. Why all those replies which apply to "libraries" before even getting the focus right? And why all this time and forth and back to demonstrate to you that the problem is real, when it would have taken you a few minutes to test the issue yourself as described in first place? We are paying for this product, we are more than willing to help Isolate the issue in our own and the common interest... but doing someone else's work is a totally different issue!

    I'm glad we have now a certainty: we need to redownload expansions, they simply can't be "located" today!

    I hope someone here will take care to report this internally either as a bug (remove that locate button for expansions) or a feature request (add a working locate functionality for expansions).

  • neilyhype
    neilyhype Member Posts: 9 Member
    Answer ✓

    I agree. I'll redownload them

    Thank you for your assistance still. Stay blessed

  • victorp.sg
    victorp.sg Member Posts: 211 Pro
    edited September 2024 Answer ✓

    @BertTRP — NI Expansions can be relocated, provided you had already installed them on your system (not a fresh installation), and you just want to move them to some other disk volumes or external storage devices.

  • Tom Auger
    Tom Auger Member Posts: 73 Helper
    edited May 29

    This is a frustrating thread to be sure. I, too am having an issue using the "Locate" feature with an EXPANSION (not a Kontakt library).

    My situation is the following: I had previously installed everything on an old Mac, but the content libraries on an SSD. Then I migrated to a newer Mac, and used the Locate feature to avoid having to re-download all my expansions. That worked great.

    Now, while my new Mac is getting serviced, I wanted to continue gigging with my old Mac, but it somehow has lost the connection to the SSD and shows the expansions as not installed. I had hoped to be able to use the Locate feature to reconnect and avoid the bandwidth issues.

    Based on the thread, I'm guessing that the only real option is to bite the bullet and re-download the expansions (on my ****** internet it takes about 10 minutes per 2Gb expansion…)

Back To Top