macOS 12 Monterey

[bassbeing]

Hi Leigh, Thanks for the 64 bit driver for MIDISPORT 2x2 excellent it works really well with Big Sur , I am testing my music software/ hardware on a macos 12 beta 5 presently but the midisport does not seem to work with this os. It loads the firmware fine and usb light blinks as you would expect but the midisport plugin seems to hang the midi studio window in audio /midi setup ? midisport shows as a new external device not as midisport 2x2 as in macOS 11. Cubase 11 pro can't initialise CoreMidi services and hangs cubase. My MOTU 828 driver seems to work fine everything works as expected on their Catalina driver. Just wondered if you had any ideas on this problem. macOS 12 doesn't seem to be vastly different to macOS 11 ? hope you don't mind me bugging you with this Leigh. thanks again for making my old piece of hardware useable again. Best regards.

Ian V

[bassbeing]

Crash report,

[de073823]

agree I have similar issues

[IvanExpert]

Thought I'd mention I am seeing the same thing as others here: things work fine in Big Sur 11.6.1 (using a Midisport 2x2 original), but in Monterey, trying to open the MIDI Studio window in Audio MIDI setup results in an endless pinwheel. In Logic, it eventually announces a failure to initialize CoreMIDI. Removing the plugin from /Library/Audio/MIDI Drivers resolves the pinwheeling (but, of course, with no MIDI interface shown). I've loved this little box for 20 years -- I'm hoping I can keep using it!

Thanks for your efforts in providing the driver. Much appreciated.

[fvogel]

Hi. I have similar issue, using Ableton Live on Monterey 12.0.1 Live would take 5 minutes to start, hanging when loading midi. Many thanks for your efforts and ready to test if needed.

[ljhorstman]

hi there I downloaded the driver and installed on Monterey 12.0.1 - I am experiencing the same hanging issues. Sorry to ask if this is posted elsewhere but you direct me towards instructions to uninstall? Thanks LJ

[bassbeing]

Remove driver from the Library/Audio/Midi drivers folder. And your software should boot ok after that . This driver issue is not resolved to my knowledge in MacOS 12 Monterey.

[ljhorstman]

hey. thanks for the reply - I had a look in there but there's nothing in the drivers folder... I tried unhiding files but not showing. No midi devices are currently showing in my DAW either.

[bassbeing]

There should be a folder Library /Audio/ Midi drivers. The installation puts the midi driver in the above folder . There. Is also a folder which has the firmware files which loads at startup . But it’s the midi driver that gives you the coremidi device hang . Leigh smith has given all the locations for the installed files in his readme notes . Removing the driver stopped the hang so I could use my daw with a class compliant interface . Good luck

[bassbeing]

Vs 1.3 midisport driver posted by Leigh smith works in macOS 12.1 and 12.2 beta nice work from Leigh & co great work. Thank you .

[ericcowden]

Brilliant! Thanks so much Leigh! I'm using a Midisport 2x2 with Mac OS Monterey 12.3 with Ableton Live 11.1.1. The v1.3 MIDI driver works great!. I love my little Midisport interfaces. Thanks for your continued support. Can we at least buy you a beer? :-)

[naturligasteg]

Just bought my first Mac and would love to get my old Midisport 4x4 to work. I am totally new to Mac but when I try to open the installer packet not blank refuse. I don't even get a dialogue to open with password. What am I missing here? On Monterey 12.4

[aleksibovellan]

Thank you for your hard work Mr. Smith,

I tried this v1.3 driver (following instructions to the teeth) with an M1 iMac 24-inch 2021, OSX Monterey 12.5, and Logic Pro 10.6.2, with Midisport 2x2 Anniversary, connected to a powered USB-hub. But unfortunately, it does not work correctly.

A couple of first notes from a MIDI keyboard might transmit well into Logic, but then their timing starts to go all around the place, like we are talking about seconds of delay soon after. Some notes seem to be repeated also. The MIDI note stream becomes irratic and unpredictable. Also, if for example a C key is pushed a few times in a row, it's not only C that the sequencer receives sometimes, it could also be D, D#, and what not. The Midisport 2x2 seems to transmit data in some sort of panic.

The future of M1 Macs and MIDI seems to be grim, but hopefully Mr. Smith might find away, since he seems to be the only person who can.

[DJ-MacT]

Hi, This is more of a trouble shooting suggestion if you find erratic MIDI behaviour. I have discovered when using the MIDIsport for MIDI 5 pin DIN interface and other MIDI devices using a USB port leave Port A/1 (Send and RCV) open on the MIDIsport device. Unplug everything except the MIDIsport and USB devices, restart and add back the DIN connections one by one to test all whilst leaving Port 1/A open. To help isolate try an app called MIDIView ( free via the AppStore no affiliation ). It can monitor the device and what MIDI messages are being sent independent of Logic. This helped me identify the conflict between USB connected Midi devices and devices connected by USB. I will add my THANKS to Mr Smith for all his help over the years. Cheers!

[aleksibovellan]

Hi, thanks a lot for your generous help!

MidiView sounds something I will definitely look into. It will be interesting to see the raw data and how it conflicts with other devices.

For now, all timing problems seems to have been solved by just downgrading back to the latest Big Sur, 11.6.8, on this M1 iMac 24-inch 2021. With that done, so far no problems using any MIDISport ports or channels, while also being connected to a bunch of USB synths. [Edit: Nope, it all came back. Back to the drawing board.]

-Aleksi

Hi, This is more of a trouble shooting suggestion if you find erratic MIDI behaviour. I have discovered when using the MIDIsport for MIDI 5 pin DIN interface and other MIDI devices using a USB port leave Port A/1 (Send and RCV) open on the MIDIsport device. Unplug everything except the MIDIsport and USB devices, restart and add back the DIN connections one by one to test all whilst leaving Port 1/A open. To help isolate try an app called MIDIView ( free via the AppStore no affiliation ). It can monitor the device and what MIDI messages are being sent independent of Logic. This helped me identify the conflict between USB connected Midi devices and devices connected by USB. I will add my THANKS to Mr Smith for all his help over the years. Cheers!

[rhenning]

fantastic. thank you so much @leighsmith! works a treat here with the following specs:

• midisport-macos v1.3
• m-audio midisport 4x4 rev-b (pcb says midiman (c) 2000)
• macos monterey 12.6.1
• arm64 m1 pro
• ableton live v11
• Darwin m1mac.local 21.6.0 Darwin Kernel Version 21.6.0: Thu Sep 29 20:13:56 PDT 2022; root:xnu-8020.240.7~1/RELEASE_ARM64_T6000 arm64

👩🏼‍🍳 😗 🤘🏼

[mauvehead]

Hello...I just installed v1.3.1 for my MidiSport 4x4 and everything seems to be working. It shows up in Audio MIDI Setup and it shows up in LPX and I can control old gear MIDI with it, however the green USB light won't quit pulsing. Is that normal?

[leighsmith]

Hello...I just installed v1.3.1 for my MidiSport 4x4 and everything seems to be working. It shows up in Audio MIDI Setup and it shows up in LPX and I can control old gear MIDI with it, however the green USB light won't quit pulsing. Is that normal?

Yes, the pulsing is normal, and is part of the firmware to indicate the firmware has been downloaded and is functioning and nothing has hung.

[mauvehead]

Thanks for the quick reply! All looks and behaves as expected. I’m on a 2021 M1Max MBP running macOS Monterey 12.6.7 and I’m thrilled to be able to use some of my old MidiMan gear again. Thanks for making these updated drivers and for maintaining them on newer systems!

[txaukos]

MiDISPORT 1x1 on Monterey 12.7.2 worked fine after updating to 12.7.4 and reinstalling MIDISPORTDriver-v1.3.1 it still doesn't work. MacPro 3.1

[txaukos]

Sorry, but I must insist on this.

I have installed MIDISPORTDriver-v1.3.1 on three disks with Monterey 12.7.4. They work for me on two disks but the Midisport1x1 does not activate on the main one. If I look in System Information, this version does NOT work:

Vendor Specific Device: Product ID: 0x1010 Manufacturer ID: 0x0763 (M-Audio) Version: 0.01 Speed: Up to 12Mb/s Location ID: 0x00300000/2 Available current (mA): 500 Required current (mA): 100 Additional operating current (mA): 0

But this one, Yes:

Composite Device: Product ID: 0x1011 Manufacturer ID: 0x0763 (M-Audio) Version: 1.21 Speed: Up to 12Mb/s Location ID: 0x00300000/2 Available current (mA): 500 Required current (mA): 0 Additional operating current (mA): 0

For it to work you should change:

Vendor Specific Device: by Composite Device: Product ID: 0x1010 by Product ID: 0x1011 Version: 0.01 by Version: 1.21

Version 1.21 is the one contained in the file /usr/local/etc/midisport_firmware/MidiSport1x1.ihx. I don't understand why that firmware doesn't load, that's what I think.

Sorry for my bad English

[aleksibovellan]

Just to add another 2 cents to this topic also, here is my product ID from a 2x2, which experiences those hanging notes and irregular timing issues. Requires an USB unplug-replug most of the time to clear. Perhaps there's something to this product ID thing.

[txaukos]

Sorry, but I must insist on this.

I have installed MIDISPORTDriver-v1.3.1 on three disks with Monterey 12.7.4. They work for me on two disks but the Midisport1x1 does not activate on the main one. If I look in System Information, this version does NOT work:

Vendor Specific Device: Product ID: 0x1010 Manufacturer ID: 0x0763 (M-Audio) Version: 0.01 Speed: Up to 12Mb/s Location ID: 0x00300000/2 Available current (mA): 500 Required current (mA): 100 Additional operating current (mA): 0

But this one, Yes:

Composite Device: Product ID: 0x1011 Manufacturer ID: 0x0763 (M-Audio) Version: 1.21 Speed: Up to 12Mb/s Location ID: 0x00300000/2 Available current (mA): 500 Required current (mA): 0 Additional operating current (mA): 0

For it to work you should change:

Vendor Specific Device: by Composite Device: Product ID: 0x1010 by Product ID: 0x1011 Version: 0.01 by Version: 1.21

Version 1.21 is the one contained in the file /usr/local/etc/midisport_firmware/MidiSport1x1.ihx. I don't understand why that firmware doesn't load, that's what I think.

Sorry for my bad English

Thanks to the user @understructure I have been able to "fix" the startup of the 1x1 midiman Run this command in Terminal to boot MIDISPORT 1x1

/usr/local/libexec/MIDISPORTFirmwareDownloader /usr/local/etc/midisport_firmware/MIDISPORT_devices.xml