I have a Project that I have been moving from the desk to the laptop and back. All works well with the exception of Kontakt 5 always stops and asks where to find the Renaxxance samples when I switch to the different machines.
 
The samples do reside on different drive letters but all the other 3rd party libs I am using also reside on different drv letters and I don't get that error msg. on those.
 
I have tried about everything I know to do using my limited Kontakt knowledge, NI's forums, google searches, etc. I am probably just having a senior moment but it is starting to put me off as I've been doing this daily/nightly for a week now and I just can't solve it.
 
When the msg. comes up, I can point it to the right location for that particular machine and everything loads up fine but it has now become the proverbial thorn and I am letting it hinder the creative process every time I have to go through that process.
 
Any suggestions or direction would be greatly appreciated!
 
Kind regards,
Rick

Batch save or save preset as maybe?

This could probably be remedied with a re-save of the .nki and choosing the correct options in the save dialogue.  At times, the vendors will code it with absolute path names when they should be relative path names. When you switch machines, if there are absolute paths saved in, then the new machine doesn't know where to find the samples.

Thanks for the quick reply's,
 
Have already tried the batch resave and the .Nki is a tweeked preset that resides on both machines. All paths are set to Relative. (I've been burned on the absolute path before...)
 
I do notice that there was an update to this library and one of the .nkc files has a date that is much different. I will probably try to change the extension to something else and allow the .nkc to be rebuilt next time I load the .nki.
 
Currently in the process of changing out to larger sample drives so it looks like the project is going to reside on the laptop for a couple of days....  It will be so nice to load the project without getting that insane error msg.

Sometimes I have GUI issues caused by .nkc files & have to delete them.

Do they re-build ok when you load the .nki's back up?

The reason some libraries complain while others do not comes down to how the developer saved the pathnames, whether they're relative to the root folder or absolute paths. It's quite normal and expected behavior for Kontakt (or any other application) to not find the files by the paths embedded in the nki if those file locations do not exist.
 
If the only difference between the library locations on your two computers is the drive letter, you may be able to solve the dilemma by using a drive letter substitution or link. I haven't tried that solution for any Kontakt libs, but it worked for me when I moved Dimension Pro's files from their default location.

rtucker55
Do they re-build ok when you load the .nki's back up?

Not sure about all libraries but in Albion 1 / One yes.
To fix the gui problem I needed to delete the .nkc files that were in the Scripts folder.
After re-opening the files were re-generated & the gui appeared normally again.

I Really enjoy using the Renaxxance library so, while I am swapping out the sample drives to larger ones, if I move that library to the same drive letter on both machines the problem should go away? Sounds like an easy solution since I will be copying things over anyway.

Yes, try to keep the folder names and drive letters the same when you upgrade hardware and you'll save yourself some hassles.
 
I did not do that when I migrated to a new computer earlier this year. That decision was intentional so I could organize things better, but I paid the price for it. Not just because I sometimes had to tell Kontakt where to find the libraries or samples - the biggest hassle is that in some cases I lost extensively customized patches. Nothing I couldn't recover from, but is was a PIA getting some projects to open on the new machine.
 
Here's a suggestion for your desktop->laptop scenario: freeze the Kontakt instruments you don't plan on modifying on the alternate machine. Kontakt won't have to load them then, and therefore won't complain.