There are two meta-events missing, Device Name and Program Name, that
were defined in Recommended Practice (RP-019).
They are:
FF 09 len textDEVICE NAME
FF 08 len text PROGRAM NAME
Both are similar to the TEXT meta event in contruct. For details of
their use see www.midi.org. The d
The current midi2ly.py contains the follwing todo items which are of
interest to me:
1 test on weird and unquantised midi input (lily-devel) -- is there a
file or files that can be used?
2 do not ever quant skips -- don't understand what is meant
3 drop c++ midi2ly -- replace with Python co
I made my improvement available at the following url:
http://www.amwoodproducts.com/midi2xml.py
The name reflects the fact that it will also produce MIDIXML files.
There is obviously much to add. It seems to work technically but I doubt
that
the output of my test would be readable. Splitting long
I working on a new process for creating .ly files from MIDI. My current
algorithm was able to produce the following, but it seems to fall down
at 4 polyphonic voices.
<<{f,2} \\ {r4 c'4} \\ {r4 g8 f8}>> <<{c,2} \\ {r4 4}>>
I have another algorithm in mind yet to try and would like to have a
g
