Posted
Hi
i didn't want to put this on bug reports because it seems like  vst plugin directory usage/scan  logic of SFP to me..
ok
recently i was messing with my old projects ( 2-3 months older)
and i just realized that
1-- if you change main  vst plugins directory  ( for example: minimal / copy of it  ... just covers the fav. instruments)
2-- also changing   one of the vst folder ( for example :  re installing plugin to different location in  vst plugins folder) 
causes error message about "....could not find their original sounds" "
"ErrorMessage" png.
synfire can't open projects properly.
more details:
Engine 32 bit 
in this example project contains  2 plugins   Nexus (7 instances)  and Kontakt
my regular vst plugins folder is too big to scan...also   a lot of free vst fx and too many midi plugins etc.
so not all of  them useful for SFP works ..
i decided to create small selection of my fav. vst instruments in a new folder name: "Synfire Minimal" 
also my nexus dll was in the root of the main/regular vst folder before..
i installed nexus again but this time in to the nexus folder instead of root folder...
and i copied this folder too ...to the synfire minimal folder
and kontakt dll was in the root of the main vst folder... i copied kontakt dll to the root of the minimal folder..
so same as in the main folder..
...
i did full re-scan for this new minimal vst folder.
opening all plugins to new instruments is ok too.
but
when i try to open old projects
 i got that error message .
first   i  switch to the  my regular vst plugin folder and  i did  full re-scan again...
 this solved kontakt problem but   didn't fix the nexus  problem..
then i copied  nexus dll  to the root folder...
all problems gone  (now i have 2 nexus in the plugin list)
...
this definitely not a negative feedback
for the safety of  future i think it would better to look at "main" vst folder (regardless to name of this folder)...
also  not  to the folders of each vsts ..
because when users  have to do new system format + setup
its almost impossible to remember + re-crate of  each vst's original folder locations + folder names.
Sorry if i missing something here
Best Regards
Yıldırım
Mon, 2012-07-23 - 23:20 Permalink
uhmm
i can not say % 100  there wasn't device descriptions
but probably % 90 there wasn't... because at the beginning   i was using only private plugins / devices
creating and using  device descriptions  new to me ...
also important point in this case
 only putting vstis back to their  first locations fixed the problem.