Tangentially, this was surprising
The system prevents you from mixing
arm64 code and x86_64 code in the
same process. Rosetta translation
applies to an entire process,
including all code modules that the
process loads dynamically.
I mean, it's literally the same DMG from way back when and there's no chance it doesn't run under Rosetta, but I run Ableton natively!
Seems like you're trying to load an Intel-only plugin binary in a native ARM application. This doesn't work. DAW and plugins must use the same archicture. You would either have to run Ableton in Rosetta or use a plugin bridge. (This is similar to Windows if you want to run 32-bit plugins in a 64-bit DAW.)
AU plugins work, the AU framework itself spins up a separate process to host the translated Intel plugin.
That's actually what's going on, it turned out -- I'm using the AU version of the plugin, Activity Monitor lists an Intel process when I add it to a track.
Not sure this will be of any help to my projects once Rosetta 2 gets sunsetted...
Yes, that's how you do it. I have written a VST plugin host for Pure Data and SuperCollider and it supports sandboxing/bridging. It's not rocket science. I'm not sure why Ableton never bothered to implement this.