Quoting liang seng <[EMAIL PROTECTED]> from ml.lilypond.bugs:
:Hi, I tested this on 2.6.3 and 2.7.18. Seems that nothing has been done to 
:fix this although I would think MIDI generation is not the main priority for 
:a music engraving program like Lilypond.

Says you, with all due respect! :-)

I use Lilypond to typeset my composition exercices, and when I compose for
a string quartet, I cannot easily play that on the piano and therefore I
rely on accurate MIDI generation to be able to get a feeling of how it sounds.

I'm therefore interested to contribute financially to the open-feature MIDI
refactoring.  There's no quote on that yet, but I'd be willing to put
50 EUR on the table to get a much better MIDI backend.

Finale has what they call "human playback" and a Lilypond MIDI output
which would include "accurately" things like staccato, pralls, trills,
arpeggios and all the accentuations you can think of would be very
helpful for me, as I prefer to use Lilypond over Finale (try to put
a Finale composition under CVS).

Anyone else interested into teaming up with me to match the (yet unknown)
price tag for the MIDI rewrite?

Raphael


_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to