On 25-Aug-05, at 9:15 AM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
Thanks for this info! The problem (and solution) appears on
OSX 10.3.9 as well.
Developers, can we modify scripts/midi2ly.py accordingly?
- Graham
Actually, I'm not sure what the status of this issue is. Technically,
Graham Percival wrote:
Thanks for this info! The problem (and solution) appears on
OSX 10.3.9 as well.
Developers, can we modify scripts/midi2ly.py accordingly?
- Graham
Actually, I'm not sure what the status of this issue is. Technically,
architecture independent stuff should go into /u
Thanks for this info! The problem (and solution) appears on
OSX 10.3.9 as well.
Developers, can we modify scripts/midi2ly.py accordingly?
- Graham
On 18-Aug-05, at 7:21 AM, John Mandereau wrote:
When I tried to run 2.6.3 midi2ly on Fedora Core 4, I got:
Traceback (most recent call last):
When I tried to run 2.6.3 midi2ly on Fedora Core 4, I got:
Traceback (most recent call last):
File "/usr/bin/midi2ly", line 42, in ?
import midi
ImportError: No module named midi
I fixed it:
I opened midi2ly.py and edited these lines:
libdir = '/usr/lib/lilypond/2.6.3'
if not os.path.isdir
