could not load due to incorrect architecture

klaus filip's icon

hi there
after updating to Max 8.2.0 many externals cannot be loaded resulting in the error above.
for example jeremy's
pattrexists: could not load due to incorrect architecture
what can i do, if not downgrading max?
its on apple M1 Big Sur.
thanks for any help
klaus

11OLSEN's icon

It was announced previously that externals will have to be recompiled to be compatible with m1.

klaus filip's icon

ah ok, i missed that.
the externals work fine though with Max 8.1.11 on M1 !

11OLSEN's icon

yeah, but I think 8.1.11 is not running natively on your m1 and therefore not using it's full potential.

klaus filip's icon

hmm, it seems that my 8.1.11 is running with rosetta, but the according checkbox is not showing in the finder-info window. max8.2 under rosetta also runs "fine".

11OLSEN's icon

Do the externals keep on working if you run 8.2 with rosetta?

klaus filip's icon

yes, the externals in question are all plain max (no msp or jitter).

Thierry Bernard's icon

Hi, quick question, I am having the same problem on Max 8.5.-- but as you said, it needs to be recompiled, but how do you process it?
Thanks a lot!

T./

Source Audio's icon

quick answer
you install Xcode, Max SDK, rewrite external sources for UB
architecture and then compile it.


Thierry Bernard's icon

Thanks Source Audio!
I'll give it a try..

Alexandre's icon

Resonators from cnmat don't work.. (last version i just downloaded) ... Same 'incorrect architecture' msg in the max window... Does someone have an idea how to make it work .? .. (there is 3 files in external cnmat folder) , not sure if there is maybe any kind of conflict of anything? ... resonators~.mxo , resonators~.mxe , and resonators~.mxe64 .) Thank you so much <3

Alexandre's icon

(...maybe it needs recompiling? ...i don't know how to compile source code, but if someone knows, that would be wonderful <3 )

Source Audio's icon

'incorrect architecture' msg in the max window... ????
which OS, which Max, which hardware ?
Current CNMAT externals v 1.0.5 and so
resonators~ have x86_64 AND arm64 architecture in mac version
32 & 64 bit on windows.
If you need ppc or i386 on mac , one can still get them somewhere...

but maybe you simply have uncompatible version for your hardware
somewhere in max search path

Alexandre's icon

Hey, thank you so much for the help! ... Here i have MacOS 12.5 / MacBookPro 16-inch 2021 M1-max 32Gb , and Max 8.5.3
And i had just DL the current version here : https://github.com/CNMAT/CNMAT-Externs/releases/tag/v1.0.4

Should this work or... ? ... I do get the error in the max window :
" resonators~: could not load due to incorrect architecture "
...everytime i try to load "resonators~.maxhelp"
(And I am sure it is the right external v1.0.4 in the search path because I erased all the older ones, to make sure)

Let me know what could i do <3

11OLSEN's icon

Just download the latest 1.0.5 as source audio advised

Source Audio's icon

1.0.5 is availabe through max package manager, or

https://github.com/CNMAT/CNMAT-Externs/releases

michel8's icon

after install CNMAT 1.0.5 through Max package manager, it works once – until I restart Max, then it says "could not load due to incorrect architecture". After reinstall the package it works again untill I restart Max, then the object get red again (it concerns the OpenSoundControl objects (maybe) only).

The latest download from CNMAT 1.0.4. for Apple Silicon also didn't work. Here It cause this topic with no succsess https://cycling74.com/forums/%22external-cannot-be-load-due-to-macos-quarantine%22
Terminal comand: xattr -cr "and drop whole bach folder on it" didn't help.

I try it also with no success, to run Max in Rosetta (although CNMAT is 64bit).

Later I just install the latest Max 8.6.4, same problem. MacOS 14.1 with M3.

What else can I do?!

Source Audio's icon

make sure that older versions of the package don´t exist

somewhere in max search path.

michel8's icon

Source Audio: make sure that older versions of the package don´t exist somewhere in max search path.

Thanks for the hint.
There were old (many years old) .mxo files (OSC-route.mxo) that were interfering. It's just strange that it hasn't played a disturbing role all these years long.