New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin version mismatch gives uninformative error #3305

Closed
muellmusik opened this Issue Nov 21, 2017 · 11 comments

Comments

Projects
None yet
2 participants
@muellmusik
Contributor

muellmusik commented Nov 21, 2017

Just helped a user resolve an issue with a mismatched version of sc3-plugins. She got:

*** ERROR: dlopen '/Users/.../Library/Application Support/SuperCollider/Extensions/SC3plugins/AmbisonicUGens.scx' err 'dlopen(/Users/.../Library/Application Support/SuperCollider/Extensions/SC3plugins/AmbisonicUGens.scx, 2): no suitable image found.  Did find:
            /Users/.../Library/Application Support/SuperCollider/Extensions/SC3plugins/AmbisonicUGens.scx: unknown file type, first eight bytes: 0x4D 0x5A 0x90 0x00 0x03 0x00 0x00 0x00
            /Users/.../Library/Application Support/SuperCollider/Extensions/SC3plugins/AmbisonicUGens.scx: unknown file type, first eight bytes: 0x4D 0x5A 0x90 0x00 0x03 0x00 0x00 0x00

Needless to say, this is less than ideally informative. Perhaps a warning to check your plugins are the right version would be helpful for those who haven't memorised the bytes? ;-)

@brianlheim

This comment has been minimized.

Show comment
Hide comment
@brianlheim

brianlheim Nov 21, 2017

Member

@muellmusik is this with supernova?

Member

brianlheim commented Nov 21, 2017

@muellmusik is this with supernova?

@muellmusik

This comment has been minimized.

Show comment
Hide comment
@muellmusik

muellmusik Nov 21, 2017

Contributor

scsynth

Contributor

muellmusik commented Nov 21, 2017

scsynth

@brianlheim

This comment has been minimized.

Show comment
Hide comment
@brianlheim

brianlheim Nov 21, 2017

Member

What OS? What version of SuperCollider? What version of the plugins?

Member

brianlheim commented Nov 21, 2017

What OS? What version of SuperCollider? What version of the plugins?

@brianlheim

This comment has been minimized.

Show comment
Hide comment
@brianlheim

brianlheim Nov 21, 2017

Member

This does not seem like simply a versioning issue to me. This error message would be posted before the version is checked. Perhaps the plugins are meant for a different OS?

Member

brianlheim commented Nov 21, 2017

This does not seem like simply a versioning issue to me. This error message would be posted before the version is checked. Perhaps the plugins are meant for a different OS?

@brianlheim

This comment has been minimized.

Show comment
Hide comment
@muellmusik

This comment has been minimized.

Show comment
Hide comment
@muellmusik

muellmusik Nov 21, 2017

Contributor

3.9 beta, OSX.

Don't know version of plugins, but they ended in scx, so shouldn't have been another OS. She tried both downloaded and built from source. I downloaded the 3.9 beta plugins and then was fine.

Contributor

muellmusik commented Nov 21, 2017

3.9 beta, OSX.

Don't know version of plugins, but they ended in scx, so shouldn't have been another OS. She tried both downloaded and built from source. I downloaded the 3.9 beta plugins and then was fine.

@brianlheim

This comment has been minimized.

Show comment
Hide comment
@brianlheim

brianlheim Nov 21, 2017

Member

here's a related SO post: https://stackoverflow.com/questions/1924452/what-can-cause-dlopen-no-suitable-image-found-cant-map

I would recommend trying out file like that first answer suggests. It sounds like the dylib is in the wrong format somehow.

When I try this out on my system, which is AFAICT the same (except that I don't know how our OS versions compare; I'm on 10.13 beta), I get the expected API version message. So I cannot reproduce or investigate this locally. If you have the problematic file itself somewhere, that could be useful!

Member

brianlheim commented Nov 21, 2017

here's a related SO post: https://stackoverflow.com/questions/1924452/what-can-cause-dlopen-no-suitable-image-found-cant-map

I would recommend trying out file like that first answer suggests. It sounds like the dylib is in the wrong format somehow.

When I try this out on my system, which is AFAICT the same (except that I don't know how our OS versions compare; I'm on 10.13 beta), I get the expected API version message. So I cannot reproduce or investigate this locally. If you have the problematic file itself somewhere, that could be useful!

@muellmusik

This comment has been minimized.

Show comment
Hide comment
@muellmusik

muellmusik Nov 22, 2017

Contributor

Here ya go. I can reproduce with this. 3.9 dev, OS 10.12.16

AmbisonicUGens.scx.zip

Contributor

muellmusik commented Nov 22, 2017

Here ya go. I can reproduce with this. 3.9 dev, OS 10.12.16

AmbisonicUGens.scx.zip

@muellmusik

This comment has been minimized.

Show comment
Hide comment
@muellmusik

muellmusik Nov 22, 2017

Contributor

Hmm...

file /Users/.../Library/Application\ Support/SuperCollider/Extensions/AmbisonicUGens.scx 
/Users/.../Library/Application Support/SuperCollider/Extensions/AmbisonicUGens.scx: PE32+ executable (DLL) (console) x86-64, for MS Windows

Don't know why it's named .scx rather than dll then.

Contributor

muellmusik commented Nov 22, 2017

Hmm...

file /Users/.../Library/Application\ Support/SuperCollider/Extensions/AmbisonicUGens.scx 
/Users/.../Library/Application Support/SuperCollider/Extensions/AmbisonicUGens.scx: PE32+ executable (DLL) (console) x86-64, for MS Windows

Don't know why it's named .scx rather than dll then.

@brianlheim

This comment has been minimized.

Show comment
Hide comment
Member

brianlheim commented Nov 22, 2017

@brianlheim

This comment has been minimized.

Show comment
Hide comment
@brianlheim

brianlheim Nov 30, 2017

Member

Closing as user error. Feel free to reopen if you disagree or have an idea for a fix that could avoid this problem in the future.

Member

brianlheim commented Nov 30, 2017

Closing as user error. Feel free to reopen if you disagree or have an idea for a fix that could avoid this problem in the future.

@brianlheim brianlheim closed this Nov 30, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment