Hi,
It seems that SuperVP for Max does not work on machines that use Apple’s M1 chip. Is that correct, or have we just not tried hard enough?
If so, do there happen to be plans for a version that runs on them?
Thank you for the information!
Hi,
It seems that SuperVP for Max does not work on machines that use Apple’s M1 chip. Is that correct, or have we just not tried hard enough?
If so, do there happen to be plans for a version that runs on them?
Thank you for the information!
Hi,
Are you sure it’s not just a quarantine-related issue? I don’t have a M1 Mac, but I don’t see why Rosetta wouldn’t do its thing and it’s also often an issue with command-line tools in post-Catalina macOSes.
All the best,
António
Thank you for your reply. I too figured Rosetta should do its thing, but the Max console does say that it’s an architecture problem. I’ll look into the quarantine stuff when I get the chance.
Well, it turns out that the externals do work on versions of Max strictly older than 8.2. So this does not, or at least not solely, seem to be an issue with the M1 architecture. We’re just going to downgrade Max for now.
Hi,
From what I understand, from Max 8.2 (SDK linked), only objects compiled with the following options
-arch x86_64 -arch arm64
will be able to be loaded…
https://developer.apple.com/documentation/apple-silicon/addressing-architectural-differences-in-your-macos-code
We will make sure all externals on the forum are compiled with these options in the future (if it is not already the case yet)…
Thanks for reporting
Noted! Thank you for updating me.
Hi,
Is there any update on this? I was trying to run the patch for Saariaho’s Frises and had the incorrect architecture message for supervp~. (I see the last version of the patch is Oct 2020, so the version of the external in the patch predates Silicon). Would be nice to keep all these pieces going
John
Hi,
what architecture are you running on? Supervp is compatible Arm64 since November 2021. Have you tried the latest release v2.18.9?
Best
Riccardo
MacAir 10,1 (M1) but, yes, the patch has v2.18.6 …
Thanks for that.
John