BFD3.5 - issues (Sept 2025)

Having used BFD3.5 for some time, I’ve noticed a few issues that need addressing yesterday, not next year.

When you import a sample, fine, you can assign a Snare to a Snare, a Kick to a Kick, a Cymbal to a Cymbal, a Tom to a Tom (though not high, mid, or low). But why, despite the manual claiming otherwise, is there still no way to assign articulations properly? Snare hits, rimshots, flams, side sticks, these should all land on the same snare, not float around in limbo. It shouldn’t be some massive “developer priority” to let users map articulations logically, it’s basic functionality.

The same logic applies to everything else: kicks (regular hits, flams), cymbals (hit, bell, choke), toms (hit, rimshot, flam, choke), and so on. Hi-hats are the worst offender: open, closed, ¼, ¾, pedal, choke… yet importing a hi-hat still dumps it into the “percussion” category, even though hi-hat is literally already its own category. Madness.

And here’s the kicker: every imported sample already shows up with “choke” as an articulation. Brilliant. So why not just make it actually work?

That one fix alone would let percussion-assigned hi-hats function properly, open hat chokes on a closed hat hit, giving a natural open/close feel. Revolutionary concept, I know.

Then there’s the image import fiasco since the last update. Before, images were assigned in a consistent format. Now it’s PNGs only, and every time I import an image it has to be backwards and upside down just to appear the right way up. Why should I have to run a gymnastics routine with every drum image just so I can see what I’m playing?

Slight gripe aside, BFD3 is still the most realistic drum software out there. I just need to remind myself, as a guitarist and keys player, that drummers can’t actually play four cymbals, a hi-hat, a kick, and a cowbell simultaneously. Sadly.

Oh I didn’t mention the occasional your “audio software is having a spasm reload or close” messages, which seems to have become part of the glory of using BFD3. Please make that stop!

3 Likes

I’m not sure I understand what you are saying, but I want to mention that any of the articulations can be assigned to different pads, OR they can be assigned to one pad and eash articulation can be assigned to a different velocity range. Or a combination of the two. Having said that, it should be easier and more intuitive to do. It’s a little laborious.

1 Like

The BFD3 sample import function automatically assigns choke to every imported sample, but unfortunately, it doesn’t actually work. Setting up individual articulations manually is tedious enough, but the current implementation feels unnecessarily complicated. Instead of something intuitive - like a menu where you can assign samples for hits, rimshots, and side sticks - you’re stuck in what feels like a “developers-only” maze.

If choke actually functioned as intended, imported samples would instantly become far more usable. After all, choke is just a simple close filter. Implementing it properly would allow anyone to take advantage of it without needing to write code or wrestle with programming logic.

For example, hi-hats imported into BFD3 are currently only assignable as percussion, which means they can’t open and close like real hi-hats. With functional choke, they could. Cymbals could be made to stop at defined points as well. In other words: no programming, no tinkering, no wasted hours - just a straightforward, musical workflow

1 Like

It is a pain with hi-hats for sure, but you can assign all of the hi-hat samples/pads to the same choke group, that’s how I do it. Ignore the default choke. Closed chokes open, as you would expect it to. I just end up with a bunch of percussions loaded for the hats, lots of channels in the mixer, so I send to an aux for processing.
I never understood why articulations weren’t supported for user samples either, we should be able to load any samples we want as an articulation of any of the drum sounds.

2 Likes