Just go to https://www.synthchris.com/projects/drum-midi-converter/ to use the web app, or this page to download the latest release for the 64-bit Windows app. That's all there is to it!
- Drum MIDI Converter - Free, open-source applications to convert between drum MIDI mappings
- Build
- Add your own drum mappings
Table of contents generated with markdown-toc
This repository contains all of the source code necessary to build the Drum MIDI Converter. I will make a video explaining how to use it and explaining the backend. When I do, I will link it here.
This README is written for Linux systems, but can be run in any terminal that can use bash commands, assuming you have the following CLI tools installed:
- python3
- git
- cmake
- make
Clone this repository:
git clone https://github.com/lotkey/Drum-MIDI-Converter
I will refer to the cloned repo's directory as ROOT_DIR.
Clone the midifile library into ROOT_DIR/src-cpp/.
cd ROOT_DIR/src-cpp/
git clone https://www.github.com/craigsapp/midifileOptionally, remove all the unnecessary stuff:
cd midifile
rm -rvf !("include"|"src")
rm src/Options.cpp
rm include/Options.hYou should have the following structure:
ROOT_DIR
├── ...
├── src-cpp
| ├── mappings
| ├── midifile
| | ├── include
| | ├── src
| | └── ...
| └── ...
└── ...
You may need to change the include paths in the following files:
- MidiEvent.h
- MidiEventList.h
- MidiFile.h
- Binasc.cpp
- MidiEvent.cpp
- MidiEventList.cpp
- MidiFile.cpp
- MidiMessage.cpp
For example, change from:
#include "MidiFile.h"
#include "Binasc.h"To:
#include "src-cpp/midifile/include/MidiFile.h"
#include "src-cpp/midifile/include/Binasc.h"ii. Qt & Qt Creator
Download and install Qt Creator. If any issues come up, I recommend following this YouTube guide:
Open Qt Creator. On the top menu, select File > Open File or Project.
Open ROOT_DIR/src-cpp/DrumMIDIConverter.pro. If prompted, configure the project with a kit.
Build the project for your system. For Windows, you can follow this tutorial:
Install dash with the following command:
python3 -m pip install dashii. mido
Install mido with the following command:
python3 -m pip install midoRun the following command to run the Dash app:
python3 ROOT_DIR/src-python/app.pyIf the mapping you are adding has kit pieces that are not in the tree, you will need to add some kit pieces to the tree. The tree is located at ROOT_DIR/src-cpp/mappings/tree. This tree is used to generate the Keys namespace, which is used to create mappings.
RULES:
- Each root has it's own text file. These roots are completely separate, there is no crossover, and the kit pieces under one root cannot replace or substitute kit pieces under any other root.
- Defaults have an *asterisk* in the beginning of the name
- Indent with spaces, and keep the amount of spaces consistent in each text file
Update the tree folder to fit your needs. This could include:
- Reorganizing the tree
- Adding kit pieces
- Creating roots
I have included a program to automate updating the Keys namespace from the tree. You will need to build app from the source code and then run it.
To build the program:
cd ROOT_DIR/update-mappings/
cmake .
makeThis will build an executable called "update." To update the Keys namespace with the current tree, run the following:
ROOT_DIR/update-mappings/update --keysIf you reorganized the tree or removed some kit pieces, the other mappings will not compile. You will need to update them to use the current Keys namespace.
Mappings.hpp is located at ROOT_DIR/src-cpp/mappings/Mapping/Mappings.hpp. It contains the Mappings namespace. This is where you should add your function prototype.
Conventions:
- Each company has its own namespace inside the Mappings namespace
- If a product has a single mapping, then it has a function inside the company's namespace named "get{product name}Mapping()"
- If a product has multiple mappings, then it has a namespace inside the company's namespace that will contains functions for each mapping, each with the name "get{product name}{mapping name}Mapping()"
- Every function takes no arguments and returns a Mapping
Each mapping has its own source file in the Mappings folder located at ROOT_DIR/src-cpp/mappings/Mappings/.
Conventions:
- Each company has its own folder inside the Mappings folder
- If a product has a single mapping, then it has a C++ source file inside the company's folder named "{product name}.cpp"
- If a product has multiple mappings, then it has a folder for the product with C++ source files inside for each mapping, each with the name "{mapping name}.cpp"
If you follow the conventions, then you must create a new source file. The source file will include some headers and define the function like so:
#include "../../../Parsing/Keys.hpp"
#include "../../Mapping.hpp"
#include "../../Mappings.hpp"
#include "../../../Midi/MidiNote.hpp"
Mapping Mappings::CompanyName::getMappingNameMapping() {
return Mapping("CompanyName MappingName", {
// Each mapping maps a key onto a group of notes
// {Keys::..., {{Note::..., ...}, {Note::..., ...}}},
// {Keys::..., {{Note::..., ...}}}
// Here are some example mappings
{Keys::Cymbal::Bell::Crash::_1, {{Note::A, 3}, {Note::D, 4}}},
{Keys::Cymbal::Hit::China::_1, {{Note::F, 4}}}
});
}The CMakeLists file is located at ROOT_DIR/update-mappings/CMakeLists.txt. Inside the add_executable part, add the path to the new source file.
cmake_minimum_required(VERSION 3.13)
project(update)
set(CMAKE_CXX_STANDARD 20)
add_executable(update
${CMAKE_CURRENT_SOURCE_DIR}/update.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Helpers/stringpp.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Mapping/ConversionMap.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Mapping/Mapping.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Mapping/Mappings.cpp
# Like so ---
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Mapping/Mappings/CompanyName/MappingName.cpp
# -----------
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Mapping/Mappings/Drumforge/Bergstrand.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Mapping/Mappings/Drumforge/Ultimate.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Mapping/Mappings/GeneralMIDI/GmStandard.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Midi/MidiNote.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Midi/MidiNoteGroup.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Parsing/ParseTree.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/mappings/Parsing/ParseTreeNode.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/midifile/src/Binasc.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/midifile/src/MidiEvent.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/midifile/src/MidiEventList.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/midifile/src/MidiFile.cpp
${CMAKE_CURRENT_SOURCE_DIR}/../src-cpp/midifile/src/MidiMessage.cpp
)Add a line to Mappings.cpp located at ROOT_DIR/src-cpp/mappings/Mapping/Mappings.cpp.
#include "./Mappings.hpp"
#include "../Midi/Note.hpp"
// Converts from Yamaha standard to integer
uint8_t Mappings::yamahatoi(const Note& note, const int8_t& octave) {
return 12 * (octave + 2) + (int)note;
}
std::map<std::string, Mapping> Mappings::getAllMappings() {
using namespace Mappings;
auto nameMapPair = [](const Mapping& map) {
return std::pair<std::string, Mapping>(map.name(), map);
};
std::map<std::string, Mapping> map = {
nameMapPair(Mappings::Drumforge::getBergstrandMapping()),
nameMapPair(Mappings::CompanyName::getMappingNameMapping()) // like so
};
return map;
}After that, the C++ app will be completely updated.
If you want the Python app to have the new mapping, you will have to update conversions.lkcmap, located at ROOT_DIR/src-python/conversions.lkcmap. You can use the update program from earlier, but you will need to update that as well.
Update and run the update program:
cd ROOT_DIR/update-mappings/
cmake .
make
./update --cmapsAfter that, the Python app will be completely updated.