Posted
I had an vst plugin that was present in two different places, the plugins are identical and had the same name. Both locations A and B were added as search paths in synfire. That's why the plugin was listed twice in synfire. That's ok/correct.
For all of my songs I used only the plugin from the one location A.
Now I removed this search path A in which one copy of the vst plugin was located.
The result: Synfire does not find this plugin in all of my songs any more:
I would think it still should be able to find the plugin because actually one with the same name is available from the location B. But it seems synfire insists on the absolute file path of the (identical) plugin - which is not very nice...
Is this a bug ? If not, I would suggest this as enhancement: "Try to find another plugin with the same name if the one originally used isn't availabe any more at its absolute path".
Mon, 2017-02-20 - 02:45 Permalink
I would guess that Synfire and most DAWs assign an id to each plugin. A VST in a different location may have a different version number, might be 64bit or 32bit. A new version may have fixed problems in an older version.
If you want to clean up your search paths, you should point your Synfire files to the new location first.
I have 4 VST locations: 1 - plugins that insist on C:\ drive and can't be moved;
2 - 64 bit plugins; 3 - 32 bit plugins; 4 - VST3 plugins.
I scan only the appropriate location(s) for whatever program I'm using.
I hope this helps.
Mon, 2017-02-20 - 15:05 Permalink
Well, that location may be part of the ID info,which is why it's no longer found. You can test this by copying it back to that location.
If it works, duplicate your setup using the plugin from the correct location. Then delete the old setup and the plugin copy from the bad location.
I hope this helps.