< Back to IRCAM Forum

Unrecognized Architecture

Antescofo
#1

Bonjour, after nine years I finally bought a new MacBook but unfortunately my favorite software component doesn’t recognize it (it’s an M4 Pro):

antescofo~: could not load due to incorrect architecture

I’m quite sure that it’s only because it doesn’t have the name of the system in its list.

Cordialement
Kai Yves

#2

Hello Kyl.
You need to take an antescofo~ object for Silicon. The zip file on the Forum provides both architectures (Silicon and x86). For simplicity’s sake, antescofo objects are not “FAT” libraries and you need to put the correct version of the object in Max’s external directory or next to your patch.
Jl.

#3

Hello Jean-Louis, thank you for swift reply. Yes, I installed the Max external from antescofo–1.0-599–Max_OSXarm64–240511.dmg. uname -m in the terminal gives “arm64”, but maybe the string checked by antescofo~ is a different one. Kai Yves

#4

Do you have several antescofo~ object in your Max path ?

In this case, the console has a warning messake similar to “you have multiple files in your search path with the name antescofo~.mxo”. If so, remove the unwanted antescofo~object from these paths.

If not, I am confused : the arm external is used routinely here.

#5

You’re right, there was a second antescofo~ object. However, there was no warning “you have multiple files in your search path…”, but the offending x86 object had been copied by Max to my recent project. I wasn’t aware of that. Sorry for the confusion and thank you for the hint.

#6

Hello, I am afraid that I am running into the same “incorrect architecture” problem with the newest antescofo–1.0-599–Max_OSXarm64–240511 object. I am on arm64 and can still open antescofo with a May 6 2021 version. What can I do? Thank you in advance for any suggestion.
Jarek Kapuściński

#7

Hello @jkapusci.
First, please double-check that there are no legacy versions of antescofo~ remaining in the folders where Max looks for externals (as per the previous discussion in this thread).

If that isn’t the issue, the problem might be related to how Max is launched. Could you look at which version of Max you are running and in which mode? Max is usually a “Universal” bundle, meaning it can run either in native ARM mode or via x86 emulation (Rosetta).

To check this:

  1. Right-click the Max application icon and select "Get Info."
  2. If the “Open using Rosetta” checkbox is selected, Max is running in x86 mode. In this case, you must use the x86-compatible version of the object.
  3. If you are running Max in native mode (ARM), the antescofo~ object—and all other externals—must be ARM-compatible.
#8

Thank you, Jean-Luis - it was indeed the issue with my new update to Max which was using Rosetta. All is working fin now.