silvercn
I am wondering if for the sake of overall C drive discs space, if there is any problem I should be worried about with putting my VST folder/files to an external drive - my DAW will be on C.
Thanks
With Sonar I've found that keeping the Sonar default VST install location and then custom location/s after that is the way to go.
Simply because certain Cakewalk plug-ins (e.g. Dimension Pro) won't work from a different location than the default install (without fiddling around at least).
Similarly a bona fide Audio editor such as Wavelab, Sound Forge etc, will have some non-realtime plugs that will not make much sense in a realtime host, so you may want to keep those in an application specific folder too.
That way you can set the scanned paths in Sonar to scan it's own folder and ignore the Audio app VST plug-ins and vice versa.
Over and above that any available plug-ins you want to be available to any app, put them where you desire and set up the scan paths in each app accordingly.
However as you are citing disk space being an issue I'm wondering if you are meaning VSTi's that come with large libraries, because the plug-ins themselves generally take up small amounts of space.
Generally you will want large sample libraries on your fastest drive (especially ones that are accessed direct from disk such as Kontakt) to save on loading and sample retrieval times which your external drive isn't likely to be, although it may well be fast enough not to cause issues.
post edited by Jonbouy - 2010/12/05 19:53:27