Has anyone in this group ever worked on the midi internals?

[Redwood (Daniel)]

It looks like the primary work was done by Jan over 10 years ago. Since then, 
the changes seem such that no architectural understanding was required.

Jan, are you available to advise? My goal is add in more details from the score 
to the midi output. This would include what articulate.ly does and more and 
better. That’s the goal.

I see these files:

./lily/midi-stream.cc
./lily/include/midi-stream.hh
./lily/include/midi-item.hh
./lily/include/midi-chunk.hh
./lily/include/midi-walker.hh
./lily/midi-control-function-performer.cc
./lily/midi-walker.cc
./lily/midi-item.cc
./lily/.midi-chunk.cc.swp
./lily/midi-chunk.cc
./scm/midi.scm
./python/midi.c
./ly/midi-init.ly

Along with many supporting midi scripts and so on. From what I can see every 
level of source, from .ly to .scm to .cc is involved (but that may be true of 
everything in lilypond). I’m an experienced C++ programmer, with a dabbling 
knowledge of Lisp, and a user’s knowledge of .ly.

There’s a lot to penetrate. I’m trying to get a sense of the flow of events, 
and some advice would mean a lot. Perhaps Jan no longer recalls the 
architecture for midi?

-d