Why is Kontakt accessing my connected NAS shares despite none of my libraries being installed on it?

dreikelvin
dreikelvin Member Posts: 17 Member
edited February 13 in Kontakt

Hi there,

I have a weird issue where all of my KONTAKT instances, be it KONTAKT 5, KONTAKT 6 or KONTAKT 7 - as soon as I load them as a VST inside my DAW, I can immediately hear my NAS drives spin up and accessing something.

None of my NI products are installed on any network share, just locally on my hard drive. My DAW project is saved on the network volume, yes. But even if I create a local project and load the KONTAKT vst, it first accesses my NAS - why?

How can I make KONTAKT stop doing this? It seems to slow down loading of the plugin quite significantly and there is no benefit from scanning all my network shares since all the libraries are hard connected and have their local paths set, pointing to local folders.

Pretty strange, if you ask me. It would be great if anyone had a tip for me how I can make KONTAKT not touch any of my network shares, thank you!

Answers

  • Milos
    Milos Member Posts: 1,836 Pro

    I will 'summon' @Jeremy_NI to help you.

    I am pretty sure he can solve the issue.

  • reffahcs
    reffahcs Member Posts: 713 Pro

    If you're NAS drive is mounted as a share on your Mac/PC then my guess would be that your DAW is just accessing every attached drive?

  • dreikelvin
    dreikelvin Member Posts: 17 Member
    edited February 11

    Sorry, can you specify? You mean KONTAKT is accessing every attached drive, correct? I don't see why my DAW would have anything to do with that. That would mean it takes control over all the connected file systems and relays them to the plugin. That cannot be the case, can it?

    My theory is that KONTAKT simply scans all available volumes that the OS reports to it - and that includes creating an index tree of everything, which means it has to index my NAS share which takes a bit longer than the other drives. If that is the case, I would love an option to turn off certain drives in the KONTAKT browser tree.

  • reffahcs
    reffahcs Member Posts: 713 Pro

    No I meant DAW. At least for me with Ableton Live it usually does a quick scan for any new VST/VST3/AU plugins during startup.

    One way to rule out your DAW would be to try Kontakt in standalone mode.

    What operating system are you on?

  • dreikelvin
    dreikelvin Member Posts: 17 Member

    I'm on Mac. The same thing happens when I launch Kontakt in standalone.

  • reffahcs
    reffahcs Member Posts: 713 Pro

    Interesting... hard to say. Perhaps Kontakt polls the Mac for available drives when it starts up? I know there's some file locations stored in Kontakt itself, separate from NA so that may be why it's searching for drives?

    I've always been a PC person until about a year ago when I jumped on the ARM bandwagon, so I still don't really understand how Mac handles NAS/SMB shares at the OS level.

  • dreikelvin
    dreikelvin Member Posts: 17 Member

    yes, definately. I had an issue a couple years ago where I moved my sample library from one drive to another and native access wasn't able to do that at the time. so I edited some .plist files (macs equivalent of registry and .ini on windows) to change the paths - it worked well but somewhere there was still a path that I didn't see or was unable to access and kontakt was constantly looking for that missing drive...a complete reinstall was the only option. there is definately some weirdness with file paths/drives inside Kontakt.

Back To Top