Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
dev:edrumsupport [2016/04/02 19:33] glockedev:edrumsupport [2016/04/02 19:33] 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/Closing hihat seems to work like a statmachine +  Opening/Closing hihat seems to work like a statmachine 
-Some kits support stopping cymbals+  Some kits support stopping cymbals 
 + 
 +**Issue 1: Wrong midimapping**
  
-Issue 1: Wrong midimapping 
 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's interface like the following: Let's use a cymbal with id XY-123 as crash. We'd need a database which tells us the midi pitch of that component (e.g. 55). The UI could offer to match "XY-123" to "Crash with description" (supported by the specific DG kit, e.g. using pitch #49), so each #55 would be handled as #49. 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's interface like the following: Let's use a cymbal with id XY-123 as crash. We'd need a database which tells us the midi pitch of that component (e.g. 55). The UI could offer to match "XY-123" to "Crash with description" (supported by the specific DG kit, e.g. using pitch #49), so each #55 would be handled as #49.
  
 tba tba
dev/edrumsupport.txt · Last modified: 2016/04/02 19:50 by glocke
Trace:
GNU Free Documentation License 1.3
Valid CSS Driven by DokuWiki Recent changes RSS feed Valid XHTML 1.0