Essential storage keeps the site and your preference working. Optional analytics help measure page visits and form journeys. Analytics are off until you choose.
Read the Privacy Policy or analytics and cookie information.
Current BeatCodex plugin build
Real MIDI pattern editing, drum mapping, velocity editing, and Beat Variants workflow.
MIDI drum workflow plugin
BeatCodex is a MIDI-only drum workflow environment for writing, editing, organizing, and translating drum parts across drum libraries, kits, and controllers.
Insert it before Kontakt or another drum sampler to preserve timing, velocity, notes, and articulations while adapting the MIDI for the target kit.
No audio engine or drum sounds. Every mapping stays editable, understandable, and deterministic.
Core idea
Most DAWs treat drum parts as generic piano-roll notes. That breaks when every sampler puts kicks, snares, hi-hats, cymbals, and articulations on different notes.
BeatCodex treats the pattern as drum intent first: rows, pieces, articulations, timing, velocity, sustain, and variants. The selected map decides where that intent should be sent in the target drum library.
Change the kit without giving up control of the groove.
Product
The first public BeatCodex layer is the drum map catalog: supported libraries, DAW-ready exports, library requests, and mapping corrections.
Product action
Find supported drum libraries and kit mappings in the public BeatCodex catalog.
Product action
Export mapping files for supported DAWs so drum lanes are easier to read and edit.
Product action
Tell us which drum library you need next so coverage grows around real user demand.
Product action
Submit missing notes, wrong articulations, or mapping fixes to improve the database.
Connected workflow
BeatCodex keeps editing, translation, live remapping, and pattern organization connected, while your existing sampler continues to provide the sounds.
Create and edit
Use the pattern editor and playlist to write, arrange, import, and export drum MIDI. Shape velocity, micro-timing, and Beat Variants without losing sight of the part.
Translate
Work from drum pieces and articulations rather than raw note numbers. Library-aware mappings and kit-aware workflows translate the same intent for the selected target.
Perform
Route live input through editable mappings, Drum Pad, and low-latency MIDI transformation before it reaches Kontakt or another drum instrument.
Organize
Use MIDI Vault and reusable patterns alongside factory and user mappings. The public catalog remains a place to request coverage and contribute corrections.
Workflow
The workflow stays simple: take in the groove, interpret it through BeatCodex, map it for the target kit, and export or play back the corrected result.
Step 1
Drum MIDI / live input
Step 2
BeatCodex drum intent layer
Step 3
Library / articulation map
Step 4
Target sampler / DAW export
Step 5
Correct playback
FAQ
No. BeatCodex does not make drum sounds. It sends MIDI to your existing sampler, drum library, DAW, or MIDI chain.
No. The public map catalog is the first public validation layer. The V0.1 alpha plugin already exists internally; public plugin access is being prepared through the beta program.
No. BeatCodex is focused on deterministic MIDI editing and translation. The goal is predictable control, not black-box generation.
