Midi not working properly on M1 MacBook Pro

I have a 16GB MBP M1 as well. I bought it less than a week ago.

There seems to be an M1 chip issue (not Big Sur) that's been reported many times on various support boards. The "stock" answer by Apple is to either use bluetooth midi or to try to get it running via audio/midi setup via a cable. I've heard that bluetooth midi is working with the MBP/M1, but didn't want to buy a wireless midi keyboard to fix a problem that shouldn't exist. It's a shame that six months after product launch Apple still hasn't fixed the very well documented midi issues with the new M1 chip.

Here is a solution: iConnectivity mioXC. It's a simple midi cable with a USB C (and USB A converter) on one end and a pair of DIN midi connections on the other. Perhaps the USB output on the keyboard is confusing the MBP and it can't sort audio from midi data - I'm not an engineer, so can't say for sure. When you use the DIN (round) midi connector, it's midi only - no audio.

Neither my M-Audio Ozone, nor my Yamaha MOX8 were working with my M1 laptop and I tried going deep into the audio/midi setup, and used a midi monitoring program called snoize. I saw on another board that someone had tried this simple midi cable and it worked, so I took the chance (it's about $50).

My Apogee Duet works for audio, but the USB midi - nada. So I plug my Ozone midi controller into the mioXC and it even works through a hub using the USB C to USB A adapter. No muss, no fuss and I'm operational.

I can't imagine if the guys with big midi rigs requiring multiple midi ports will ever be running on this chip, but if you just have a single or 2 midi input devices, this could work for you.

Good luck!

I have a Traktor F1 and can tell you that it works perfectly, both in native and in MIDI mode.

Just got a reply from Allen & Heath, here's what they say:

This is something that we are currently aware of and our software team is investigating.The K2 is Core-compliant on Mac, so there is nothing to fix. As it currently stands, the new M1 system is not working with the K2. Hopefully, we will have some more information and a workaround on this soon.

The K2 is, therefore, currently unsupported on this platform until further notice.

At least they're aware of it. Hopefully a solution is coming, before clubs open again! 😉

DJ Nasty Fingers wrote:

Thanks for the input everyone.

I too was hoping the 11.2 update would fix it. I have reported the to apple via the feedback form and to tech support.

I've console too, I can see the connection but I get the same error as sinm pointed out.

I spent 2 months scouring support forums for anything that might help and come up with nothing other than more devices that aren't working. I asked A&H for an update but they've yet to get back to me, its been a week so I'm not holding my breath.

So off the back of that I've just bought a Native instruments X1, which according to NI is compatible with both Big Sur and M1 Macs.

I'll report back when it's arrived.

Hey,

Just tapping in to say that the Xone:K2 seems to only work through an USB hub. Directly it won't (using a Mid-2014 MBP with Big Sur 11.4).

Hope this helps someone!

After over a month of chasing down empty leads and possible fixes I finally came to the conclusion that this is an M1 chip issue and I returned my new MacBook Pro. Apple was very understanding and didn’t even quibble about the fact that I was well over the 30 day return period. That tells me that they know they have a problem. Back to my 2012 MacBook Pro! It’s slow but still works like a champ!

M1 have this problem! I have mbp pro on m1 and my m-audio keystation mini 32 - budget keyboard, also not working correctly. it working randomly. But i found a solution for me. If your daw doesn't see keyb you can try go to audio-midi settings (type 'midi' in spotlight) - click on window - show midi studio - choose your midi keyboard and just delete it by clicking on tray, then reboot mac, connect your keyboard and it might be working... sometimes it working without rebooting...

Sorry for my english and i hope it will help someone.

Just for the record. Console shows this error from MIDIServer (AppleMIDIUSBDriver) on device connect:

USBMIDIDevice.cpp:190   [-] USBMIDIDevice(0x152108818)::Initialize() encountered an error and is exiting prematurely.

I'm having a similar problem on my new macbook Pro with M1. My Zoom R16 Recorder/Interface Controller and my Alesis SR18 midi drum machine are recognized as present but the M1 will not recognize either audio or midi signals from either. I've been through the Apple store help desk and the manufacturer help desks. Apple says it's a problem with the manufacturer's drivers. Both Zoom and Alesis just sent out driver updates for the M1 chip. Both those updates allowed the M1 to recognize the devices but still no input allowed by the M1. I plugged both devices into my 10 year old Macbook Pro and they work perfectly. I have a friend who just bought a Macbook Pro 13" with the Intel chip. Plugged my devices into it and Bingo! No problem!

So, my conclusion is that this is a Mac M1 problem and I'm not holding my breath that they are going to fix it any time soon. My advice. Before you get your new Macbook Pro... Think twice!

I totally get the frustration, some MIDI interfaces (e.g. MOTU) aren't compatible with M1 and Big Sur -- but there are low-cost solutions out there. I bought, for 50 bucks, a MioXC and it transmits perfectly from my keyboard to my M1 MacBook Air, no latency, no issues, both Logic and Garage Band. Simple and cheap. Don't know why MOTU is hung up, but I no longer care.

I have now recreated this workaround:

https://dmgadget.net/en/djsetups/

I had previously taken similar devices with the same technical values. But then it did not work. Exactly with the same devices as in the article it worked then. Understand zero why but the workaround goes. But it must be exactly these devices. I have tried it with three different configurations and never went the XONE:K2.

With the configuration you see in the pictures in the discussion to the article, it goes 100%.

Is my most expensive workaround ever.

Have you tried the iConnectivity mioXC cable? It did fix my problem, but it has a MIDI DIN input and USB A (or C) output. I don't know if USB to USB would work. Mine even works via a USB C hub going into one of it's USB A ports.

I have a BCR2000. I have been trying to troubleshoot it with Pocket MIDI and BC Manager.

It seems that it works under Big Sur on intel based macbook, but not on the M1.

-BCR is recognized properly in Audio Midi Setup

-input and output ports are created, and can be selected in apps

-input (from BCR to M1) works okay in CC and Sysex commands

-output (from M1 to BCR) does not work in any way, same hardware and software in intel works.

if anybody can give me any pointer where to dig, I am happy to help.

All of a sudden I got a new update from Allen & Heath:

"Thanks for your feedback, hopefully we'll have more info on compatibility with Apple Silicone hardware soon"

So, let's keep raising awareness on this issue!

Hi everyone!

I have the same identical problem with Moog Slim Phatty.

My Macbook air M1 (Big Sur 11.3.1) recognize all my external usb/midi devices (Korg SV1 keyboard; Waldorf Blofeld synth; Behringer umc1820 audio interface; Akai APC40 controler; Midistart music 25 midi keyboard) except Moog Slim Phatty! No one of these devices needed an update (or a driver) to be recognized by the computer.

Slim Phatty is recognized in the Midi Configuration window but the icon is transparent. It appears like not turned on. In all the other devices is selected "on" automatically. There's no way to select "on" manually in the icons. I tried with another macbook m1 Big Sur and it was the same. With my old macbook pro (intel i7, OS 10.13.6) everything works fine.

Slim Phatty is updated to the latest firmware.

I contacted Apple and they said that it is a manufacturing problem.

I contacted a Waldorf technician, just to ask if Blofeld works with M1, and he gave me this answer: "USB is a fixed protocol and therefore independent of the system (Windows/Mac) or operating system OS". BTW, I asked Moog as well before buying my macbook but they didn't answer me and they still don't answer me even now that I wrote them about this problem.

Conclusion. I'm seeing here that a lot of people have the same problem with several devices therefore, maybe I'm wrong but it seems to me that it is an Apple problem.

Thanx in advance to all those who will help us to solve, in some way, this issues!

Hi Everyone,

... I am a bit late to the subject but wanted to give my input ...

Same here ... Recently bought a new MBP M1 for DJ-ing ... I still own some older DJ-controllers ( MIDI with an integrated audio interface) The controllers are Class Compliant "Plug & Play" ... Both my Intel MBP and new M1 are on the same version of Big Sur (11.4) ... On Intel, the controller's Midi input is recognized and the audio-interface is working ... On M1, the audio is working but the MIDI-input is not recognized ( ... checking in Mac System Report under the hardware section ==> USB, the controller shows up with all details (Manufacturer, Model Name, Voltage Requirements ... etc.)

Conclusion: Intel and M1 on the same version of Big Sur ( ... I never had to install/update any drivers on my Intel...) On Intel everything works fine and on M1 it doesn't ... ==> THE PROBLEM IS M1 ....