On Tue, Dec 27, 2016 at 08:43:34AM +0100, k...@aspodata.se wrote: > Graham: > > That is correct; the python midi2ly conversion is quite > > independent of the rest of LilyPond. As a result, it is an > > excellent place to begin! :) > > So I propose that a better course of action would be to research
Thank you for the suggestion. At the moment, it appears that midi.c is broken on at least one architecture. Fixing it would be a pain, and would do nothing to reduce the problem it poses. Moving to a completely python solution would represent a solid step forward, both in terms of reducing technical debt, and also in terms of a new contributor getting familiar with our development process. At that point, an interested person -- perhaps yourself? -- could offer further patches which improved the quality of the lilypond code. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel