Thanks for the quick reply. I've done as you recommended, and while that worked for the standalone app, when opening a project in Sonar that uses the GPO VST plugin, I get an error message for each sample (where OldPath is the previous location of the lib):
The AutoFind button is enabled, the Find button is disabled. If I select Abort Loading or Ignore for each instance and get the project up, I can bring up the Synth rack, pull up a GPO player, click options, and sure enough, it's pointing to the new path that I set via your suggestion. However, my project doesn't seem to honor this change.
Creating a new project, however, now works appropriately as does adding a new GPO instance in an existing project. However, I'd naturally like to avoid having to go through each and every project, delete the old synths, add new ones, recreate the instruments and settings, etc.
Do you know of a way to get an existing project to recognize the new directory?
I doubt there's any automatic way to deal with this problem. At least, I don't know of one. All plugin settings are saved with the project; apparently this includes the library path. I'm guessing the easiest solution is to just let the plugin search for the samples. If you choose "Manual" you can quickly point it to the library folder. With a bit of luck it will remember this folder for the remaining instances of the project. And you won't have to set up the plugins anew.
I was thinking that might be the case. Oh, well. You got me set up for all new projects, so for the pre-existing ones it's a matter of updating the settings.
By the way, since I'm seeing GPO4 now and I'm on 1.x, I was wondering if you have any experience with the new version. Mainly I'm wondering if I upgrade, will my existing projects play nice with the new version, or will there be some sort of conversion process similar to what I'm doing with the new directory?
If I'm gonna go through the projects, may as well only do it once.
Don't know about GPO4; I am using GPO2 in Kontakt 3.5. But, one thing I do know, is if you upgrade to GPO4 you will have to either stick to GPO1 in existing projects re the way I outlined, or delete the old GPO1 instances and replace them with GPO4 instances, which have to be set up from scratch. Could be a lot of work.