• SONAR
  • New install: plugins not matching up.
2012/11/28 23:51:41
...wicked
I recently rebuilt my DAW (from WinXP sp3 32-bit to W7 64-bit) and now my projects won't recognize their appropriate plugins. I found this thread in researching:

http://forum.cakewalk.com/tm.aspx?m=281141&high=clsid+matching

That seems to be similar to my problem. Sadly there's no resolution in that thread. I'm wondering how screwed I am here. Anyone experience something like this?

2012/11/29 00:37:37
robert_e_bone
Could you please list some of the ones that are not matching up?

I dropped 32-bit stuff a long ways back, so my upgrade path has been 64-bit for a while, and this has never occurred for me.

But if you can list a few, I will take a look and see if there is anything I can find of assistance for you with this.

Thanks, 

Bob Bone

2012/11/29 12:17:39
...wicked
older NI plugs mostly (but not exclusively). Absynth (2), Pro-53, Kontakt, but some other plugins too. DimPro for example. 

I, in perhaps the only smart thing I did when I re-built, kept a copy of my old VST folder. Based on a tip I got I'm going to comb through and check actual .dll names to see if there's discrepancies. 
2012/11/29 13:04:28
robert_e_bone

If you installed a 64-bit Sonar, then you got 64-bit versions of its default installed synths.  The Dim Pro is also a 64-bit component now.  The program file structure changed when you went to your now 64-bit OS, as there are now 2 different Program Files folders, one just called Program Files (for the 64-bit progs), and one called Program Files (x86) for the 32-bit progs.

Many of the NI plugs have been upgraded to 64-bit versions, which would definitely be better for you.  Your old setup only had the 32-bit ones loaded.
Go to the NI site and download all of the updates you can for any of your modules from NI.

Pro-53 was eliminated some time ago, and though I just tried running my old 32-bit version of it on my newly installed Win 8 64-bit machine, as soon as I press a note, it makes some NASTY noise then quits playing - it seems to be toast and I removed it.

Akoustik Piano was also done away with - but was rolled up into Kontakt, sort of.  They did NOT keep all of the old presets.  What you want to do there is to have an active version of Akoutik Piano installed - it will be 32-bit, and load its sample libraries, I think there are either 24-bit or 32-bit ones during the install.  Then, after making sure its activated, get rid of the Akoustik Piano component, but KEEP the libraries.  You can ADD each of the sound libraries from the different pianos into Kontakt's newer versions, so you can still play all of the sounds - but using a 64-bit version of Kontakt as the player.

Hope any of that helps you, 

Bob Bone

2012/11/29 13:10:30
robert_e_bone
As a matter fact, I LITERALLY just after posting above got an email from NI that a new version of Reaktor is out there as a free upgrade with a bunch of nifty new functions.

Bob Bone

2012/11/29 16:40:28
eric_peterson
I am having similar fun with my move to waves v9 from v5 - they dropped DX in favor of vst, and v9 and v5 can not coexist. So much fun!
2013/02/20 03:16:03
...wicked
Resurrecting this thread, as I'm still stuck with the same probs. Plugins have the same .dll name so that's not it.

I'm contemplating nuking my SONAR install and reinstalling in 32-bit to see if that reconnects my plugins. Aside from that, I'm stumped.

I know SONAR stores patch info for synths in it's project file, does anyone know if there's any way to access that info? At least then I could manually locate the patches in the synths that don't seem to realize they're already installed.

2013/02/20 05:38:42
Lanceindastudio
You can install 32 bit SONAR on the same system as 64 bit SONAR while keeping 64 bit version installed and see if they work in 32 bit.

Having both 32 and 64 bit installed is good if you need to open old projects.

Lance

© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account