Henning Hraban Ramm <lilypon...@fiee.net> writes: > Am 2014-01-27 um 16:43 schrieb Eluze <elu...@gmail.com>: > >> David Kastrup wrote >>> Uh, this is awkward, but you do know that the LilyPond distribution >>> comes with a program called lilymidi which you can use like >>> >>> lilymidi --pretty somefile.midi >>> >>> in order to get a readable representation of a Midi file? >> >> but - at least here - it doesn't produce more than the help information > > On my LilyPond 2.18.0 on OSX (Intel) 10.9 there’s a wrong MIDI library in > LilyPond: > > $ lilymidi --pretty something.mid > Traceback (most recent call last): > File "/Applications/music/LilyPond.app/Contents/Resources/bin/lilymidi", > line 250, in <module> > go () > File "/Applications/music/LilyPond.app/Contents/Resources/bin/lilymidi", > line 231, in go > midi_data = read_midi (midi_file) > File "/Applications/music/LilyPond.app/Contents/Resources/bin/lilymidi", > line 67, in read_midi > import midi > ImportError: > dlopen(/Applications/music/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so, > 2): no suitable image found. Did find: > > /Applications/music/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so: > mach-o, but wrong architecture
Ugh. Can we collect feedback on the various platforms? For me, stuff works fine. That would be Ubuntu 13.10 on i386. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
