No need to apologise, this is exactly what the forum is for.

Heinbokel


Alright, apparently it's fixed. There was a problem with the 64 bit dll and the directory etc...

It was a stupid mistake, I've only taken one course with Berkleemusic on Desktop music production, everything else has just been on actual composition, nothing to do with the production/technology. 

So sorry guys, I still have a lot to learn about Sonar, I think I'll take a course just for Sonar.

It's an easy thing to overlook even if you are on top of it.  Installers can put stuff where you don't want it and stuff like that can happen.

I just have a directory structure setup outside of the basic Sonar install paths that goes:

Program Files/Vstplugins  <--- 3rd party 64 bit plugins go here.
Program Files(x86)/Vstplugins < 3rd party 32 bit specific plugins go here.
Program Files(x86)/VstBridged <-- Bridged 32 plugins to be shared with 64 bit Sonar go here.

Then I just add 'Program Files/Vstplugins' and 'Program Files(x86)/VstBridged' to the scan path of Sonar 64.
Then 'Program Files(x86)/Vstplugins' and 'Program Files(x86)/VstBridged' to the x86 version of Sonar's scan path.

Of course if you don't run the 32 bit version of Sonar you can dispense with the 'Program Files(x86)/Vstplugins' folder and keep 'Program Files(x86)/VstBridged' just for 32 bit plugs you want to run bridged in Sonar 64.

Sorry to drag this one up but I am having a similar problem with my new Windows 8 installation.

I've currently got a test project on the go, into which I am inserting every plug that is available through Cakewalk and all the third party stuff I have collected.

The obvious problem is that I'm running 64bit X2a and there are still a lot of plugs I am using that are 32bit, some of which I don't really use. But I was wondering if there was a particular culprit. Perhaps one of the older Cakewalk plugs?

Again, apologies for dragging this up from the depths.