• SONAR
  • "The following VST plug-in CLSID could not be matched with an entry in the VST plug-in ...
2014/01/31 18:48:24
BlixYZ
"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."
 
This message keeps coming up when I-
A- try to insert a plugin
B- try to change plugin layouts
C-  open a project
 
sometimes i will have to click through a dozen, sometimes the same plugin will come up more than once in just a few minutes.  This just started happening recently.   I was told to do a full plugin rescan (reset) and it did not help.
All my plug-ins seem to work, but this is REALLY annoying.  I'm endlessly clicking through these pop ups!
Help!
2014/01/31 19:00:54
scook
Could it be a bad plug-in layout? The CLSIDs are stored in the layouts. The only layout built on the fly is "Default All Plug-ins". Does the problem persist if all the layouts are set to default?
2014/01/31 19:06:26
John
What version of Sonar are you using?
2014/01/31 19:06:43
Splat
Remove all 32 bit equivalents of 64 bit plugins (assuming you are running 64 bit), and anything else that looks like a plugin dupe I suggest.
2014/01/31 19:10:20
BlixYZ
ok, i'll try checking the "remove 32 bit dupes" box.   
I'll get back to you.
2014/02/01 20:42:43
BlixYZ
I am running X3d.   Installing it started the issue.   in 64 bit there are lots of plugins it can't locate.   In 32 bit there are only a few.
 
If no one can help me, I am going to uninstall X3d and go back to X3c.
 
My 32bit X3 is also very unstable.  I dont want to try to "clean" my plugin folder, because i have over 1000 plugins and even though i dont use many of them, most are used at least once in old projects.  
 
I admit that I'm bad at managing my plugins, I've just never learned how to do it properly and efficiently.  If there is thread or article on how it should be done, I'd love to read it.
 
2014/02/01 20:46:00
John
Did you reset in the plugin manager then do a full scan?
2014/02/01 20:49:57
Splat
VST Reset.
 
If you have 1000 plugins I would suggest removing most of them. Be quite hard to yourself about it. Just use the basic requirements and add the plugins as and when a project complains about a missing plugin. There is no way 1000 plugins could be useful.
 
Cheers...
2014/02/01 23:49:54
kitekrazy
BlixYZ
I am running X3d.   Installing it started the issue.   in 64 bit there are lots of plugins it can't locate.   In 32 bit there are only a few.
 
If no one can help me, I am going to uninstall X3d and go back to X3c.
 
My 32bit X3 is also very unstable.  I dont want to try to "clean" my plugin folder, because i have over 1000 plugins and even though i dont use many of them, most are used at least once in old projects.  
 
I admit that I'm bad at managing my plugins, I've just never learned how to do it properly and efficiently.  If there is thread or article on how it should be done, I'd love to read it.
 




 That must take an hour for an DAW to scan all plugins. You must have close to a gig in drive space just on plugins.  As DAWs get updated you will probably have more problems when plugs may scan but will create errors especially if they are the DX format.
 
2014/02/02 10:59:43
BlixYZ
I cannot help it if clients sometimes ask to open old projects.  If the plugins aren't there then I have to replace them all and remix.   Clients wont like it (and i wont either).
 
I totally agree that FAR fewer are necessary and I have a small number that I go to regularly, but I want to keep the old ones around so old projects can be useful.  I just ordered jbridge to possibly help with compatibility moving forward.  It's ironic because i just read a post of a guy who said gbye to jbridge after using it for years but not needing it anymore.
 
I don't see why just having these plugins in my vst folder should cause a problem when they aren't being used (often).
 
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account