It doesn't search for a plugin, but tries to match a given plugin to another plugin. In particular this means that it matches the parameters of a plugin to a preset (called 'program' in VST speech) of a different plugin.harryupbabble wrote:If I made a song that used reverb plugin X but now reverb plugin X is broken and I want to have that same sound of reverb plugin X then your application will search my VSTPlugins folder to find reverb plugin Y and a specific preset of reverb plugin Y... and it actually will have the same sound as reverb plugin X?
Since this is not an easy task, it takes quite long already (in some test cases about 8 hours, but depending on the number of parameters it can be far more or less). Eventually the tool could also be altered to try different presets instead of altering the parameters, but this might be too limiting.
Please note also, that I haven't modeled the ear with the tool, so it might be that two plugins will sound "perfectly" equal to your ears, but not for the tool. This is mainly because of the fact that the ear typically ignores the phase properties for many cases (you can only hear the phase when it translates to a time delay and in particular on transients). Since this is hard to emulate and the perception is also different for everyone, the tool only checks rather mathematical/technical issues.
This means that you typically don't really need a perfect match, but a close match is already quite useful.