Last nite I installed Waves NS1 demo on my computer and once again I had to do this little "trick" to make Sonar's Plugin Manager to notice that there is a new plugin (demo) installed. The trick is that I have to cut WaveShells from my VstPlugin folder (which is located on my Audio Program drive (F) - and launch Sonar, shut Sonar, move WaveShells back to their original location and after that manouver every new plugin is listed on Sonar's Plugin Manager. Weird, isn't it?
But something happened last nite. During my special "trick" I accidentally opened one of my current projects and because those WaveShells were "on exile", Sonar couldn't locate them. No problem. I closed that project and hoped that there was no damage done. After that I moved WaveShells back to their folder and reopened that same project and then I got this:
Locate VST Plug-in
The following VST Plug-in CLSID could not be matched with an entry in the VST plug-in list. Please identify the plugin from the nearest matches listed below.
Original Name: The King's Microphones Stereo
Original CLSID: {lots of numbers and letters}
New CLSID: {lots of numbers and letters}
New Path: f:/audio programs/vstplugins/WaveShell-VST
After clickin "OK" (couple of times) project opened and The King's Microphones and all those other unlocated Waves plugins were located and working. So after that I opened Plugin Manager and rescanned every plugin. BTW: my Waves folder was lost so I had to create a new one and add all my Waves plugins to the folder. That was little weird.
Ok, I shut Sonar and reopened that same project file. Waves screen popped up to tell me there was 53 Waves plugins (Diamond and Silver) that were not available anymore (demo expired), ok, clicked "SKIP". Back to Plugin Manager and all those 53 expired Waves plugins were gone and I thought that it may have solved the problem. I repeated this couple of times to make sure that everything was working and went to bed.
This morning that same "Locate VST Plug-in" screen popped again + that Waves expired plugins screen.
Now everything seems to work fine
So what do you guys think? Hope you managed to understand me... poor english, not enough sleep and too much coffee.
