Taken from an earlier post of mine on the subject:


It turns out that the name of the soft synth is in the .cwp file in plain text.  So I used a search tool (Cool Find from nihuo software) which has text string searching within a file.  Note that although Windows Search appears to have the same facility it doesn't search within .cwp files.  Since I only really need to find projects that use a specific soft synth Cool Find works fine for me.  Since Cool Find also supports searching for the AND or OR of strings I can also find, for example, all projects that use TTS and PianoOne.  --Larry  PS:  I'm not pushing the Cool Find product - I'm sure there are other search tools that can do the same thing, maybe even for free. 

Guitarhacker


X1 will still open all the projects just fine, it will give you a notice that the project has a missing plug in. Simply delete it and save that project.... 

Herb, that I knew. But that is not the issue. If I knew, before I delete the plugin, where it's used I could open the project and replicate the FX/VSTi and remove the plug from the project. If the plugin was simply gone from my system, when I open the project I would have no idea what I had done with settings wise.

I probably should have explained that better in the OP.

bapu

yorolpal


While you're at it put in a request also for a feature that tells you what plug you "should have" used instead iffn you hadn't been a nitwit.  I'd get a lot of use out of that.

Are you gonna pay for the now ruined keyboard (whew! I had a spare) from the mouthful of water I just sprayed all over it from LMAO at your remark???? Huh????

You really should be using one of these then:

 
Just in time for hurricane and typhoon season too!
 
...
 
from Logitech, of course.

yorolpal


While you're at it put in a request also for a feature that tells you what plug you "should have" used instead iffn you hadn't been a nitwit.  I'd get a lot of use out of that.

+1. :)

SONAR needs some reporting features. Imagine a report that showed all the details for a project: which plugins were used on which tracks, a routing diagram, file statistics, unbounced AudioSnap and V-Vocal clips, and the notes from the File -> Info page. 

In my day job I deal with databases, where reporting isn't just a nice add-on, it's an absolute necessity without which all you have is a meaningless pile of data. A SONAR project is a database, but one in which the data can only be managed via the application that created it, a very 1970's approach. Or worse, an IOS approach. 
 
The problem with a grep-like text search tool like the one mentioned above is that you have to know what you're looking for in advance. I can imagine a tool that looks in your VST folder and makes a list of all your plugins, looks up their CLSIDs in the registry and then scans projects while aggregating data. Maybe I should write that tool.

bitflipper

 I can imagine a tool that looks in your VST folder and makes a list of all your plugins, looks up their CLSIDs in the registry and then scans projects while aggregating data. Maybe I should write that tool. 

You'd be my hero Dave.

Mine too!