Rhytenow


Thanks for all your help.  Just a quick question, when I add it in the new folder (via Jbridge) will my old projects find that it's in the new folder automatically?  That's what I'm worried about.  I don't my old projects to not be able to find BFD2 because I know I use Jbridge with the separate folder option.  

I'm sorry, the way I explained it, you would be using the original BFD2 in your old projects, and the jBridged version going forward in new projects.  If you want to use the jBridged version in your OLD projects, there is no automatic way of doing that that I know of.  You will have to delete the old BFD2 VST and add in the new jBridged version manually.  Sorry.  Maybe someone else knows a trick there that I don't.

Before you do anything drastic try configuring BFD2 to work with what you have. One thing you can look at is memory. It will try to load everything into memory and some of its kits use more than 8 GB of memory. This can cause all sorts of problems when you consider Sonar also needs some memory too. You can set it so is loads only a portion of the total amount thus you can work with it without issue.  Another thing to try is use as few FX within BFD2 as you can get away with. They tend to be CPU hogs. 

You don't loose much but you do gain a working BFD2.

Thanks John.  When i think about it.  I think that's probably the issue.  I'll go in and change the memory settings.  

Curious to why you aren't using the x64 BFD2 version without any converter... I am using X2a and BFD2 under WIN8 and no issues whatsoever.

Jim

Just to add on with what everyone else said, you should be using the x64 bit version of BFD2 in Sonar x64. If you're having stability issues, you should post the specific issues either here, on the Fxpansion forums, or to Fxpansion directly via a support ticket.

It doesn't make sense to wrap that 32bit version using JBridge, and I doubt it will resolve your issues. I'm a BFD2 beta tester, and can tell you it's been extensively tested in Sonar (there's another forum member who is also on the beta team) and works like a champ. As someone already pointed out, your issues could be related to memory usage, which is easily resolved in BFD2's engine. 

You might get problems running BFD if the samples aren't on a dedicated drive.

And it also makes no practical sense to load the 24 bit samples - just use the 16 bit ones and challenge anyone to hear the difference.

Just to add on with what everyone else said, you should be using the x64 bit version of BFD2 in Sonar x64. If you're having stability issues, you should post the specific issues either here, on the Fxpansion forums, or to Fxpansion directly via a support ticket. It doesn't make sense to wrap that 32bit version using JBridge, and I doubt it will resolve your issues. I'm a BFD2 beta tester, and can tell you it's been extensively tested in Sonar (there's another forum member who is also on the beta team) and works like a champ. As someone already pointed out, your issues could be related to memory usage, which is easily resolved in BFD2's engine. 

I think my issue may be that I don't have BFD2 on a dedicated hard drive and I am using the 24 bit samples.  I'll try putting the samples on their own drive and going down to 16 bit samples.  Thanks, for everyone's input.   As crazy as it sounds I was going to wrap the 64 bit version.  I know it sounds crazy but I've done it to other 64 bit plugins that have given me trouble and it's fixed the issues.  

I am that other beta tester and can scarcely recall ever having problems with BFD2 32 bit or 64 bit in sonar.

Definitely move your samples to another drive, obviously make sure it's a fast drive 7200 rpm and not green or blue.
Internal would be best too. You might find that alone will fix your problem, if not then try the 16 bit rather than 24 bit
You really won't hear any difference.

As far as the jbridge option goes, (not that you'll need it) it is integrated into sonar now so you should be able to go to the plug in manager, choose the VST you want to use jbridge with, click properties and you'd see a check box to use jbridge.
It should then open all your existing projects that use BFD2 with jbridge so you shouldn't need to create separate projects.

Steve

twaddle


I am that other beta tester and can scarcely recall ever having problems with BFD2 32 bit or 64 bit in sonar.

Definitely move your samples to another drive, obviously make sure it's a fast drive 7200 rpm and not green or blue.
Internal would be best too. You might find that alone will fix your problem, if not then try the 16 bit rather than 24 bit
You really won't hear any difference.

As far as the jbridge option goes, (not that you'll need it) it is integrated into sonar now so you should be able to go to the plug in manager, choose the VST you want to use jbridge with, click properties and you'd see a check box to use jbridge.
It should then open all your existing projects that use BFD2 with jbridge so you shouldn't need to create separate projects.

Steve

Thanks Steve, it worked.  

Thanks Steve, it worked.  

So you're saying you're using jbridge now and your problems have gone ?


You still should move the BFD2 audio to another drive.
Have you installed the 64 bit version of BFD2 and if not why not ?


Steve