Fixing e-drum mapping issues in Melodics (advanced)

If your electronic drums are connected but not triggering the correct sounds in Melodics — for example, the tom triggers a cymbal, or the hi-hat doesn’t open/close — it’s likely due to a mapping mismatch.

This guide walks you through two ways to fix it:

Option 1: Change the MIDI values on your drum module (easier)
Option 2: Edit your Melodics .json mapping file (advanced)

⚠️ This is an advanced guide. If you’re unsure about any steps, reach out to our support team — we’re here to help.

🔍 Start here: Quick checks before you dive in

Before changing MIDI settings or editing files, try these first — many issues can be resolved with one of these quick fixes.

1. Factory reset your module

If MIDI settings have been changed on your drum module, compatibility with Melodics will likely return after a factory reset. This is often the simplest fix. Check your drum module’s manual or manufacturer website for instructions.

2. Use a direct USB connection

If your kit has both USB and MIDI out ports:

Use direct USB wherever possible
Avoid MIDI-to-USB interfaces — they can prevent proper detection in Melodics (especially for hi-hats)

3. Use a good USB cable

Use a short, high-quality USB cable (USB 2.0 instead of 3.0 can help some Alesis kits)
Avoid USB hubs or extenders

4. Try reverting to default mappings

In Melodics → Settings → Devices, hit Revert all mappings to return to the default configuration. This resolves most issues for supported instruments. Do not use the "Map MIDI instrument" button for supported instruments.

📝 Instructions for specific kits

Alesis Strata / Strike
If you're using an Alesis Strata or Strike module, avoid creating a custom mapping using the "Map MIDI instrument" button in Melodics — it may cause compatibility issues. In most cases, reverting to default mapping is the fastest way to restore Melodics compatibility. Hit that "Revert all mappings" button in Melodics settings!

Yamaha DD-75
Sends note 40 for snare by default — which Melodics interprets as snare rim, not centre. Manually reassign the snare pad to note 38 to match the GM standard — more information below.

Roland TD-9
If your hi-hat isn’t working, set HH Compatibility to External in the module.

Roland SPD-SX and HPD Series
These controllers do not follow the GM standard. Adjust the MIDI settings to match the GM standard drum map for syncing with Melodics (Option 1), or edit your Melodics mapping file (Option 2).

✅ Option 1: Change the MIDI values on your drum module

Recommended for most people

Many drum kits let you manually assign what MIDI value is sent by each pad. The easiest fix? Set your kit to follow the General MIDI standard, which Melodics expects by default.

Many kits already use the General MIDI standard already, so a simple factory reset will fix most issues. Still having issues after factory resetting? Follow this guide.

🎯 Who this is for

Your drum module allows you to reassign MIDI notes
You’d rather not edit .json files

🎵 General MIDI drum map (Melodics-compatible)

Instrument	MIDI Value	Common Note
Kick	36	C1 / C2
Snare	38	D1 / D2
Snare Rim	40	E1 / E2
Low Tom	41 / 43	F1 / G1
Mid Tom	45 / 47	A1 / B1
High Tom	48	C2 / C3
Crash	49	C#2 / C#3
Ride	51	D#2 / D#3
Closed Hi-hat	42	F#1 / F#2
Open Hi-hat	46	A#1 / A#2
Hi-hat Pedal	CC #4	–
More MIDI info here

Example: Some kits send MIDI note 40 for snare. Melodics interprets this as the snare rim, so may not function as expected. This is applicable to kits like the Yamaha DD-75.

🛠 How to change MIDI values

Check your drum module’s manual or settings menu. You’re looking for a “MIDI Note Assign” or similar option per pad.

Change each pad’s MIDI output to match the table above.

🧠 Option 2: Edit your Melodics .json mapping file

Advanced – for experienced people

If you can’t change MIDI values on your module, or want more fine-grained control, you can manually edit your custom device mapping.

🧰 What you’ll need

Your .json mapping file from the Melodics devices folder
A code editor (e.g. Visual Studio Code)
A MIDI monitoring tool to check values (e.g. MIDI Monitor or MIDI-OX)
A JSON validator to avoid formatting errors

🔎 Step 1: Work out the MIDI value being sent

Use a MIDI monitoring app to find out what MIDI value is sent when you hit a pad.
Write it down for each misbehaving drum/cymbal.

Don’t rely on the note name (like C2) — different systems interpret octave ranges differently. Always use the MIDI value (0–127) which is what is required for Melodics .json mappings. You can change how the MIDI value is displayed in your MIDI monitoring app.

📝 Step 2: Edit your mapping file

Open the .json file in a code editor
Located here:
- macOS: ~/Library/Application Support/Melodics/Melodics/devices
  (Note this is in the "hidden" Library folder.)
- Windows: C:/Users/<username>/AppData/Local/Melodics/Melodics/devices
  (Replace <username> with your Windows username.)
- iPadOS: Look for the Melodics/devices folder in your Files app.
Can't see your mapping file? Make sure you made a mapping in Melodics by using the "Map MIDI instrument" button in settings.
Find the relevant instrument section
Search for "snare", "kick", etc.

Update the "note" value
Replace it with the MIDI value your drum is actually sending.
Example:

{
    "channel": 10,
    "events": [
        {
         "message": "snare",
         "type": "NoteOff"
        },
        {
         "message": "snare",
         "type": "NoteOn"
        }
    ],
    "instrument": "drums",
    "note": 38
},

Be careful editing your .json file — any small formatting errors like a missing comma may break it.

Repeat for all MIDI channels
Melodics mappings usually contain all 16 channels — focus on channel 10 if unsure, as this is usually the default channel for drums. Update them all for thoroughness.
Validate your file
Use JSONLint to catch any missing commas or formatting mistakes.
Save and restart Melodics
Your changes won’t take effect until you restart the Melodics app.

⚙️ Having hi-hat issues?

Is your hi-hat not opening or closing?

Hi-hats use Control Change (CC) data — usually CC 4 — to send pedal position info. But different kits behave differently, so you might need to add a filter to your mapping.

To add a hi-hat filter:

Look near the top of your mapping for:
```
"filters": [
],
```
Insert one of these filters (inside the square brackets):
- "HiHatNoteCorrection" – works for most kits
- "RolandHiHat" – for Roland kits
- "HiHatNoteCorrectionNoPedalNote" – for some specific Alesis models
Example:
```
"filters": ["HiHatNoteCorrection"
],
```
Save, validate, and restart Melodics. (Same as step 5 and 6 above.)

Using a MIDI-to-USB cable instead of direct USB? Melodics may not recognise your device and won’t auto-apply filters — this manual step is essential for Roland kits and some Alesis models.

🔄 Not sure which option to try?

You can…	Try this:
Change MIDI notes on your drum module	✅ Option 1 (easiest)
Can't change notes, or need fine-tuning	🧠 Option 2 (advanced)
Only your hi-hat isn’t working	Add a filter to the `.json` mapping file

💡 Final tips

Restart Melodics after any changes
Use MIDI values (0-127) when editing .json files, not note names
If things go wrong, validate your .json files before anything else
Speak to the Melodics support team if you get stuck — we're always here to help!

Connecting your electronic drums

Melodics app settings

Guide to Calibrating Acoustic Drums with Melodics

Connecting Your Drums to Melodics on iPhone