Re: BUG: Lilypond 2.18.2 and 2.18.36 fail on midi2ly in El Capitan

[Han-Wen Nienhuys]

Lilypond dev should know more

Op ma 8 feb. 2016 15:44 schreef pstone imap <
address@hidden>:

> Hi, I have implemented LilyPond output from MIDI files in Symbolic
> Composer.
>
> It has been working well for years, and runs through OS X 10.7.0-10.10.5.
>
> Now, El Capitan 10.11 breaks it.
> MIDI file is not anymore converted to .ly file.
> Error happens in both Lilypond 2.18.2 and 2.18.36 on OS X 10.11.1 and
> 10.11.3 used in testing.
>
> Here is example dump of converting MIDI file to .ly. Same error on both
> 2.18.2 and 2.18.36.
>
> calling midi2ly
>
> ; defaults write com.apple.versioner.python Prefer-32-Bit -bool yes (tried
> no option, too, same error)
>
> ; /Applications/Lilypond.app/Contents/Resources/bin/midi2ly
> --output='/Applications/Symbolic Composer
> 7.2/Projects/05.Snippets/Notation/Chain-transpose tester2 16.ly'
> '/Applications/Symbolic Composer
> 7.2/Projects/05.Snippets/Midi/Chain-transpose tester2 16.mid'
>
> error
>
> ; Traceback (most recent call last):
> ;   File "/Applications/Lilypond.app/Contents/Resources/bin/midi2ly", line
> 54, in <module>
> ;     import midi
> ; 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
>
> Do you know how to fix this? Are there any other parameters to midi2ly
> which would work in El Capitan?
>
> As said, Lilypond has been working remarkable stable, and it would be neat
> to continue using it.
>
> Peter
>
>