midi2ly on mac: midi.so wrong architecture

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

midi2ly on mac: midi.so wrong architecture

Flaming Hakama by Elaine
> I am not top posting

I am reporting a problem from the facebook group,
someone trying to use midi2ly on mac.

It also failed for me on 3 different macs.

So, I entered it on lilytestissues as:
#5151 midi2ly on mac: midi.so wrong architecture



Their report was:

Hi! When a try a midi2ly, I get this:
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
/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so:
mach-o, but wrong architecture
Any idea of the problem?
Thanks!



My initial tests resulted in a similar error about wrong architecture on
one (OSX 10.11.6).   (The other one resulted in an error "RuntimeWarning:
Python C API version mismatch for module midi: This Python has API version
1013, module midi has version 1012" (OSX 10.9.5)--that one is likely my
fault due to a failed attempt to build lilypond dependencies.)


Here is an MWE of sorts, a round trip from lilypond to midi, then running
midi2ly on that midi file.  Also, to show the midi file was reasonable, I
imported it into a DAW and bounded it as an mp3.

The error on the mac for this example (OSX 10.11.5) was:
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



%%% File: fifth-and-back.ly %%%
\version "2.19.15"

#(define output-suffix "output")
\score {
    <<
        \relative c'' {
            \tempo "Allegro con brio" 4=144
            \time 2/4 r8 g8\ff [ 8 8 ] | ees2 ~ | 2 |
        }
    >>
    \layout { }
    \midi { }
}


command line:
$ lilypond fifth-and-back.ly

fifth-and-back-output.pdf is attached
fifth-and-back-output.midi is attached.
Here is the contents of the midi file when looking in a text editor:

4d54 6864 0000 0006 0001 0002 0180 4d54
726b 0000 0053 00ff 030d 636f 6e74 726f
6c20 7472 6163 6b00 ff01 0963 7265 6174
6f72 3a20 00ff 011e 474e 5520 4c69 6c79
506f 6e64 2032 2e31 392e 3135 2020 2020
2020 2020 2020 00ff 5804 0202 1208 00ff
5103 06ef 9100 ff2f 004d 5472 6b00 0000
3a00 ff03 055c 6e65 773a 00b0 0764 8140
b007 6400 9043 6581 4090 4300 0090 4365
8140 9043 0000 9043 6581 4090 4300 0090
3f65 8c00 903f 0000 ff2f 00



Now, running midi2ly on the file fifth-and-back-output.midi

$ midi2ly fifth-and-back-output.midi
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



Please let me know what else I should do to register the bug properly, as
this is my first attempt.



David Elaine Alt
415 . 341 .4954                                           "*Confusion is
highly underrated*"
[hidden email]
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel

fifth-and-back-output.pdf (49K) Download Attachment
fifth-and-back-output.midi (232 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: midi2ly on mac: midi.so wrong architecture

ElRay
> I am not top posting

FYI:  This has been reported as a bug -- in 2012.I will see if this is something I can take-on in the next month or two.
dak
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: midi2ly on mac: midi.so wrong architecture

dak
ElRay <[hidden email]> writes:

>> I am not top posting
>
> FYI:  This has been reported as a bug -- in 2012.I will see if this is
> something I can take-on in the next month or two.

I am pretty sure that Graham posted a patch for this on one of the lists
one of the last times this was being discussed.

--
David Kastrup

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: midi2ly on mac: midi.so wrong architecture

ElRay
>> I am pretty sure that Graham posted a patch for this on one of the lists
>> one of the last times this was being discussed.

Tracking on that, but it's been 5 years since the ticket was opened and the patch hasn't made it into the release (or it did and was re-broken), so I'd like to do what I can to drive it home.  I'd rather not "homebrew" a stand alone midi2ly and keep using that in parallel to the regular Frescbaldi/LilyPond workflow.

Ray
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: midi2ly on mac: midi.so wrong architecture

Carl Sorensen-3
On 7/28/17 3:09 PM, "lilypond-devel on behalf of ElRay"
<lilypond-devel-bounces+c_sorensen=[hidden email] on behalf of
[hidden email]> wrote:

>>> I am pretty sure that Graham posted a patch for this on one of the
>>>lists
>>> one of the last times this was being discussed.
>
>Tracking on that, but it's been 5 years since the ticket was opened and
>the
>patch hasn't made it into the release (or it did and was re-broken), so
>I'd
>like to do what I can to drive it home.  I'd rather not "homebrew" a stand
>alone midi2ly and keep using that in parallel to the regular
>Frescbaldi/LilyPond workflow.

It seems like the "patch" on issue 2208 is less of a patch and more of a
workaround.

I think that fixing this problem will require changing GUB, but I'm not
competent enough in GUB work to even know whether I'm right in thinking
this.

Carl


_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Loading...