Browse for Folder

Question

Hi there,

Here is the scenario:

I have a Cubase Pro 15 project containing various NI Kontakt tracks. So far, these tracks appear correctly and are synchronized across both my laptop and my PC—where I am working on the very same project.

However, for two specific tracks, the file paths failed to load automatically when moving from one PC to the other, for a reason I cannot identify.

The screenshot shows which tracks are affected. I am now wondering—something I have never encountered before—how I can fix this so that everything carries over correctly, even when switching between computers.

On my laptop, the NI products are located on the (D:) drive, whereas on my desktop PC, they reside on the (E:) drive.

Warm Regards

P.s.: Strangely enough, it affects the "Loops" section in Kontakt 8.

.

JesterMgee · Answer

https://community.native-instruments.com/discussion/comment/263398#Comment_263398

What it is likely trying to suggest is to create a "symlink" or "junction" which may work (it's a way of making a dummy link from an old location to the new one so software still sees things at the old location), but it's a bandaid to a problem that just shouldn't exist. I guess if AI says it should work then give it a try asking AI for advice, tho the description you provided by simply creating a "shortcut" and placing it in the startup folder doesn't make sense but who am I to argue with the all knowing AI overloads…

Endzone · Answer

@Uwe Thanks a lot for your feedback. Apparently, I’m not the only one—though that hardly surprises me; once I realized I could reproduce the issue across two different machines, I had the idea to ask my AI about it. Now, regarding @JesterMgee : the AI ​​actually suggested that I could mount the drives—that is, simply create a "shortcut" (or alias)—and, if desired, place it in the shell:startup folder so that it loads automatically whenever Windows 11 starts up.

Could it be a Solution? I don´t know…

JesterMgee · Answer

Yeah it's honestly stupid how NI plugins work with content resolution and a hard path. It's a big reason I moved away from plugins such as Battery where I spent months making multi-channel battery drum racks in Live but after overhauling my whole system and moving my NI content to a different drive, everything just broke and I ended up having to manually open hundreds of kits, scan for the new files and resave again.

It should use relative paths…. like almost every other library based plugin does. Irrespective of the actual drive or path, the content if available is linked to the project because of course that also makes it difficult between mac and PC.

No solution other than to just update the path and save but if you move between 2 machines constantly, as mentioned by Uwe303, having the exact same path is the only real way to overcome it because given it's been like this for 20 years now, NI ain't fixing it.