Certainly for many of the models (1×1, 2×2, 4×4), the firmware does get downloaded each time you unplug and replug the USB cable to the MIDISPORT and the USB LED will slowly pulse when the MIDISPORT has it’s firmware running. However I don't have an Anniversary edition, and it's not clear to me yet if that one is downloading firmware? One way to diagnose is after the MIDISPORT is plugged in, click Apple->About This Mac->System Report...->USB and scroll looking for a "Composite Device" with a Vendor ID of "M-Audio", and report the product Id? That will indicate if the firmware is being downloaded.

It could be that after reboot, the firmware isn't being downloaded immediately when the system is booting. That is something to diagnose, by checking if the USB LED is pulsing after rebooting the Mac?

One thing to test is if you can send MIDI to the MIDISPORT (even if you don’t have a synth attached, you should see the MIDI out LED flash) after reboot with a delay or not?

Thanks so much for your reply, Leigh. Much appreciated.

Here's some help with the diagnosis from the questions you asked;

• After computer reboot (and before unplugging and replugging the USB), the MIDISPORT USB LED pulsates slowly.

• The Mac System Report has the device listed, with a Product ID of '0x1050' and it's Version 1.04

• When I send MIDI to the MIDISPORT from my computer the output LED flashes and MIDI is received by the connected synth module without any delay, but there is still a 2-second delay in the DAW receiving MIDI data from my controller keyboard through the MIDISPORT

• I've tried it with a different DAW but the same problem exists

Any other thoughts, Leigh? Could it be that the MAC is initially trying to use a class-compliant driver?

Cheers,
Steve

I'm starting to see what I think is common behaviour on my 8x8, where input isn't being received. One thing to try is to immediately start the Apple /Applications/Utilities/'Audio MIDI Setup.app' and see if the MIDISPORT becomes responsive, or whether it still delays or eats MIDI input? I suspect it might be that the Audio MIDI Setup app is doing some initialisation now required on recent versions of MacOS, that the driver is not. I'm hoping to get to do some diagnosis on this soon.

Thanks, Leigh.

I'd tried the AudioMIDISetup previously to no avail. The MIDISPORT is showing in there even when MIDI notes are delayed. I've tried making a new configuration to no avail.

Here's something I've noticed; My Belkin hub is external transformer-powered, meaning the MIDISPORT remains powered if I unplug/ replug the Belkin hub from the computer, which doesn't clear the problem.

It's only when I unplug/ replug the MIDISPORT from the Belkin that the fault clears meaning that the MIDISPORT needs to actually lose power for the reset to work.

Also, I've noticed that the fault reoccurs if the computer has woken from a 'sleep', so it's not just from a restart.

Cheers,
ST

One more observation: After an unplug/ replug and opening of a Logic project with MIDI behaving correctly, when I open another project I get the attached warning. Not always but sometimes, it seems, but crucially the MIDI works fine, no delay.

I'm looking for a pattern to do with the status of the project when it was laswt saved etc...

Hi,
I wanted to chime in here with some observations with the hope of isolating and solving this issue. The Midi multi-second delay issue is a tricky one. I work with some other musicians and between the three of us with three different audio interfaces and different midi interfaces and I think I have figured out the issue. Sorry for the length but I hope i can help prevent unnecessary debugging.

Environment Catalina OSX 10.15.7 < Logic Pro X ( current ). Multiple Midi devices connected by USB and Din Port Midi.

Issue: Hit a key on a device connected by DIN interface and there is a 2-5 second delay. Been happening ever since upgrading to Catilina.

Isolation: Close the DAW and monitor the midi ports with Midi View (AppStore Free) or MIDI Setup (test mode). Issue is independent of Logic BUT unsure if Logic can trigger the issue.

Here are observations

• It tends to relate to older / outdated versions of MIDI drivers when multiple devices are connected.
• Cleaning out old control surfaces in Logic and the Midi Setup helps but issue tended to "reappear".
• Seems to relate to multiple Midi device environments
• Mix of DIN and USB Midi interfaces seems to be the culprit

I had a Midisport 4x4 Anniversary Edition ( with M-Audio drivers ) with the following connected:

• Roland Drum kit
• Yamaha 88 key
• Roland FA-06 workstation (no USB Connection)
• All ports on Channel 1
• Note other USB Midi devices were connected.
  The Delay Issue was a problem when devices on the Midisport were powered up. Disconnected the Midisport 4X4
  In the case of the FA-06 installing and using the current USB driver from Roland resolved the issue.

Isolation to a Potential Solution
Installed the current version of midisport-macos with careful manual removal of prior version of M-Audio Midi drivers (etc)
Sequentially added and tested. Everything worked fine at first... soon the Delay was back on the device on Port A
Step 1 - Yamaha 88 Key (Port A)- No Delay
Step 2 - Drums (Port B) - No Delay
Step 3 - Roland FA06 (MidiSport 4X4 Port C AND also connected USB ) No Delay
Step 4 - Test Yamaha 88 Key (Port A)- Now has Delay
Step 5 - Move the Yamaha to Port D the delay is gone...
Step 6 - Switch the Yamaha back to Port A and the Delay returns
Step 7 - Disconnect Roland FA06 USB
Step 8 - Test Yamaha 88 Key (Port A)- Delay issue gone

Conflict Isolated
If a ANY Midi device is connected by USB (on Channel 1 ) and another device is connected using the MIDISport 4x4 Port A the Delay Issue is triggered.

** Hypothesis - Solution? - Workaround **
When you have a mixed Midi environment of USB and a Multiport DIN Midi interface/adapter. Leave Midisport 4x4 Port A open.

Still to Research
What to do when there is a single Midi DIN port ( on interface or usb adapter ) and a Midi device connected USB direct.

I hope this helps.

Hello all, I just want to chime in that I've had this very problem with my MIDISPORT 2x2 Anniversary Edition FOR YEARS. The issue lies entirely with the hardware and is not due to the operating system nor its drivers. I've been able to replicate this issue under Windows and, just moments ago, under Linux using a very barebones setup (the amidi utility from alsa-utils).

The workaround is indeed to reset the unit by removing it from the USB and plugging it back in. But I must stress that this is a workaround and not a solution. The solution lies with M-AUDIO recognizing the issue and, hopefully, coming up with a way to flash in a patch.

It's not just you!