[Lmuse-developer] IMPORTANT: how does in-note-mapping for drum tracks work?

[Florian J. <flo...@we...>]

Hi

i'm addressing you, tim, because svn blamed/praised you for the changes 
deep in the recording stuff:
with revision 1085, you changed midi.cpp ("engine fixes").

how does midi-in-mapping work?

i found the buildMidiEventList function, and the processMidi function 
(both in midi.cpp)
both functions deal with the "enote".

i know that the "pitch" stored in the event list, the pitch causing that 
event to be recognized (in-note/enote) and t5he pitch played 
(out-note/anote) are or at least can be different.

but at which place is the "in-note" -> "stored note" mapping one? in 
buildMidiEventList or in processMidi?
as i said, both deal with "enote", so i am confused.

what i want to do is to respect the "in-note" for my "new-style drum 
tracks" while recording.
my "new-style drum tracks" are basically the following: stored pitch and 
out-note are the same (thus, out-note is actually ignored). stored 
channel/port is ignored, the track's channel/port is used instead.



also, what must i do for step-recording and midi-echoing to respect the 
enotes?



could also remove the "one enote at a time" limitation? i know it 
usually makes sense, but the way the drum list handles this makes it 
hard to set up the enotes as i want.

for example, if i increase the enote several times, it changes all other 
enotes on my way, which really sucks.
can we instead make it NOT change other enotes except the one i'm 
editing currently, and maybe make the field red when there are duplicates?

greetings
flo