You are a guitarist. Or a bassist. Maybe a pianist. You make music content, and somewhere along the way you decided to add real-sounding drum tracks to your productions. You bought a drum VST, found a great MIDI pack online, dropped it into your project, and hit play.
Wrong sounds everywhere. Kick triggering a cymbal. Snare landing on a tom. Hi-hats completely missing. You checked the MIDI file itself and it looks fine. You checked your plugin and it is loaded correctly. So what is going on?
This is one of the most common frustrations in modern music production, and almost no one explains why it actually happens.
The Root Cause: Every VST Has Its Own Note Map
MIDI communicates through numbers. Every note on a piano keyboard corresponds to a specific number, from 0 to 127. When a drum VST receives a MIDI signal, it reads those numbers and decides which drum sound to trigger based on its internal note map.
The problem is that there is no universal standard for drum VSTs. Each developer decides independently which number triggers which drum sound. This means:
- Note 36 might be a Kick in GetGood Drums
- Note 36 might also be a Kick in EZdrummer, but the snare sits at a different number
- Note 36 in Addictive Drums 2 might be mapped to something else entirely
- Mixwave, Superior Drummer 3, MDL Tones, Krimh Drums: each one does it differently
So when you load a MIDI file that was programmed for Plugin A into Plugin B, every single note goes to the wrong destination. The MIDI data is technically perfect. It is just speaking the wrong language for your plugin.
Watch: See the Problem and Fix in Real Time
Before we go deeper, here is a full video walkthrough showing exactly how this problem happens and how to fix it using DrumRemap:
Why This Hits Content Creators the Hardest
If you are a guitarist or bassist who makes YouTube or social media content, you are especially vulnerable to this problem. Here is why:
- You are not a dedicated drum producer, so you rely on MIDI packs from various sources
- Those packs are almost always built for one specific plugin
- You switch drum VSTs based on deals, recommendations, or new sounds you discover
- Every time you switch, your existing MIDI breaks
The traditional solution is to open the piano roll, find every kick note, shift them all to the correct position in the new plugin, then do the same for the snare, hi-hat, toms, crashes, and ride. For a four-bar loop that takes about ten minutes. For a full song with verse, chorus, bridge, and fills, you are looking at an hour or more of mechanical work that has nothing to do with making music.
The Fast Fix: Automatic Remapping
DrumRemap was built specifically to solve this problem. Instead of editing the piano roll, you upload your MIDI file, select the plugin it was originally programmed for, select the plugin you are using now, and download a correctly mapped version. The whole process takes under a minute.
The tool supports 20+ drum libraries including all GetGood Drums variants, the full Mixwave lineup, Toontrack Superior Drummer 3, EZdrummer 3, XLN Addictive Drums 2, Bogren Krimh Drums, MDL Tones, RS Drums: The Monarch, Drum Forge, and General MIDI.
What the Remap Actually Does
When you select your source and target VST, DrumRemap reads every note in your MIDI file, looks up where that note sits in the source plugin's map, finds the equivalent position in the target plugin's map, and writes the corrected note to the output file. It does this for every single note simultaneously, preserving your velocities and timing exactly as they were.
After the Remap: Humanize and Velocity
Once your notes are in the right places, DrumRemap gives you two optional tools to shape how the drums feel before you even bring the file back into your DAW.
Velocity Scaling lets you adjust the overall intensity of the hits. If the pack feels too quiet or too aggressive for your mix, you can push or pull the velocities across the entire file at once.
Humanize adds subtle timing and velocity variations to make programmed drums sound less robotic. Start with small values. Even a 5ms timing shift on some notes is enough to make the groove breathe.
The Bigger Picture
This is not just about fixing a broken MIDI file. It is about making your entire drum workflow flexible. When you are no longer locked to one plugin, you can buy any MIDI pack regardless of what it was built for. You can switch VSTs mid-project without starting over. You can send a MIDI file to a collaborator running a different setup and know they will hear it correctly.
For content creators who produce music alongside their main instrument content, that flexibility is significant. It means less time troubleshooting and more time making content.