[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: midi2ly failure
From: |
address@hidden |
Subject: |
Re: midi2ly failure |
Date: |
Mon, 17 Dec 2012 18:29:40 +0100 |
On 17 déc. 2012, at 18:13, Ben Rudiak-Gould <address@hidden> wrote:
> On Sat, Dec 15, 2012 at 11:07 PM, address@hidden
> <address@hidden> wrote:
>> ImportError:
>> dlopen(/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so,
>> 2): no suitable image found. Did find:
>>
>> /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so:
>> mach-o, but wrong architecture
>
> Incidentally, why is the midi parser written in C? It seems unlikely
> to be a time bottleneck since midi files are normally pretty small,
> and there's a lot of additional per-note processing written in Python.
> If it's just that no one has had the time to port it to Python, then I
> volunteer.
>
Go for it - the code was written in 2001, maybe at a time when Python/computers
were slower than they are now. It's 500-ish lines, so good luck!
Cheers,
MS