MPC X cannot connect to MacOS in Controller Mode

Thanks for sharing that. I wonder why the driver option isn't there in Sequoia, nor the drivers showing in the package itself? It's the same installer file, perhaps a system security restriction?

MPC-Tutor wrote:Thanks for sharing that. I wonder why the driver option isn't there in Sequoia, nor the drivers showing in the package itself? It's the same installer file, perhaps a system security restriction?

No worries!

That's a good question, I think you're right in regards to security - especially in regards to drivers. macOS is moving from kexts to system extensions. However, what Akai/InMusic SHOULD have done is indicated clearly on the downloads page of the inMusic website that for Sequoia users, the hardware drivers are available separately in the inMusic Software Center. Instead, I had to find out through a support ticket.

It clearly states on Akai website that not to update your Mac yet. They are not ready for sequoia…..

This page states clearly that the MPC X and MPC Software are supported:

https://support.akaipro.com/en/support/ ... patibility

They only say not to update if your hardware/software is not specifically listed as 'supported' on that page.

pk1 wrote:It clearly states on Akai website that not to update your Mac yet. They are not ready for sequoia…..

indeed. I didn't scroll down at all last month when I checked.
Just read the top paragraphs and moved on. I have held off myself for no reason.
thanks for the correction.

auricle wrote:That's a good question, I think you're right in regards to security - especially in regards to drivers. macOS is moving from kexts to system extensions. However, what Akai/InMusic SHOULD have done is indicated clearly on the downloads page of the inMusic website that for Sequoia users, the hardware drivers are available separately in the inMusic Software Center. Instead, I had to find out through a support ticket.

They still function just fine, but you get an annoying pop up occasionally reminding you they wont work in a future OS (they've been doing that since Catalina came out).

But you DO have to boot into Recovery and set the security to allow user kexts, otherwise the system ain't going to do shit with it. I just replaced my MOTU 828x with an RME Digiface in December, and man am I glad that I never have to see that message again. I didn't even bother with RMEs kext extension and went straight for the driver extension and it works great. Little Snitch did the same thing a few years ago, and now when you update it, you don't have to reboot anymore. It just turns off the extension and back on again when its done.

Monotremata wrote:

auricle wrote:That's a good question, I think you're right in regards to security - especially in regards to drivers. macOS is moving from kexts to system extensions. However, what Akai/InMusic SHOULD have done is indicated clearly on the downloads page of the inMusic website that for Sequoia users, the hardware drivers are available separately in the inMusic Software Center. Instead, I had to find out through a support ticket.

They still function just fine, but you get an annoying pop up occasionally reminding you they wont work in a future OS (they've been doing that since Catalina came out).

But you DO have to boot into Recovery and set the security to allow user kexts, otherwise the system ain't going to do shit with it. I just replaced my MOTU 828x with an RME Digiface in December, and man am I glad that I never have to see that message again. I didn't even bother with RMEs kext extension and went straight for the driver extension and it works great. Little Snitch did the same thing a few years ago, and now when you update it, you don't have to reboot anymore. It just turns off the extension and back on again when its done.

Yes, you're right. Akai could be pre-empting this change. There has to be a reason why Sequoia users need to download the drivers separately whereas everyone else can install them during the MPC Software installation process.

I had to update the firmware on my RME HDSPe MADI FX card before I could install the new system extension. No more annoying messages that the driver will be incompatible in the future.

I had the same issue with same Mac OS-version and 3.4.2.

Now it's working, BUT I get the message:

MPC project failed to load.

No matter from what drive try to open from. Drag and drop which I read somewhere one should do, rather than double click on file.

Any ideas?

Thanks!

EDIT:
Old projects made on 2.15 opens fine.

ecksbocks wrote:I had the same issue with same Mac OS-version and 3.4.2.

Now it's working, BUT I get the message:

MPC project failed to load.

No matter from what drive try to open from. Drag and drop which I read somewhere one should do, rather than double click on file.

Any ideas?

Thanks!

EDIT:
Old projects made on 2.15 opens fine.

Are you trying to open them in the MPC Software? The desktop software is still 2.xx. Your 3.0 projects have no chance in hell of opening in it.

Monotremata wrote:

ecksbocks wrote:I had the same issue with same Mac OS-version and 3.4.2.

Now it's working, BUT I get the message:

MPC project failed to load.

No matter from what drive try to open from. Drag and drop which I read somewhere one should do, rather than double click on file.

Any ideas?

Thanks!

EDIT:
Old projects made on 2.15 opens fine.

Are you trying to open them in the MPC Software? The desktop software is still 2.xx. Your 3.0 projects have no chance in hell of opening in it.

Yore are absolutely right about that. I'm new to this bug fest and just about to leave.

Back to Kontakt/Pro Tools heaven!

Hooray, thanks auricle for contatcing support.