Windows 10 not recognizing m-audio uno sport midi interface

[Justanotherguy]

My apologies if there's already a good answer for this type of question. I couldn't find the search function and wasn't able to find anything close enough going through all the pages. I'd be glad to read any existing posts if anyone were able to point me that way. And I'll delete this if asked to.

But i just got a ND3P and I've been trying to load some banks on it, but im unable to get this M-Audio Uno midi interface to be recognized in the drum manager software. Do you think I need a different interface? Or is it probably something to do with the drivers? Maybe the fact that im still using windows 10? I've tried switching the midi ports and adding the nord clavia drivers and so far, no luck. So far, it's just the green usb light on the interface lighting up. Neither usb out or in lights up. Nothing about the interface is recognized in the drum manager. Open to any and all suggestions. Thanks for any answers.

[kotatsu]

Are the other MIDI messages from the ND3P recognized by your computer (for instance in a DAW or in another midi console)?

The ND3P midi manager can be picky, especially if the MIDI interface is low quality (which could be your case). I remember that using a crappy USB MIDI interface the sysex messages from the ND3P would get cut out and the manager would crash entirely. Using the midi interface of my Focusrite card would show no problems though.

Those USB midi interface more often than not just can't deal with the way some machines send sysex messages. I found the Midisport manual online and it says that it should manage long sysex messages, granted the right drivers are installed. I have founds also some reports of people online saying that sometimes the interface correctly sends/receives sysex and sometimes not. It is an old interface but according to M-Audio's website its drivers should be supported by Win11.

You can try downloading a MIDI monitor app like MIdi-OX or MIDIview and see what you computer receives from the midi dump. It should start with the byte F0 and end with byte F7 and it should be 295 bytes long if I remember correctly. Anything else means that the message is being corrupted. It should look something like this (this is a sysex dump from my Nord Lead 3).

midioc.png (138.87 KiB) Viewed 1199 times

Anyway, if you happen to put your hands on a more solid interface (like an audio interface with midi connection or like the 2x2 midisport) your problem should go away.

[Justanotherguy]

Thanks for the detailed response. Im not going to pretend that I fully understand all the things you were saying above like how to send sysex messages through the midisport. But I ended up finding the usb devices section in windows and it was saying that there was a driver error. Tried rolling back, updating and reinstalling the driver from the manufacturers website, but none of that ended up working. I searched a little more about m-audio and from what I gather, they're not very good about keeping their drivers up to date. I didn't realize it at the time, but as you said, it's an old ass interface. So I ended up grabbing another midi interface(Lekato LUM-01) that was recommended by another user in the nord keyboards side to use with nord sound manager and it ended up working right away for drum manager. Apparently, this one is fully class compliant. No driver issues whatsoever. Just plug and play. But again, thanks for the detailed response and I'll go ahead and download that test program incase of any future issues.

[kotatsu]

Yeah, I was pretty confident the drivers were the issue. Enjoy!