MPC Software on M1 Mac?

Has anyone got the MPC software working on an M1 Mac yet? Any issues?

I don't think so. You have to wait for an update from Akai.
It's like you want to run windows apps on your android phone. Different architecture.

I asked saintjoe , and he said it runs fine from what he can see.

NewAkaiUser wrote:I don't think so. You have to wait for an update from Akai.
It's like you want to run windows apps on your android phone. Different architecture.

Most Mac apps made for Intel work fine on M1 Macs though. Almost all of them, in fact. It seems that VSTs and some audio apps in particular have problems. Intel Mac apps run using Rosetta 2 on M1 Macs.

just charlie wrote:

NewAkaiUser wrote:I don't think so. You have to wait for an update from Akai.
It's like you want to run windows apps on your android phone. Different architecture.

Most Mac apps made for Intel work fine on M1 Macs though. Almost all of them, in fact. It seems that VSTs and some audio apps in particular have problems. Intel Mac apps run using Rosetta 2 on M1 Macs.

Just because Apple states they 'Should work fine' doesn't mean that's the case for every app. The AirWindows guy is having a hell of a time with his plugins in Big Sur because he's been using deprecated API's for development because he "has to" support old ass Mac OS's that maybe a handful of folks still use. The Valhalla guy told him straight up on Gearslutz, he has to buck up and drop support of the older OS's and update all his shit to use the newer APIs. It all depends on the app, and I guarantee you Akai is NOT doing things 100% by Apple's playbook. They haven't even listed compatibility for Big Sur on Intel Mac's let alone the M1's which more than likely will take a rewrite of at least the controller mode and MIDI drivers (the device isn't class compliant, its not going to work without being updated). I can tell you right now the software for the most parts works in Big Sur on the Intel side, but the Network MIDI app needs to be updated (it works but doesn't have a GUI anymore) and who knows what other workarounds they did in the MPC Software need to be updated as well.

It wasnt the greatest piece of code to begin with, its probably going to take Akai some work to get it updated.

Software seems to work, however MPC is not recognized in controller mode on the M1s...which makes it useless for me

Can confirm M1 Macs run MPC Software and as a plug in with Logic. Though seems no controller mode but the MPC hard drive mounts. MPC Software runs in intel mode and obviously not written for apple silicon yet. Wonder what the time Frame is for that?
I also have no novation USB connection, and also that's not being seen by the MPC in standalone mode or by logic, though off topic.
I just got the live, yay, finally. and rocking it but yet to even see controller mode yet, and old Mac won't be up to the job hence new M1. So I am waiting on Akai, novation, Steinberg, Korg and I think Waldorf for updates. until then it is old school midi, and yeah not bothered to try midi for controller mode, kinda defeats the point of having it hooked up to the computer in a way, so waiting. come on Akai, hurry up

I have a feeling it's going to be long time before it's compatible.

Akai needs to recompile and then test... agree that this will be a while

NearTao wrote:Akai needs to recompile and then test... agree that this will be a while

Do they write their own drivers?

Don’t know... some of the usb audio/midi is generic/class compliant and just needs a text change... not sure about Akai’s solution... may need a third party update... but we all have seen the eight’ish month lag from a new OS X release to getting support... I cannot see how they could get M1 support any faster

NearTao wrote:Don’t know... some of the usb audio/midi is generic/class compliant and just needs a text change... not sure about Akai’s solution... may need a third party update... but we all have seen the eight’ish month lag from a new OS X release to getting support... I cannot see how they could get M1 support any faster

This is the issue with any hardware that connects to a computer. A new OS or update and it's lights out. That's why I never use a general purpose computer for music.

CharlesRandolph wrote:

NearTao wrote:Don’t know... some of the usb audio/midi is generic/class compliant and just needs a text change... not sure about Akai’s solution... may need a third party update... but we all have seen the eight’ish month lag from a new OS X release to getting support... I cannot see how they could get M1 support any faster

This is the issue with any hardware that connects to a computer. A new OS or update and it's lights out. That's why I never use a general purpose computer for music.

And when you're waiting on Akai, better add even more time than the usual developer.. They just barely got a handle on Catalina a few months back, now they've got to catch up to both Big Sur and the ARM architecture. Im glad I kept my Intel Mac mini and didn't trade it in a month ago hah.

Monotremata wrote:And when you're waiting on Akai, better add even more time than the usual developer.. They just barely got a handle on Catalina a few months back, now they've got to catch up to both Big Sur and the ARM architecture. Im glad I kept my Intel Mac mini and didn't trade it in a month ago hah.

I don't know why people do it to themselves. For macOS, I stick with RME, UA, APOGEE and currently only RME is ready. My guess is Akai will be ready fall 2022.

Akai have no excuse at all, the dev team know this is happening way before most of us do. So Akai Dev team get onto it and pull ya finger out. NOW. There are plenty of other companies that can be nimble and up to date quickly and QA too. $20 they are on holiday and not working on it till they get back. Time waits for no man, but all mankind has to wait on AKai. There is no excuse for not having it ready, if dev team can't do it, hire more, if that is the issue, then get a better dev team. Straight up.