Native Access is constantly forcing me to relocate/repair libraries (disk access fully enabled)

KikkoAndMoonman
KikkoAndMoonman Member Posts: 12 Member
edited 1:18PM in Native Access

Hello,

This seems to be a problem affecting numerous people since the last update, but I am constantly needing to repair libraries as NA keeps losing track of them, despite my external drives not being disconnected or having any issues. It is causing significant frustration as I keep needing to repair.

All disk access is fully enabled for the necessary plug-ins, so no issues on the OS side. This appears to be Native Access issue, possibly due to the last update.

We would all be grateful for this issue to please be acknowledged, with some reassurance a fix is coming imminently? It is hugely affecting workflow.

On MacOS Sequoia 15.4. NA 3.18.0

Tagged:

Comments

  • DunedinDragon
    DunedinDragon Member Posts: 1,076 Guru
    edited 12:54PM

    What platform is this on? I'm on Windows 10 and Native Access ver. 3.18.0 using external drives as well and haven't had any such issues at all.

  • Vocalpoint
    Vocalpoint Member Posts: 3,759 Expert

    On a number of other forums I frequent - I am starting to see a LOT of chatter on this topic.

    All from Mac users and all about the same issue. One minute NA can see their externals and the next it cannot.

    While there may be some obscure connection to the latest NA update (v3.18.0) - I have also seen a number of folks talking about Sequoia (specifically) suddenly losing/forgetting "internal disk IDs" in MacOS which of course then starts to look like it's a Native Access issue - when in fact it is not.

    Have not read a single post about any Windows user experiencing this.

    Given the amount of posts that I have come across - I am starting to think this is a "where there is smoke - there is fire" kinda thing going on here.

    What exactly it is - is unknown however.

    VP

  • KikkoAndMoonman
    KikkoAndMoonman Member Posts: 12 Member
    https://community.native-instruments.com/discussion/comment/225675#Comment_225675

    Ah sorry, should've put that info. Updated.

  • KikkoAndMoonman
    KikkoAndMoonman Member Posts: 12 Member

    That's interesting, but important to state that I've been on Sequoia for a while now, and I've had zero issues. This has only happened since a newer update to Native Access, so I do feel it is fair to, for now, point the finger at the Mac release by NI.

  • Vocalpoint
    Vocalpoint Member Posts: 3,759 Expert
    https://community.native-instruments.com/discussion/comment/225683#Comment_225683

    Well - being "on" Sequoia has nothing to do with it.

    Being on 15.4.1 is definitely part of the chatter. This seems to be a Sequoia ONLY thing given the threads I have come across.

    I can also tell you that I have been reading about this elsewhere for easily over two weeks - which is outside the boundary of the latest NA (3.18.0) release - which I believe was about 10 days ago now.

    If the v3.18.0 release IS suspect - stands to reason folks still running Sonoma or even Ventura would be seeing issues - but I have not seen that with my limited reading. And there are tens of thousands of users still on those two.

    If this was rampant - we would have known by now - considering none of us have zero ability to stop a Native Access update.

    There is definitely something going on here…possibly just with NA and Sequoia specifically.

    VP

  • KikkoAndMoonman
    KikkoAndMoonman Member Posts: 12 Member
    https://community.native-instruments.com/discussion/comment/225685#Comment_225685

    I think maybe there's a bit of pedantry here based on what I'm trying to say. By being "ON" Sequoia, I am referring to the version and previous versions I have been on (I'm currently actually on 15.4).

    I think the biggest thing here is that NI have a responsibility for this to work on the latest MacOS. It working fine for people on Sonoma or Ventura is sort of irrelevant. However, again, I wasn't having any issues on my current version of Sequoia before this NA update. Granted, it can be a combine issue, but my issue history right now has been very much pointing at something that the last NA did, since it's only occurred now whilst being on the same version of Sequoia beforehand.

  • Vocalpoint
    Vocalpoint Member Posts: 3,759 Expert
    https://community.native-instruments.com/discussion/comment/225687#Comment_225687

    I have no idea what is going on and I am not a Mac user. Just communicating what I have seen in my travels.

    Again - this does not appear to be rampant (yet). But I have to assume a bunch a Sequoia users are on v3.18 and are not having any issues whatsoever.

    If there is some sort of obscure thing going on - that is on NI (and possibly Apple) to figure out.

    VP

  • PK The DJ
    PK The DJ Member Posts: 2,616 Expert

    I agree, from past posts on here, there's definitely something when using Macs with libraries on external drives that causes issues. It's related to the mount names or something.

  • PoorFellow
    PoorFellow Moderator Posts: 6,691 mod

    Issue has been put forward to N.I. as a possible bug - I suppose that maybe @Jeremy_NI will look into this when he returns Monday (or later ?) .

  • red_nick
    red_nick Member Posts: 331 Pro
    edited 5:18PM

    Sounds like this bug, which is a Mac issue, not Native Access. https://support.native-instruments.com/hc/en-us/articles/19786452976029-I-Constantly-Have-to-Relocate-My-Products-in-Native-Access-macOS

    Should probably put something in Native Access when things are missing (on Mac) to link to that article, because people keep having the same issue without realising it's actually their mac. Maybe it could detect when the mount point doesn't match the name.

Back To Top

Categories