Oracle Sound DrumMIDI Mapper [WiN-MAC]

• Product: DrumMIDI Mapper
• Developer: Oracle Sound
• Version: 1.4
• Format: Standalone
• Requirements: Windows 10 or later, macOS 10.13 High Sierra or later
• Source: oraclesound.com/products/drummidimapper

Switching a full-song’s worth of drum MIDI from one library to another without a dedicated tool means dragging individual notes to new pitch positions one by one — toms land on crashes, hi-hats fire on china cymbals, and a groove that took an hour to program sounds wrong in the new kit. DrumMIDI Mapper exists specifically to close that gap: a desktop conversion tool that remaps drum MIDI between library maps in one pass, with bulk import and export for processing entire folders at once rather than one file at a time.

Key Takeaway

DrumMIDI Mapper converts drum MIDI between incompatible library maps in one pass — drag in a file, select source and target, drag the converted file straight into the DAW. It’s a utility for producers who switch between drum libraries on the same project; anyone who works with a single library and never crosses maps has no problem it solves.

Source and Target, Then Done

Conversion works from two selections — source map and target map — with the converted file dragging directly into the DAW, a folder, or the desktop via native drag-out once it’s done. No intermediate export dialog, no bouncing to a temp location first. Drag in, select, drag out.

Bulk import and export processes entire folders rather than requiring each file individually. A full song’s worth of grooves and fills for one library converts to another in a single operation, which is the workflow the tool is actually built around — not one groove at a time, but a whole project’s MIDI in one pass.

What the Articulation Table Shows

A visual articulation routing table displays exactly how each drum voice translates between the selected source and target maps before any conversion happens. The table covers:

• Note assignments for kicks, snares, toms, and cymbals
• Hi-hat articulations (closed, open, pedal)
• Chokes and off-center snare hits
• Rim and fallback logic for articulations without a direct match

Seeing the full routing before committing to a conversion matters most when the source and target libraries treat edge-case articulations differently — a china hit that doesn’t exist in the target map, or a cross-stick routed to a note the target uses for something else. The table surfaces those mismatches before the file is written, not after.

Fallback Logic Handles the Gaps

Drum libraries don’t share a common standard for where articulations live, and a direct note-for-note translation between any two libraries is rarely possible — some voices in the source have no exact equivalent in the target. DrumMIDI Mapper’s fallback routing handles those gaps automatically, applying intelligent substitution for toms, rims, hi-hats, cymbals, chokes, and off-center snares when a direct match doesn’t exist rather than dropping the note entirely or leaving it on the wrong pitch.

All maps use C1 = 36 as the shared kick-drum reference, enforced consistently across every supported library and DAW format. That single standard eliminates the specific mismatch — is the kick on C1 or C2 — that causes the most frequent remapping errors when moving MIDI between DAWs that number octaves differently.

Building and Importing Custom Maps

The Map Creator builds new library maps from scratch for kits and libraries not already in the app’s list. Existing maps load as templates to start from a known note layout, then modify from there rather than defining every articulation from zero. Finished maps export in DAW-compatible formats and import directly into the app’s own map list for use in future conversions.

The DAW Map Converter handles a separate problem: translating DAW-native drum maps between hosts — Cubase, Logic, Reaper, Studio One — with auto-detect available for identifying the source DAW format. This is a different workflow from the library-to-library MIDI Converter; a project moving between DAWs uses the DAW Map Converter, while a project switching drum plugins uses the MIDI Converter.

The trial linked at the top of this review was sourced from Oracle Sound’s own public product page, so the conversion and bulk export workflow described above is testable directly on your own MIDI files before purchasing. If that covers what the session needs, the full version is available at Oracle Sound’s store for a one-time $29.99 — no subscription, no conversion limits after purchase.

Rating: 4.1 / 5

• Workflow efficiency — 4.6/5: drag in, select maps, drag out covers the full conversion in three steps; bulk folder export handles whole-project MIDI in one operation.
• Articulation accuracy — 4.0/5: fallback logic handles mismatched articulations cleanly, though edge-case substitutions in the fallback layer won’t always land exactly where a human would route them manually.
• Library coverage — 4.2/5: the supported map list covers the main commercial drum libraries and DAW formats, with custom map import filling gaps for anything not in the default list.
• Value at price point — 4.5/5: $29.99 one-time with no conversion limits or subscription tier is straightforward pricing for a tool that replaces hours of manual work.
• Scope — 3.2/5: it does one job and does it well — producers expecting pitch correction, groove quantization, or velocity editing inside the same tool are looking at a different product.

Pros & Cons

Pros:

• Bulk folder export processes a full project’s MIDI library in one pass rather than requiring conversion file by file — the only way this workflow makes sense at real song scale.
• The articulation routing table shows exactly where every drum voice lands in the target map before anything is written, so mapping mismatches are caught before they’re committed.
• Custom map import means any library not in the default list can still be reached — the tool doesn’t go stale when a new drum plugin ships.
• One-time $29.99 with no conversion limits or subscription fees — the pricing matches what the tool actually is.

Cons:

• Fallback routing for articulations without a direct match is automatic rather than manual — the substitution choices are reasonable, but producers who want per-articulation control over how gaps get resolved need to go into the Map Creator and define the routing themselves.
• No velocity editing, groove quantization, or timing correction inside the tool — it converts what’s already there and leaves all feel and dynamics unchanged.
• Confirmed system requirements and supported formats weren’t findable at time of review — worth checking Oracle Sound’s product page directly before purchasing on an older system.

Editor’s Note: The bulk export is the actual feature here — converting one groove is a minor convenience, but dropping a full album’s drum MIDI into a folder and converting the whole thing to a new library in a single pass is genuinely different in kind from what manual remapping looks like. The Map Creator is the less-obvious bet: as new drum libraries ship, a user-built map gets the tool working with them immediately rather than waiting for an official update.

FAQs