It's a known problem for windows. http://code.google.com/p/lilypond/issues/detail?id=834
The info about different midi programs is interesting, though, and might help somebody fix it. If you can duplicate the problem using a very simply score (1 staff, 1 note, with 2 or 3 different programs), could you attach those files to that bug report? Sorry, - Graham On Sun, May 16, 2010 at 02:07:11PM -0700, Jonathan Townes wrote: > I'm encountering problems with midi2ly. I receive the error below when > running midi2ly on midi files exported from Reaper, a DAW. I receive > no error when converting midi files created by Lilypond or Anvil > Studio, a midi only program. Any insight or suggestions for exporting > midi would be greatly appreciated. > > C:\Documents and Settings\jt\Desktop>midi2ly Test8.mid > Traceback (most recent call last): > File "C:\Program Files\LilyPond\usr\bin\midi2ly.py", line 991, in ? > main() > File "C:\Program Files\LilyPond\usr\bin\midi2ly.py", line 989, in main > convert_midi (f, o) > File "C:\Program Files\LilyPond\usr\bin\midi2ly.py", line 823, in > convert_midi > for (dur, num, den) in global_options.allowed_tuplets: > SystemError: > /main/src/gub/target/mingw/src/python-2.4.5/Objects/listobject.c:255: > bad argument to internal function > > > Lilypond version 2.2.13-1 (Windows XP) > > _______________________________________________ > lilypond-user mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/lilypond-user _______________________________________________ lilypond-user mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-user
