Jump to content

BFD2 with Logic


Recommended Posts

  • 2 weeks later...
I was wondering if anyone has had any experience using BFD2 with Logic. I just got the new imac and I have heard that this is a beast of a program but I have also heard rumors that it does not work well with Logic.

 

I have down loaded the free demo and it seems pretty versatile.

 

Hmmm. Don't know who, or why, you've heard that it doesn't work well with Logic?

 

I have a copy and have used it from time to time - never had any issue whatsoever. It does prefer a lot of RAM, though.

 

I only use it with the 8-bit expansion pack and it's never hiccuped or given me any trouble at all.

Link to comment
Share on other sites

A little surprised at Spiralsurfer's post - I thought you couldn't run BFD2 in a 64-bit application. Or is it that BFD2 just won't take advantage of the whole 64-bit deal?

 

I've been sticking with 10.5 because I make heavy use of BFD2 and the UAD plugs, and thought those wouldn't work if the OS and Logic were 64-bit: is that wrong?

Link to comment
Share on other sites

A little surprised at Spiralsurfer's post - I thought you couldn't run BFD2 in a 64-bit application. Or is it that BFD2 just won't take advantage of the whole 64-bit deal?

 

I've been sticking with 10.5 because I make heavy use of BFD2 and the UAD plugs, and thought those wouldn't work if the OS and Logic were 64-bit: is that wrong?

 

To make the transition to 64-bit easier, both Logic Pro and MainStage are still able to access 32-bit-only Audio Unit plug-ins while in 64-bit mode by using a utility application called 32-bit Audio Unit Bridge. This application opens automatically whenever a 32-bit-only Audio Unit plug-in is accessed.* The 32-bit Audio Unit Bridge hosts all currently used 32-bit-only Audio Unit plug-ins and runs alongside Logic Pro or MainStage to provide access to the plug-ins being used.

 

The 32-bit Audio Unit Bridge has the same 4GB memory address limit as any other 32-bit application. Also, it is only possible to display and edit one 32-bit plug-in at a time.

 

Audio Unit plug-ins which are 32-bit only will appear in the channel strip plug-in insert menu under "Audio Units (32-bit)". Audio Unit plug-ins which are 64-bit will appear in the normal location in the menu. Check with your favorite third-party plug-in developers for updated information on the availability of 64-bit versions of their plug-ins.

 

Taken from here:

 

http://support.apple.com/kb/HT3989

 

J.

Link to comment
Share on other sites

Thanks, Jordito. That sounds like an unworkable drag for the kind of projects I'm working on.

 

As long as we're on the subject, is it true that 4GB is the ceiling for how much RAM Logic can access in a 32-bit system (like the one I'm using, where Logic and the OS are both 32-bit)?

 

I ask because I have a song I can't even open any more with my 2GB of RAM, and am wondering whether grabbing 2GB more will help.

Link to comment
Share on other sites

As long as we're on the subject, is it true that 4GB is the ceiling for how much RAM Logic can access in a 32-bit system (like the one I'm using, where Logic and the OS are both 32-bit)?

 

Yes, though it's actually less than a round 4Gb...keep in mind that Logic itself, plus the OS, use up RAM.

One thing though, you don't need to to boot your system (the kernel) in 64bit, only Logic (you do need Snow Leopard, though).

 

I ask because I have a song I can't even open any more with my 2GB of RAM, and am wondering whether grabbing 2GB more will help.

 

Yes, it will help. But these days, if you work with many sample based instruments, 4Gb is really not that much RAM. That's what I have at the moment, and it works for me...cause I use my RAM "responsibly". :wink:

 

J.

Link to comment
Share on other sites

Jordito, thanks so much for your help!

 

Usually BFD2 is the only virtual instrument I'm using, and at at this point I've actually bounced everything (including my BFD2 drums) to audio, so it's just plugin use that seems to be triggering memory alerts. I hope that's considered "responsible". ;)

 

One last question - are you saying that I need to be running Snow Leopard in order to address 4GB of RAM in Logic, even if I'm not running Logic at 64-bit?

 

I ask because I'm in the middle of a big mix project right now and would much rather just dump an extra 2GB of RAM into my machine than embark on an entire OS upgrade.

 

Thanks!

Link to comment
Share on other sites

Jordito, thanks so much for your help!

 

You're welcome!

 

Usually BFD2 is the only virtual instrument I'm using, and at at this point I've actually bounced everything (including my BFD2 drums) to audio.

Are you saying that I need to be running Snow Leopard in order to address 4GB of RAM in Logic, even if I'm not running Logic at 64-bit?

 

Then you should be fine with 4Gb of RAM, and no you don't need Snow Leopard to use that amount of RAM (or at least most of it). If your computer supported more than 4GB, say 16GB, in order to access those 16Gb's, you'd need SL and Logic running in 64bit mode.

 

 

so it's just plugin use that seems to be triggering memory alerts.

 

What version of Logic are you running?

Please add all your system specs to your signature, as per forum rules.

 

J.

Link to comment
Share on other sites

Thanks, Jordito. That sounds like an unworkable drag for the kind of projects I'm working on.

 

It's actually not that bad once you get used to it. I've almost forgotten what it was like having multiple plug in windows open now lol. BFD2 does open in the 32 bit bridge while running Logic in 64 bit mode, but it's no big deal. It has enabled me to run projects with a lot of software instruments and plug ins that wouldn't normally open without getting the low memory warning running Logic in 32 bit mode, so it's definitely an improvement on that. Once BFD3 comes along and it is 64 bit it will be even smoother I'm sure, but that sounds like it's still a fair way off according to the FXpansion forums and for now BFD2.1 works just fine in the 32 bit bridge.

Link to comment
Share on other sites

Yeah, it doesn't sound like working with 32-bit BFD2 would be such a problem, actually, but mixing with UAD plugs definitely would be.

 

I think I'm going to grab another 2GB of RAM today and cross my fingers that that will solve my problems for now. No jump to Snow Leopard or 9.1.

Link to comment
Share on other sites

Ack. Adding 2GB of RAM (to bring my total up to 4GB) does not solve the problem (I guess throwing $ at it rarely does ;).

 

I guess this isn't really about BFD2 anymore, but if anyone has an idea or two on what to try next, I'd appreciate it.

 

Sounds like your problem is related to that particular project. Could be project corruption...

 

You said that BFD2 is the only instrument your using. How large is the kit...or, how many instances of BFD2 are you using in that project?

 

J.

Link to comment
Share on other sites

No, at this point in the project I'm no longer using BFD2 at all - bounced all VIs to audio long ago.

 

However, I did just come across something on the LUG that seems to have helped: removing all the Flex Time audio from the project. Bouncing 5 FT tracks to plain vanilla audio lowered Logic's RAM consumption by an entire gig.

 

I then deleted (not just bypassed) all 7 of my old virtual instruments in the project, removed the plugins from those channel strips, deleted all unused audio from the project and deleted all hidden audio/midi regions from the arrange.

 

So far, so good - thanks again for all your help!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...