CLSID problem

Hi Nick,

I can't give you any specific info on this error, but for me, it happens because I have both Sonar 32 bit and Sonar 64 installed. Because of this, my 32 bit plug folder is included in my 64 bit folder scan. Thus, when Sonar 64 opens, I sometimes get that exact issue you are running into.

To make it stop: I copied and pasted all my plugs that are 32 bit that have 64 bit counter-parts, to a custom folder that is NOT included in my Sonar 64 folder scan. So when Sonar 64 boots up, there are no chances of any 32 bit plugs showing up that have 64 bit brothers already installed.

The only other way this could be happening to you (I'm no tech support guy) would be if you have some how tried to uninstall a plug or something got moved or jacked somehow, it may remain in your registry. Sonar is seeing two instances of the same plug pretty much. If you are having the 32 bit/64 issue like I had, a good way to test for this is to try each option in the "identify" list. When the plug opens up, if it's bit bridged and you are using Sonar 64, that's the one you DON'T want it to open and it's probably hapeening because you have your 32 bit plug folder being scanned in 64. You'll know it's been bit bridged as it opens up with a light blue/grey border around the plug window. 

If it IS a case of a 32 bit plug showing up in 64, don't just un-include the 32 bit plug folder because there may be 32 bit plugs that need to be bridged. The best bet is to just copy all 32 bit plugs that have 64 brothers and paste them into a new folder. Then, if you use Sonar 32 also, make sure you add that folder to your 32 bit Sonar plug scan.

Simply my belief here: To my knowledge, we have a new plugin scanner in X2. Ever since this was implemented, I've had nothing but weird anomalies with CLSID errors to where I have NEVER seen this before in any other version of Sonar. I have been running the same folder/file system for many years and now, it doesn't work. For example...

My normal VST plugin directory for 32 bit Sonar has always been C:/Program Files/Cakewalk/Vstplugins (XP) or C:/Program Files (86)/Cakewalk/Vstplugins.

When running Sonar 64 and changing to Win 7, my Sonar 64 plug directory is always C:/Program Files/Cakewalk/Vstplugins. Enter Sonar X2, and it is not only seeing the CLSID issue you mention, but if the project was created in Sonar 32 bit and is then opened in Sonar 64, it will NOT convert the 32 bit plugs to 64. It bit-bridges just about all of them. I've never seen this behavior in any version of Sonar where I have run 32 and 64 bit at the same time until now. So it is my belief that this new plugin manager is still not quite right and this is not our faults.

This has forced me to move all 32 bit plugs that have 64 versions also, into another directory as I mentioned. I don't like doing this as I like all my 32 bit plugs to be in one folder, all my 64's to be in another. Since Sonar 8 I've only ever used 2 plug folders. Now, there's 3. Not that it's that big of a deal, but let's face it...where you install something is where it should remain. If I ever try to uninstall these plugs that I moved, I'm sure I'll get a ton of errors and my registry is probably not quite right. I just hate having to do work-arounds like this. But, if your issue is sort of like mine, that should fix you up.

Just remember, after you move the plugs, do another 64 plug scan so it clears the other versions of the plugs out of there. You should no longer get that CLSID error after you do that stuff. Best of luck.

-Danny