• SONAR
  • "Locate VST in CLSID could not be matched" (on loading old project)
2013/05/11 11:47:26
moffdnb
Hi all,

When loading an old project (from my 32bit days), some VST/I's cannot be be located.  Obviously since porting to 64bit things have changed.  However I still use them under JBridge and they work ok.  When this error pops up I can choose the closest match that Sonar finds:

Example:

Original name NEXUS
Suggested match NEXUS.64

Ok all good and work but my question is once I have selected this new match and resaved the project I would have thought this new association is made permanent.  Not the case.  I have to select each VST everytime I open the same project.

Anyone know if this can be made permanent?

Much thanks!

 
2013/05/11 11:55:56
scook
Have you tried using the "Replace Synth" function in synth rack or track?
2013/05/12 06:08:38
moffdnb
No.  I'm on X1D  ;>
2013/06/30 07:54:38
adrian.crossan
moffdnb
Hi all,

When loading an old project (from my 32bit days), some VST/I's cannot be be located.  Obviously since porting to 64bit things have changed.  However I still use them under JBridge and they work ok.  When this error pops up I can choose the closest match that Sonar finds:

Example:

Original name NEXUS
Suggested match NEXUS.64

Ok all good and work but my question is once I have selected this new match and resaved the project I would have thought this new association is made permanent.  Not the case.  I have to select each VST everytime I open the same project.

Anyone know if this can be made permanent?

Much thanks!




You may have resolved this by now, but I ran into a similar problem. I upgraded to the 64bit version of Microtonic, after which X2 made me choose which version to use (32 or 64) on opening the project. I resolved this by forcing a full VST Scan from within the Plug-in Manager: VST Configuration Options -> Re-scan existing plug-ins.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account