BFD3.1.0.16

BFD3.1.0.16 - Public Beta - Introducing the BFD Demo Pack panel, BFDLACTool, VCA Comp, and more...!

Hi everyone,

There is a new public beta in your user-area that introduces several new features for BFD3:

- Demo Pack panel, where users can download demos of our expansion packs. The currently selection is as follows:
Eldorado
Percussion
Deluxe
Jazz & Funk
Oblivion
Sabian Digital Vault
Sleishman Snares
Sleishman Drums
Kabuki & Noh
Zildjian Digital Vault

We plan to expand the range over the coming months.

- BFD3 now has an additional application called BFDLAC Tool. This is a tool that can take your WAV format versions of your expansion pack content, and losslessly compress them to our BFDLAC format. This process is not reversible, and the resulting files cannot be used with BFD2 or BFD Eco. Use at your own discretion. But it'll help save you a lot of disk space, and improve disk streaming performance!

- There is now a new compressor available in the plugin called VCA Comp. This compressor offers a cleaner more clinical alternative to our character compressors. Featuring large ranges for ratios and threshold levels, it is akin to a semi-digital 80s VCA compressor. Launch the tool from the Tools menu item "Launch BFDLACTool...".

- 24 new full presets and kits from PopGuru.

- Various crash and bug fixes, optimizations, improvements, notably:
- buffer sizes of 4096 should now work if you have an SSD drive - this can massively improve loading time, memory use.
- Support for AVX2 instructions (512bit vector maths).
- drum kit view will now start a 2nd tier of toms and cymbals if your kit size tends towards "Terry Bozzio".

 

BFD3.1.0.20 now available - Introducing the BFD Demo Pack panel, BFDLACTool, VCA Comp, and more...!

 

hoping it will work. 3.0.46 did not work for me, had lots of crashes and bugs, such as NOT BEING ABLE TO OPEN WHEN RELOADING A PROJECT and...hoping it will be on sister AZ soon

 

you are dreaming too much it seems

 

can you tell me why?

 

thats why , really a lot of people gets tired to read such things over and over

if you really need this , buying it are an option , if not search for alternatives

 

I'm not whining. I just said, "hope" if not, no prob. Can not hope?

 

simply forget dreaming and hope when it comes to such things those days

 

running 3.1.020 here, and yes less crashes than 0.46 did. I do wish they would test a little better before public release.
I will say one thing, the bfdlactool is a bonified good idea

but in their defense.. if your not on the edge of crashing it, your not drumming hard enough

for folks who experience too many crashes, try turning down the load on your cpu. reduce the bit size, reduce RR and quality in settings etc. for when your running in real time. then turn them back up for bounce down

 

Last edited: Sep 14, 2015

yeah tx I set all the "engine" tab up

are you on legit?

 

yes legit. like most folks I've run bfd to the point of constant crash. of course, it jams like a boss why wouldn't we. but then I learned how to adjust the live play setting to balance between acceptable sound quality and not crashing. I think I run kick and hats at high quality, and snare toms and cym at mid quality. and 16bit. and turn down the round robins or something. sound is pretty good for my old crappy computer, surprisingly. I didn't know if it would run at all on this jalopy. but when I get a song together that I want to record down, I just turn it up to high quality and 24bit for the bouncedown.

I've also been plagued by the ol' crash crash when opening a project. it meant I had too much running at the save point. I just go back and freeze what Im not actively working on (or bouncedown for some)

nowadays, almost any given save point is everything frozen. the projects load super fast. then i just unfreeze what I want to work on.

btw, when I ran the bfdlactool it compressed 165g to 31.74%. 52g total. thats not just awesome, thats fnA-awesome

 

Last edited: Sep 15, 2015

tx for the reply. This is my situation: I've a laptop Acer Aspire V3-571G with i7-3632QM, 8GB RAM (updated some weeks ago, two banks of Corsair Vengeance, now in Dual Channel), the HDD is not so good, 750gb at 5400rpm. There is: I don't think that, for me, it is the load on the CPU. I run everyday a project with nearly 50 tracks, dozens of VSTi open and working (not freezed - 2 instancies of Kontakt, EZD2, mTron Pro, VB3, Lounge Lizard, 3 or 4 guitars of Ample Sound, lots of Guitar Rig working, and some other). Result: it opens in some minutes, yes, but NEVER a crash. I pushed CPU meter (Cubase) nearly to the limits, never a crash.

One day I installed BFD3, opened in this project, saved and reopen and...BAM! crash after crash. On 10 times I opened that project, maybe 8 or 9 crashed. And some times it gave me that error, 0x000000 or something...AND BFD3 is running so low on profile...with a 16 pieces kit, it only take 100mb of ram. But it still crashes. And, some of the settings in the engine tab do not even remain changed when I change them...I change a setting, then reopen the preferencies and PUFF the setting is newly at the value it was before.

I do not know how to make it safe

 

interesting what you say about bfd causing the crash. yes I believe you. hmm, might be sometimes theres a 'bad relationship' between one vst and the host daw. see if you can ask around Cubase people or bfd people. see if others have experienced this. I remember something about the oxooo error, but not sure what the cause or solution was. maybe search the bfd forum for that?
I've actually experienced a vst/hardware 'bad relationship' before too, so its tricky to diagnose

 

That Code is actually a pc memory error, check your settings / configuration in the Bios try to set to Auto with memory settings when ever possible

 

here on mac I have a lot of crashes with the bfd3 3.0.4.6 with Logic Pro X ..
I cannot use it really.. bfd2 it is very stable.. but I wish I could use bfd3 ..
I hope the update for bfd3 appear in audioz soon.

 

MIND YOUR LANGUAGE LASTENO....you could be banned

so a change of memory settings in BIOS could resolve this problem? and, what does "auto" mean? auto of what? tx again

 

up