Heap-allocated strings are a common source of fragmentation and performance issues. The Bfd3 core library provides a fixed-capacity string that lives entirely on the stack (or inside any other object).

bfd3::FixedString<64> filename = "config_";
filename.append("data.bin");
const char* cstr = filename.c_str(); // null-terminated

The term "core" in Bfd3 core library is intentional. This is not a kitchen-sink framework. Instead, it provides the essential building blocks that other parts of an application—or even higher-level libraries—rely upon.

| Feature | BFD3 Core Library | Superior Drummer 3 (Core) | Addictive Drums 2 | | :--- | :--- | :--- | :--- | | Starting Point | Raw, unmixed, flat. | Natural but polished options. | Mix-ready, processed, "pop" sound. | | Workflow | Mixing/Engineering focus. | Songwriting/Library focus. | Quick/Instant gratification. | | File Size | Massive (High RAM usage). | Massive (Stream from disk). | Lightweight. | | Best For | Professional Mixers, Raw Rock/Indie. | Songwriters, All-rounders. | Demoing, Pop, Electronic. |

The library is inseparable from the BFD3 software engine, which was rebuilt from the ground up for this version.

The BFD3 Core Library is a highly structured, multi-mic, multi-articulation drum sample database. You can manually edit .bdrmap files to remap MIDI, create custom kits, or even build your own library, but you cannot bypass the BFD3 engine for mixing. Use the naming convention and XML structure to extend or repair libraries. For full control, export individual samples via drag-and-drop and rebuild in another sampler.

Would you like a template .bdrmap file or help writing a script to parse/auto-generate one from a folder of WAVs?

For network protocols or file I/O, endianness and padding matter. The core library offers binary streams with explicit byte ordering.

bfd3::BinaryWriter writer(bfd3::Endian::Little);
writer.write<uint32_t>(0x12345678);
writer.writeString("hello");
auto bytes = writer.data();

If an object with an intrusive list node is destroyed while still in a list, the list's next/prev pointers become dangling. Always remove before destruction.