I read somewhere I should install one or the other, but not BOTH 32-bit and 64-bit versions of BFD Eco... but somehow that is what I did.
 
I also have BFD Eco DV, which is 32-bit only, and it is also part of my question, which is in two parts:
 
  1) Since I am running X1 in 64-bit, should I remove the BFD Eco dll from the (x86) vstplugins folder and re-scan?
 
  2) Looking at the .dll file sizes, I found the 32-bit version to be 8280 KB, while 64-bit was only 6940 KB? Eeehhh???
 
Jonesey, Beepster (or anyone with BFD Eco expertise) please chime in! I'm unsure what to do, but have been having some problems with X1 freezing/crashing ONLY when it involved one of the BFD Eco plug-ins. Wondered if I needed to get rid of the 32-bit, but can't understand why that .dll would be larger.
 
(BTW: I re-installed JBridge this AM and told the Plug-In Manager to load the 32-bit DV with that wrapper, but have not had time to test that yet.)
 
Thanks for any input!
 
Joel

Same scenario here.   I think both versions of the Eco VST are installed by default.
 
But to be honest, it doesn't really bother me at all - I just choose Eco 64 and DV 32 (since that's all there is).   And I haven't found any issues so far doing this. 

Thanks, Steve. If I weren't having some issues, I would do like you are doing and not sweat it.

Anyone else have any ideas about the differing file size of the dll? Or any other thoughts?

This happened to me also. I simply deleted the desktop icon for the 32 bit version of the stand alone version.

In Sonar, it showed up straight away as a 64 bit plugin.  No need to Bitbridge or jBridge it. Personally i couldn't be bothered to delete the 32bit version, i'm not short of space.

Its simple to check.  If you're on 64bit Sonar and you installed the 64 bit dll and ran the plugin manager, then try to put the dll in the Multi-dock. If you can do that, its the 64 bit version.

Cheers,
Jerry

OlSkoolGuy


I read somewhere I should install one or the other, but not BOTH 32-bit and 64-bit versions of BFD Eco... but somehow that is what I did.
 
I also have BFD Eco DV, which is 32-bit only, and it is also part of my question, which is in two parts:
 
  1) Since I am running X1 in 64-bit, should I remove the BFD Eco dll from the (x86) vstplugins folder and re-scan?
 
  2) Looking at the .dll file sizes, I found the 32-bit version to be 8280 KB, while 64-bit was only 6940 KB? Eeehhh???
 
Jonesey, Beepster (or anyone with BFD Eco expertise) please chime in! I'm unsure what to do, but have been having some problems with X1 freezing/crashing ONLY when it involved one of the BFD Eco plug-ins. Wondered if I needed to get rid of the 32-bit, but can't understand why that .dll would be larger.
 
(BTW: I re-installed JBridge this AM and told the Plug-In Manager to load the 32-bit DV with that wrapper, but have not had time to test that yet.)
 
Thanks for any input!
 
Joel

I have both installed and both versions of sonar (32 & 64 bit) installed too.
Sonar 64bit doesn't list Eco 32 bit and vice versa. When you load BFD Eco you can check the "About BFD Eco" from the question mark and it will tell you whether it's 32 bit or 64 bit.
When using the plug in manager do yo8u see two versions of BFD Eco listed? I only see one and it's the 64 bit even though sonar can see both my vst folders.
As for the file size it's  8280KB is only 8.25 Megabytes.


Steve
 

Hmmmm... the deeper I go, the weirder it gets.

@twaddle: Steve, I am only running X1 64-bit, but the plug-in manager only shows BFD Eco 32-bit (as confirmed by the location of the dll).  I was able to get FXpansion to authorize the RENAMED 64-bit version (I renamed that dll "BFD Eco64"), and that NAME now appears in the list in plug-in mgr, but - again, confirmed by dll location - it is STILL the 32-bit version!!! What do I need to do to just lose the 32-bit version; simply delete that dll and re-scan again?

@joakes: Jerry, your situation is obviously different, since you have both versions of Sonar installed. But if you are certain the 64-bit dll is 82.5MB, then my dll files somehow got reversed. Still digging...

Thanks to all for your suggestions... if you have any more, please jump in!

Joel

It's supposed to install both and I don't think you can opt out. I haven't tried it as a plug in yet but yeah... just make sure when using it to use the 64 bit version. Also I wouldn't remove those 32 bit files personally. They might be needed. As far as the BFD DV version I was a little weirded out that it's 32 bit as well but was told that it works fine without any fiddling around. Are you using multiple instances of BFD? Apparently you aren't really supposed to do that. Not sure why but I'm assuming it's a resource issue. Also did you install the audio data on a second drive or let it install on your C drive? That might be borking things up too. Sorry I can't be much more help. I have really haven't had a chance to really mess around with it as a plug. If you can't get it going you can always send FXpansion an email or call them. I almost did the other day but I figured out my issue on my own.

hmm... Maybe you should try reinstalling at this point. It really shouldn't be screwing around like that and fiddling with it might just make things worse.

And the reason I say leave the 32 bit stuff in place is because of the sizes you've just described. AFAIK the 64 bit version was built on top of/around the 32 bit version so it might have some internal JBridge type thing drawing from the 32 bit stuff. I'm just guessing though. Frankly I find all this 32 vs. 64 business very confusing.

I just had another thought, and I'm just guessing here. Perhaps if you launched the 32 bit version for your initial set up instead of the 64 bit maybe it's confusing Sonar. I'd try reinstalling, install the audio data to a secondary drive (if possible) then launch the 64 bit version as a standalone (if you don't see a desktop icon just go to the FXpansion folder in your programs menu and select the 64 bit version). Be sure to "Run As Administrator" then the click options menu button (not the Windows style dropdown but the button with the question mark) and select "Set Data Path". If you don't see the folder where you installed the audio data you need to select it manually (I forget the exact process but once you are in that dialogue it's easy to figure out and it is detailed in the manual). After you can see the data folder click that same question mark button and select "Rebuild Database". Then try using it as a plug in Sonar. Just a thought.