BFD2 and Jbridge and Sonar X1 Settings

I'm having issues with BFD2 and I'm thinking about using it inside jbridge.  I already have some songs that are recorded that use BFD2.  Will it mess things up when I recall my older songs?  I ask this because I know if I use jbridge, the place where Sonar will look to find my BFD2 VST will have changed.  

I'm using Sonar X1c with AMD Athlon Phenom II x6 2.9 ghz, 8 gb ram, 1.5 tb hard drive wd 7200 rpm, Focusrite scarlet 2i2.  I guess I'm not trying to trouble shoot BFD2, I'm just trying to see if Sonar will still find BFD2 when I use it with Jbridge.  So far any VST I've been having trouble with has been solved by using Jbridge.  

Rhytenow


I'm using Sonar X1c with AMD Athlon Phenom II x6 2.9 ghz, 8 gb ram, 1.5 tb hard drive wd 7200 rpm, Focusrite scarlet 2i2.  I guess I'm not trying to trouble shoot BFD2, I'm just trying to see if Sonar will still find BFD2 when I use it with Jbridge.  So far any VST I've been having trouble with has been solved by using Jbridge.  

  I think since BFD2 is a VST it will behave just like any other you've tried.  It creates a "jBridge version" and you will have to delete BFD and add the jBridge version to your project.  As for your old projects, I believe when you create the jBridge versions you have the option of putting them in a separate folder.  If you do this and leave BFD2 in it's original location you will be fine.  You'll just need to add the jBridge folder to your VST scan.

If you are getting stuttering and drop-outs, it might be because you are running everything off one hard drive.  BFD uses samples so it works best to have those stored on a different hard drive from the OS and Sonar.  The usual recommended set-up for a DAW is OS and Programs on one hard drive, sample,loops, etc. on a second hard drive, and your project and audio files on a third.  You can get by with two, but you should have your samples on a separate drive at least. 

If that's not your problem, perhaps you could describe exactly what's happening in more detail.  That would make it easier to get your problem resolved.

Thanks for the advice SF_Green.  I'm not getting dropouts, BFD2 just randomnly crashes Sonar X1.  I did a safe mode boot up and it makes Sonar take a while to open up because of it.  When I open up and old project that has BFD2 will Sonar find my new location of BFD2, or will I have to tell it where it is?  

Rhytenow


Thanks for the advice SF_Green.  I'm not getting dropouts, BFD2 just randomnly crashes Sonar X1.  I did a safe mode boot up and it makes Sonar take a while to open up because of it.  When I open up and old project that has BFD2 will Sonar find my new location of BFD2, or will I have to tell it where it is?  

If you use the jBridge "Use separate folder" option, you would have to go to the Cakewalk Plug-In Manager, hit the Option button, and add the new jBridge folder to your scan locations.  I'm not sure why Steinberg chose to use the ".dll" library extension for VST's instead of using ".vst", but that's why we have to tell it to only scan specific locations, since .dll's are everywhere on your computer.  

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.

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

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. 

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.  

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.  

Yes, I'm using JBridge and my problems are gone.  I was using the 64 bit version.  I guess to reiterate, I wasn't having constant problems with it but I was loading a big kit and that's when Sonar stopped responding and I noticed there was an issue.  I'm using version 2.3.0.38.  I haven't moved the audio folder to a different drive but I will do that this week.  I loaded up the same big kit that caused Sonar to stop responding and under JBridge nothing happens.  Also my projects seem to load quicker now.  

Was 2.0.38 even 64 bit?  I think that 2.2 or something was the first 64 bit version???? I could be wrong.

The other parameter that can be changed is how much of the samples get loaded into RAM so you can balance the RAM usage and HD through put.

Bottom line though, you got it working and you are happy.

Jim

PS - I use a ton of sample instruments in my work and have to tweak the engine of the sample players, settings in SONAR to balance the load so I don't run into any issues myself.