I’m sad

MIDISport 2x2 and 4x4 not detected in Windows 10 preview editions

I am a preview user in the fast channel with Windows 10. I have two Midisport 4x4 (anniversary edition). I am using MIDIOX , Windows x64 and also Google Chrome WebMIDI with MIDI in UWP mode. The MIDISports can be found as USB devices in the device manager, that has not changed, The problem is with the Win32 MIDI API. This problem seems unique to the MIDISPORTs. Other USB MIDI device do not show this problem.

Win 10, Build 16257.: Both the MIDISports can be found in the device manager but cannot be found (enumerated) using the Win32 API. MIDIOX does not show either one of the input/output port of both of them. However Google chrome with MIDI UWP shows all MIDI I/O's from both units. When changing Chrome to Win32 MIDI interface, the MIDISports cannot be found. I also attached a 2x2, and it could not be detected as well. (see the first picture)

Windows 10, Build 16281, Now one of the MIDISport devices shows up in MIDI OX but not both. In Chrome with UWP both are visible. (see the 2nd picture)

P.S: MIDI-OX (and the Windows 10) UI has also become sluggish and slow to respond to mouse and keyboard changes, not sure this is related..

Just wanted M-AUDIO to point to this and suggest to closely monitor Windows 10 development because Microsoft seem to be changing the MIDI API. have used the 4x4 and 2x2 reliably well in the past so I hope that continues to be that way.

A confirmation if M-AUDIO is aware and reproduced this would be welcome.

The pictures below show left Chrome with the UWP API and right MIDIOX.

2 people have
this problem
+1
Reply
  • I got several times a Green Screen of Death at boot and the problem it reported was the MIDISport.sys driver. (Once I capture the screen with a camera it will be posted herel). Sometimes Win 10 did boot and I verified I am using the latest drivers provided on this website.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Hey Happy,

    Thank you for providing that information. I will pass this along to the M-Audio team. I understand you have some additional information - whatever you have available will be useful to the community.

    Please let me know if you have any questions!
    • view 1 more comment
    • I am now on the latest win 10 insider build 16296. I don't get the GSOD anymore but Win32 API still only sees ONE 4x4 interface and the UWP API reports both. Though the UWP API output ports are all called the same: "MIDI" while the input ports correctly have unique names. Sometimes MIDIOX does not reponsed for a while after using enumerating the port, but not sure that is related.

      It would really help to know

      [1] Are these two issues caused by the MIDISPORT 4x4 hardware or Windows 10

      [2] If/how/when this can/will these two issues be fixed in windows 10 or by 4x4 firmware
    • I've had the same problem with the older midisport 2x2 and uno's with windows 10

      If trying to boot the computer with more than one of the newer uno;s it results in windows 10 blue screen. Same with any of the older midisport 2x2's . This is using the last released driver MIDISport_Installer_6_1_3_Driver_5_10_0_5141 from 2013... heh .

      I have found a solution that usually works.

      I have put 3 midisport 2x2 (old models) on one usb hub with a power switch. Another 3 midisport 2x2's (old models) on a separate usb hub with a switch.

      I start windows 10 and login. Then I turn on bank one of the 3 from the first hub. Wait until they are detected. Then I turn on the second hub and the next 3 fire up.

      Loading only a few at a time seems to usually prevent the blue screen driver crash.

      They work in ableton no problem after this. Once and awhile it will still lock up and blue screen when the driver loads but it is not very often.

      Hope this helps someone.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Attached is the GSOD (Green Screen Of Death) used in preview editions instead of the BSOD of regular Window 10 editions.

    I removed the two 4x4 and rebooted windows. Boot ok, then installed one 4x4 and boot was ok, then installed one 4x4 and one 2x2 and boot ok (but got for some time a black screen), installed two 4x4 and boot was ok ~

    Under all conditions:

    - The 2x2 is detected in Win32 (MidiOX) and Chrome in MIDI UWP mode
    - The 4x4 is NOT detected by Win32 (MidiOX) but IS detected in Chrome in UWP Mode !

    Confirmed using the UWP API using the Win32 API wrapper in a C program that the 4x4's are visible through the UWP API but not wit the Win32 API.

    There is something fishy going on with Windows 10 and MIDI for the 4x4 in the preview editions.
    .
    It could be that Microsoft may move away from Win32 to UWP API and alll MIDI application may need to follow. But the transition seems to create some bugs and instability.

    i think this 4x4 problem is real.

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Same problems still exists on latest build 16291. Issue reported on Windows 10 Preview Feedback Hub Serious problem. Hope M-audio or someone else can conform and duplicate this.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Weird thing in 16291 is that both MIDI Sports are in the device manager (they always have been) and, only one in MIDI OX and non in Chrome. In Ubuntu Linux with ALSA no problem at all.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Two other topics found describing the same issue

    http://community.m-audio.com/m-audio/...

    http://community.m-audio.com/m-audio/...

    Does this mean i need to give up on two 4x4 and sell my interfaces to get more than 4 MIDI ports in my PC or is M-audio going to look into this ?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I’m anxious
    Just read through your thread. Dang, not good news. I have two MIDI Sport 2x2s, but haven't set them up yet. I'm just now getting my DAW reconfigured and running again after a catastrophic hard drive crash. My system is still running Win7, but I'll most likely be upgrading to Win10 soon. I hate it when OS upgrades break things!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I would be interested to know if this works for you and what version of W10 you are (enter "ver" in command prompt). Two 4x4 work fine on Ubuntu Linux, on windows one 4x4 + 1 2x2 also seems to work on Windows 10. But two 4x4 wontt.

    I removed the driver in Device manager which is provider by M-auudo (from 2012) and reverted to the Windows driver (from 2006). The problem is still there. I am wondering if I am slamming into a brick wall to get 2 4x4 to work and just should give up on the 4x4's.For me, this is a very very serious issue because I have a lot of legacy MIDI DIN I/O stuff and this issue breaks my complete studio setup.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Hi Nick D. Any feedback from the team. ? It's been 2 weeks.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • SOLVED. The problem is the MIDISPORT Driver, version 6.13 from 2017.
    The default Microsoft drivers work correctly both in Windows Insider edition and the regular Windows release.

    Do not use the M-AUDIO drivers !!!!!

    If you , like, have the M-audio drivers installed, (see Picture below. MAudioMIDISPORt.sys) remove it.

    it takes some effort to get back to the Windows drivers. here are the steps I experienced:

    [1] Uninstall the 6.13 M-Audio driver from Add/remove programs in control panel.
    [2] Device manager will change the device as an "unknown device
    Update driver won't work (no driver found)
    [3] Remove the device from device manager (uninstall device)
    [4] Scan for hardware changes
    It shows "MIDI sport 4x4" but there is an device error:
    " Windows was unable to install your MIDI sport 4x4 Anniv"
    [5] Click on "Check windows update" to try to update
    Report: device is up to date (but the driver still has an error)
    [6] Uninstall driver again
    Remove 4x4 from USB port (This is the key)
    Insert th e4x4 in USB port again
    [7] Windows now detected Driver installs ok in audio/sound devices
    [8] MIDOX etc.. now sees both two MIDISPORT 4x4 devices.

    Refer to the pictures below for the correct drviers. These drivers are from Sept 2017 because it's the Insider update. The regular Windows 10 release driver (as of Oct 2nd 2017) is from July 2017, but the filenames are the same

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Hey Happy,

    Glad to see you were able to make progress with this! Thank you for posting what you found for the community!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Thanks Nick,

    Will there be a M-Audio driver someday that works under Windows 10 that can support 2 or more MIDISports or does M Audio rely on Microsoft to support these devices now and in the future ?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Hey Happy,

    While I can't guarantee that there will be an update to provide this connectivity, I am happy to forward this request to the M-Audio development team for consideration. Thank you for your feedback!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • For all you folks reading, this, it does not should Maudio will fix this. After removing the MA drivers and using the Win 10 standard drivers, things are fine. The only issue I have that sometimes (not often) under Linux the interfaces get crazy and send data delayed or incorrectly, after a power cycle of the interfaces things are fine. I do plan to move over to an other supplier , like the MiO 10 from iconnectivity in the future to guarantee future OS support specially now that Microsoft is only concentrating on UWP MIDI and stopped development for Win32 MIDI. I don't feel M-Audio is putting similar efforts and interest in Midi interfaces anymore. (remember the new MIDI interface announcement on NAMM from MA around 2-3 years ago, these new interfaces newer came to market)
    .
    • Yeah. Also considering that device. I saw they updated the drivers with multi client functionality as well, which is what I need for both controlling hardware through vts’s, while sending controller info back to the pc. However, the asking price is a bit much for me at the moment. Not really many options out there anymore though. Motu also seemed to drop the ball a long time ago.

      How did you get that specific windows driver build btw? I have a newer one, and cant find any older ones anywhere. Also, the windows drivers dont support multi client, do they?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Just install latest Win10.and make sure you DO NOT USE the one with MAudioMIDISPORT.sys. (see picture above) If it's a newer one from Microsoft one it should work. I have Cubase as well and can check the 2x2 later, but the 2x worked with any other DAW. and client AFAICR.

    Microsoft stated that UWP MIDI supports Multi-Client, so the drivers support it but probably only via the UWP API. Just Cakewalk supported UWP MIDI so far (it's dead) and most MIDI tools only use Win32 API. Guess most DAWS will support UWP in the next year or so. Any WebMIDI can support UWP MIDI via Chrome, but if there is any client using the Win32 MIDI API, the multi-client function is not available AFAIK. I also use Linux so multi-client is not an issue there.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Does anyone have any reason to believe this won't work ok with the non-AE version?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • My midiman midisport 2x2 and 4x4 have stopped working on Windows 10 within the last week. I suspect it is the most recent W10 update that has rendered the available drivers incompatible.

    If anyone finds a workaround it would be great to know what it is but I suspect it would be more trouble than it is worth.

    Maybe time to replace the 2x2 and 4x4 which I have had since the late 90's?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I've had the same problem with the older midisport 2x2 and uno's with windows 10

    If trying to boot the computer with more than one of the newer uno;s it results in windows 10 blue screen. Same with any of the older midisport 2x2's . This is using the last released driver MIDISport_Installer_6_1_3_Driver_5_10_0_5141 from 2013... heh .

    I have found a solution that usually works.

    I have put 3 midisport 2x2 (old models) on one usb hub with a power switch. Another 3 midisport 2x2's (old models) on a separate usb hub with a switch.

    I start windows 10 and login. Then I turn on bank one of the 3 from the first hub. Wait until they are detected. Then I turn on the second hub and the next 3 fire up.

    Loading only a few at a time seems to usually prevent the blue screen driver crash.

    They work in ableton no problem after this. Once and awhile it will still lock up and blue screen when the driver loads but it is not very often.

    Hope this helps someone.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited