[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 834 in lilypond: midi2ly broken on Windows systems
From: |
codesite-noreply |
Subject: |
Issue 834 in lilypond: midi2ly broken on Windows systems |
Date: |
Fri, 28 Aug 2009 19:16:03 +0000 |
Status: Accepted
Owner: v.villenave
Labels: OpSys-Windows Bounty Usability Type-Defect Priority-Medium
New issue 834 by v.villenave: midi2ly broken on Windows systems
http://code.google.com/p/lilypond/issues/detail?id=834
This has been reported for years, and reproduced with 2.6, 2.8, 2.10, 2.12
and 2.13, on various Windows systems so I'm guessing it actually never
worked.
Any invocation of midi2ly (with a mingw build) fails with the following
message:
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:
/home/lilydev/vc/gub/target/mingw/src/python-2.4.2/Objects/listobject.c:243:
bad
argument to internal function
However, midi2ly does work on OSX and GNU/Linux. I suspect that some of the
bindings in midi.c are wrongly linked when compiling the dll.
(I know that such scripts are no longer supported, let alone on Windows
systems. But things like this might discourage newcomers, so as usual I am
personally willing to throw in a €50 bounty and/or double an existing
bounty to get a fully working midi2ly on all supported systems.)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 834 in lilypond: midi2ly broken on Windows systems,
codesite-noreply <=