CLSID Tip
After a search I saw that I was not the only one to suffer from the dreaded CLSID mixup that can happen after a fresh installation.
In short what happens is the VST-Adapter creates its CLSID for a plugin (which is a unique number) partially based on it's 8.3 (old dos style?!??!?) filename.
When many pugins have similar long names like the Voxengo or Kjaerhaus stuff it is easy for a certain plugin like VoxengoPristineSpace.dll to have one of many short file names like VOXENG~1.DLL VOXENG~2.DLL or even something really wacky like VO6442~1.DLL
Thus under certain circumstances it is possible to end up with a 'missing plugin' message when that plugin actually exists.
Well, I have a somewhat complicated, but fairly sure-fire way to fix this. It is kind of tricky... but for me MUCH easier than alternatives.
Before you start, PLEASE BACK UP ANYTHING IMPORTANT!!!!! 1. Load up the broken project.
2. Press the online information button to get the CLSID Sonar is LOOKING for. (this can also be found in the plugins placeholder)
3. Use some sort of HEX->ASCII converter like this one:
http://bluefive.pair.com/hexwrite.htm paste the CLSID into the hex box and clean it up so it is on pairs with no dashes. For example:
141AC902-564F-4558-564F-58454E477E33 becomes
14 1A C9 02 56 4F 45 58 56 4F 58 45 4E 47 7E 33
4. Note the ASCII this represents The last 8 characters (in this case VOXENG~3) is what the SHORT 8.3 name of the file is supposed to be in your vst directory. This name will now be different.
5. Load up a CMD window.
6. CD to the plugin directory. (You can use the command: 'dir /x' to see both the long and 8.3 names of a file. We are going to ONLY change the 8.3 one.)
7. Do THIS command:
fsutil file setshortname Longnameofplugin.dll SHORTN~1.DLL
or in the case of our example:
fsutil file setshortname VoxengoPristineSpace.dll VOXENG~3.DLL
(In the case a long file name has a space in it, you will have to enclose the long file name in quotes.)
8. Rerun the Adapter, tell it to reset all, and let it do it's thing.
Bingo. You are back in business.
Like I said, I realize this is a huge pain... but it is the best way to solve the problem I know of. A better idea would for cake to include a 'Suggest Plugin' feature in the missing plugin stand-in thing. That way we could repoint the session to the right DLL file.
Hopefully SOMEONE finds this useful some late night when in the agony of this problem! ;)
cAPS
post edited by cAPSLOCK - 2005/08/13 04:26:43