Sonar Platinum & BFD2 Not Getting Along!!

You should use a common VST folder for all your Sonar versions. That way when you install a new one you enter the existing VST path in the setting and all your old VSTs are instantly there.
 
 

This very curious & interesting.
 
I've installed Platinum on my 2 systems, both of which have BFD2 installed.
 
On one system, I chose NOT to import my previous settings - Sonar found BFD2 and runs perfectly.
On the other system, I chose to Import previous settings and guess what - BFD2 appear as normal and works perfectly.
 
So I don't know what's happening in your case.
Can you run BFD in stand alone mode? That's the first thing to check. From there, you should be able to get it running inside Sonar without issue.

Colin,  are you using the default VST locations? In which case all your Sonar versions would be looking in the same place ...
 
 
Mojo,  I use 2 VST folders as standard.  i:\VST\32  and i:\VST\64  where i:\ is one of the extra HDDs in my system.  It should be obvious why there are two from the names... 
The New Sonar adds two more...  i:\VST3\32 and i:\VST3\64.  These are all in the preferences.

Yes Karyn, I believe I am.
 
I will check tonight when I get home, probably during the AD2 download.
 
I've been trying to keep these 2 machines in sync so that they have exactly the same software installed, but it's not easy!

Karyn

Mojo3432
Out of curiosity...Say it works in stand alone.  Then what?  How can I make it work in Platinum?

I would start by putting the .DLL back where you found it and adding the old VST path into the prefs.

I would add a reset/rescan of all VSTs.  (Couldn't hurt, and if everyone did it would likely clear up a lot of the glitchiness some are seeing in the move to New Sonar).
 

Hi John,
 
It may be a case that Platinum did not copy your SONAR preferences over when starting for the first time.  Try starting SONAR Plat while holding down the Shift key.
 
It may be easier to include all VST folders in the VST scan paths (Edit|Preferences|File|VST Settings).  The possible problem with moving dlls around is the way the plugin was installed.  Some plugins have execution files which make reference to other folders such as "content" and their location in the Registry.  So, if you move the dll, it is broken from the installed path in the registry.  It might be difficult in locating all VST folders, but most often there are two folders for VST2, your preferred location such as Programs (x86)|Cakewalk|VSTplugins or the ubiquitous Programs (x86)|Steinberg VSTplugins (Steinberg becuase they invented the VST format and is the default for a majority of plugins) or just VSTplugins.  As mentioned above, with the advent of 64bit plugins and VST3, there are still additional folders to locate under the "Programs" (without the "(x86)") folder for 64bit systems.
 
The above provides ancillary info for those whom may not be aware.
 
Kind regards,
 
tecknot