Graham: > On Wed, Dec 28, 2016 at 08:21:58PM +0100, k...@aspodata.se wrote: > > > At that point, an interested person -- perhaps yourself? -- could > > > offer further patches which improved the quality of the lilypond > > > code. > > > > Well, I'm working on theese: > > http://turkos.aspodata.se/git/musik/bin/miditoly.pl > > http://turkos.aspodata.se/git/musik/bin/midi_to_lilypond.tex > > Hmm. At the moment, there is no perl used in user scripts in > lilypond, and thus we do not distribute a perl interpreter as part > of our application bundle. Adding perl would be a significant > complication.
Yes, I know, that is why I haven't offered it for inclusion. > That said, I'm quite willing to believe that your experience with > miditoly.pl could help inform the conversion process in midi2ly.py > -- what types of quantization work best, or how to decide which > accidental to use, etc. Once we have the basics working, Joe may > want to investigate more advanced techniques. That is why I started on the tex file, so that someone else could grasp the issues and implementation choises. Regards, /Karl Hammar ----------------------------------------------------------------------- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
