This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:edrumsupport [2016/04/02 19:33] – glocke | dev:edrumsupport [2016/04/02 19:50] (current) – glocke | ||
---|---|---|---|
Line 2: | Line 2: | ||
We tested few E-Drum kits but got the following results: | We tested few E-Drum kits but got the following results: | ||
- | - Common midimaps are obeyed most time | + | * Common midimaps are obeyed most time |
- | - Opening/ | + | |
- | - Some kits support stopping cymbals | + | |
- | Issue 1: Wrong midimapping | + | Things we could implement: |
- | Some components do not map the common midimaps. I've faced a hihat on #26 (instead #42, #44 or #46) and a crash on #55 (supposed to be splash). We could introduce midimap configuration through the plugin' | + | * Fix midimapping in Plugin UI: Some components do not map the common midimaps. I've faced a hihat on #26 (instead #42, #44 or #46) and a crash on #55 (supposed to be splash). We could introduce midimap configuration through the plugin' |
+ | * Opening / closing a hihat seems to send metadata midi events to the computer. Those could be interpreted by DG using a seperate class '' | ||
- | tba | + | Missing things which could be fixed by hand |
+ | * If a song requires use of a china (e.g. #52) but the kit doesn' | ||
+ | * A song might contain doublebass parts (using alternating #35 and #36 for left and right kick drum). But a kit might have only one kick receiving component, so either #35 or #36 is used all the time. At the moment, my only idea would to fix this by hand, too. | ||
+ | |||
+ | **Experiment: | ||
+ | |||
+ | **Idea for checking an E-Drum-Kit: |