New Apple M1 chips - MacBook Pro /Air /Mac mini

...Or maybe has someone tried Max with Big Sur?

Max 8.1.8 supports Big Sur with Intel machines. Apple Silicon is not officially supported yet. Under Rosetta, there are some currently known issues, which will be fixed in an updated version sometime in the next few months. We are working on a native Apple Silicon version of Max, but we do not have a timeline for when that will be released.

Can you confirm that a native Apple Silicon update is coming to Max 8?
Thinking about buying but would first like to make sure in case I upgrade to an Apple Silicon Mac in the coming year or two.

I'm actually curious what the improvement is with MSP. All anyone online can talk about is final cut pro.

@Audiomatt

Yep, I'm also thinking about the same topic. There is something called "High-efficiency audio processor" inside the M1 chip. But I couldn't find any information if this subsystem is exposed for developers and can be used to accelerate audio computations. If not, MSP will be, IMHO, more or less untouched by the transition to new chips (maybe a bit more robust if the new chip is really as fast as Apple says).

However I can imagine, that other parts of the M1 (accelerators for machine learning and "neuromorphic" calculations) can open some new possibilities for audio processing. Also the sneaky memory management (UMA) can be useful for better integration between MSP and non-MSP domains.

I got my new M1 mac mini yesterday and installed max straight away. After jumping through a few Big Sur security hoops, I ran my three main big patchers, 2 of which are mainly time stretchers (one for "studio" work and the other for live performance, with lots of usb midi controllers).
So far, absolutely no problems running the patchers. And I have the vector sizes set much lower (in fact, at the default settings) which I haven't been able to do for quite a long time on Intel Macs. Everything seems to be running smoothly and responsively. I don't do any video work, so I can't say if there are any problems there, but audio is looking good. I have a school workshop to run next week (as long as no-one at the school comes down with Covid!), so I'm going to try running that system on the M1 Mini. That involves sensors coming in via a Phidget 8/8/8 (I've already checked that that works), and USB midi, and DMX out over ethernet (the Enttec ODE seems to be working, but I haven't hung any lamps off it yet). That will give the processor a more serious workout. And I'll see if the computer remains as delightfully cool as it is at the moment!

I'd be interested to know ( @RobRamirez ) what the known issues with Max are, in case it affects anything I'm doing.

Edit: On running one of the patchers, I'm getting the following message in the Max Console. Anyone any idea what this is? ...

xebra_global . XEBListeningConnection_ListenProc: Error accepting connection: 670008 nodename nor servname provided, or not known

@david lower vector sizes are fantastic news. If I can get my VS down less than an mmillisecond I can stop obsessing over the friction of scheduler and audio rate ruining the groove.

that might have been the push I needed.

also, when you say you have a time stretched for studio work, are you saying it’s higher quality in nonreal time? I’d love a replacement for sera to pitch n time but it’s just the best sounding algorithm on the market.

I believe xebra is part of mira.

Ah. So that's probably because I don't have Mira active on my ipad.