Guide to making MIDI Express XT compatible w/Big Sur

[michael_m]

Thank you so much for posting this - I had assumed there was a serious compatibility issue that had to be resolved, but it seems it's basically down to the drivers not being signed...

Anyway, I got mine up and running in Big Sur, so all is good now.

One thing I don't see though is whether ClockWorks is installed. I ran the installer, but don't see it in the Applications folder - anyone been successful with the installer also installing ClockWorks?

[naiveteenidol]

Hello, I am trying this trick for my Motu ultralite AVB but the terminal is telling me no such directory after entering the code with KRCLLMGZ2D

Any ideas?
Please help
Thx in advance

Typo, I got a little further. I entered: the sudo line and my terminal, entered my password and it says “command not found”

After not knowing how to help myself, I reinstalled the driver and my system asked me to go to security and allow the changes. I can now see my ultralite AVB in MOTU Discovery. Now I seem to have the problem that Pro Tools can’t see it.
aaaah... stupid me...
“Let there be sound, and the was sound”
Thx for the help guys. I’m back in business...

I keep getting this "command not found" problem as well. Can you share how you got around this? Trying to get my Express 128 to work on a new MacBook Pro w M1.

[naiveteenidol]

Update: I wasn't properly copying the line. But now I get this message:

Executing: /usr/bin/kmutil load -p /Library/Extensions/Motu MIDI Driver.kext
Error Domain=KMErrorDomain Code=71 "Incompatible architecture: Binary is for x86_64, but needed arch arm64e" UserInfo={NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e}

Thoughts, @copasetic? Others?

[eklectic]

The process worked for me with my Micro Express XT.

I just want to echo the thanks already given and say THANK YOU again to Karmi and all the others who shared helpful thoughts--
I'm so grateful someone figured this out and had the kindness to share.

For months I've been waiting for MOTU to update their installer -- sort of surprised at how slow their update process is (if any).
I wrote them (in January) and they said to keep an eye on their page and it's sort of surprising how infrequent the updates were there.

I wish I'd found this sooner. (Sort of kills that the answer was available for months and I just didn't search right-- and I wasn't previously a member of MOTUnation....) It's so great that there are those who figured it out and shared.

[naiveteenidol]

The process worked for me with my Micro Express XT.

I just want to echo the thanks already given and say THANK YOU again to Karmi and all the others who shared helpful thoughts--
I'm so grateful someone figured this out and had the kindness to share.

For months I've been waiting for MOTU to update their installer -- sort of surprised at how slow their update process is (if any).
I wrote them (in January) and they said to keep an eye on their page and it's sort of surprising how infrequent the updates were there.

I wish I'd found this sooner. (Sort of kills that the answer was available for months and I just didn't search right-- and I wasn't previously a member of MOTUnation....) It's so great that there are those who figured it out and shared.

Yes -- I feel like I'm not necessarily *that* far off from getting this.

Does anyone else have any thoughts about what I might be running into? Is this some kind of 32 vs. 64-bit issue?

FWIW, I emailed MOTU and they got back to me right away -- tho it was more or less just to repeat the line about keeping an eye on their webpage.

[naiveteenidol]

Alright! Good stuff.

Here's what happens on my brand new M1 Mac Mini 16GB.

To boot to recovery i hold down the power button until the options sign appears.
i go to terminal and type csrutil disable enter. i enter my password.
on the kext consent line i get 10 long lines in response to the effect that the appwrapper as well as 9 other things is implemented in both

/System/Library/PrivateFrameworks/SystemPolicy.Framework/Versions/SystemPolicy and /usr/sbin/spctl. One of the two will be used. Which one is undefined.

i restart.

upon restart i open terminal.

Executing: /usr/bin/kmutil load -p /Library/Extensions/Motu MIDI Driver.kext

Error Domain=KMErrorDomain Code=71 "Incompatible architecture: Binary is for x86_64, but needed arch arm64e" UserInfo=NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e}
christiangierden@Minivonhristian ~ % sudo kextload /Library/Extensions/Motu\ MIDI\ Driver.kext
Executing: /usr/bin/kmutil load -p /Library/Extensions/Motu MIDI Driver.kext
Error Domain=KMErrorDomain Code=71 "Incompatible architecture: Binary is for x86_64, but needed arch arm64e" UserInfo={NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e}
christiangierden@Minivonhristian ~ %

any tips by impatient code wizards? otherwise the wait is going to be a bit longer for me, isn't it.

any help much appreciated. i can test run things on am m1 now, if that helps

great thread. cheers!

I am running into the same problem on my M1 w an Express 128.

[insch]

I found that this worked but only if I didn't re-enable SIP. As soon as I re-enabled SIP my MIDI Express XT went offline. Has anyone else had this experience?

[dmil2469]

Hey ALL! I wanted to confirm and share that this fix (from Karmi's original post instructions) work for the MOTU MIDI EXPRESS 128 interface. I had recently updated to BigSur 11.4 this evening, and my MIDI Express 128 stopped working. Then I followed these procedures again and it did the trick.

Re-copying the original text for convenience...

***************************************************************************************************************
1. Install the latest available OSX 10.15 driver from Motu website (if you haven't already).
2. Restart holding down Command-R to reboot into Recovery Mode.
3. Select Utilities --> Terminal from the top menu.
4. Type two commands, each followed by Enter.
1. [to disable SIP]: csrutil disable
2. [to mark Motu's dev ID "always trusted"]: /usr/sbin/spctl kext-consent add KRCLLMGZ2D
5. Restart
6. Open Terminal
7. Paste this exact line into Terminal: sudo kextload /Library/Extensions/Motu\ MIDI\ Driver.kext
8. Enter your password, press Enter
9. Go to System Preferences --> Security --> enter your password --> click the "Allow" button.
10. Restart normally
11. Confirm that you can see and use your MIDI device
12. Restart into Recovery Mode and open Terminal (#2-3 above)
13. Type: csrutil enable
14. Press enter --> restart your computer normally.
You are done.
***************************************************************************************************************

Thanks again to Karmi for the instructions.

[DWxl]

MIDI controller driver download is now available as of 06/08.

[jschussler]

Sorry to necro this thread, but I'm now on Big Sur and finding my Express 128 unwilling to play ball.

Anybody have any more recent updates to this issue? I've followed all the steps in this thread, until I get to the last one where it wants to kextload, and am finding that I don't have either the file (in one of the instructions it says "MOTUProAudio.kext") or the directory (in the other set it expects a MOTU MIDI subdirectory within the extensions folder.

Clearly their current driver pack has changed a bit ( Mac v89555 | Oct. 13, 2021 ). Presumably working for others.

Sadly not for me....