Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m confused

Problem with two Midisport 4x4 anniv. win 10

I'm trying to connect two Midisport 4x4 anniversary edition to my laptop with Windows 10 (64bit). I have installed the latest driver, 6.1.3. I connect them one at the time and I see them in the Windows device manager, but only one show up in
Sonar X3, Reaper and MIDI-OX. I have tried different USB ports and cables. Any suggestions?
1 person has
this problem
+1
Reply
  • Hi Peter,

    Thanks for posting!

    Are these 2.0 or 3.0 ports? They both appear in the Device Manager with no issues? What kind of options do you get when checking for MIDI ports in your DAW? Are you using any USB hubs?

    Try to have them both plugged in right next to each other without using a hub. For example, if you have a desktop, plug them both into the front instead of one in the front and one in the back.

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

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

  • Hi Corey,

    All ports are USB 2.0. There are no issues in the Device Manager. I have a USB hub and when I plug them in to the hub they both appear in the Device Manager but only one Midisport in the DAW or MIDI-OX, see attached picture.

    I have a laptop, HP Probook 6550b, and when I tried to connect the Midisports to the two USB ports next to each other on the left side no one showed up in the DAW (but they where ok in the Device Manager).
  • (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

  • UPDATE:

    I tried a new USB hub with my laptop, same result, they both appear in the Device Manager but only one Midisport in the DAW or MIDI-OX

    I also tried a different PC with Windows 7 pro 64bit and connected the two Midisports to USB 3 ports in the front, same result.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Good post to have. I will own 2pcs of 4x4 AE by end of February. Will test this then on W10 and Linux. Many of us need more than 4 MIDI ports. Maybe you can try another DAW. Perhaps the application does not enumerate correctly the attached interfaces because they have the same name. If that is the case, perhaps M-audio could provide a firmware to change the name of the device.. Unfortunately even on the new USB products there is no switch to change the ID to reflect in the device's name.
  • (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

  • Hi Happy,

    I have given up on Midisport. You are probably right about both Midisport having the same name is the issue. I haven't tried to change their names in the registry but that should be done by the driver/firmware! I have returned them and are going to buy the Motu micro lite instead. I hope you have better luck than I did!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Another idea if M-Audio has no solution ..wait for the 4x4h (see NAMM announcement) and combine with a 4x4 ? Really hope M-Audio comes out wit the solution, With earlier conversation with M-audio it should work, plugging one in after another. I have Win 10 in insider mode, maybe MS did some updates and there are significant differences between Win 10 normal and the latest on insiders fast channel, so hope that fixed it. I wonder if M-audio had considered a few small DIP switches on the 4x4h to change the name for detection if that is the reason. Guess many people will need more than just 4 legacy DIN MIDI interfaces, even in this age of devices with USB MIDI.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Just bought 2pcs 4x4 and they work fine With MIDI OX and Win 10, both I/F show up. Latest insider version. Only there is problem with Bitwig (3.18) on Windows which only send to one of the devices. Ubuntu 15.10 and Bitwig (3.18) work fine with both. Have not done Sysex and much transmission yet, but I will do that soon.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • @Peter The problems as you reported I now see happen in latest Windows Preview editions. There is even a GSOD. If M-Audio won't fix this with Microsoft, then I also have to move away and buy other MIDI interfaces, like the iConnect Mio.
    I really hope it does not have to come so far.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Note: Everything works fine in Linux with 2 4x4 interfaces.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

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

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

  • Problem: When you install two Midisport 4x4 Anniversaries, both are visible i Device Manager, but only one of them is visible in your DAW.

    Once (in Win 8) I solved the situation by running the Midisport Setup over again. Now, in Windows 10, I have not accomplished to make this do any difference.

    The problem is due to the situation that both interfaces have been given the same names for their ports in the Windows Registry.

    The first Interface you connect is given the following port names:

    MIDISPORT 4X4 Anniversary In A
    MIDISPORT 4X4 Anniversary In B
    MIDISPORT 4X4 Anniversary In C
    MIDISPORT 4X4 Anniversary In D
    MIDISPORT 4X4 Anniversary Out A
    MIDISPORT 4X4 Anniversary Out B
    MIDISPORT 4X4 Anniversary Out C
    MIDISPORT 4X4 Anniversary Out D

    When you connect a second interface, the Setup program obviously have problems to "identify each interface via a clear device number and port naming system", which the User Guide says it should do.

    So when you connect the second interface, the ports are given the same names as the first one. Thus, you will see both interfaces in the Device Manager. But since the DAW will only recognize unique port names, it will only recognize the first instance of each port name, and therefore only the ports of the first interface will be accessible.

    Solution: The solution is to rename the ports names of one of the interfaces to something different than the other. This must be done in the Windows Registry.

    Open the Registry Editor. The first you must do, is to find the correct main keys. The main keys will be found under:

    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{6994ad04-93ef-11d0-a3cc-00a0c9223196}\

    and they look like this:

    ##?#USB#VID_0763&PID_1061#a&260f6969&0&2#{6994ad04-93ef-11d0-a3cc-00a0c9223196}

    The part a&260f6969&0&2 is unique, and will be different for each interface. The rest is the same for all instances. If you have two interfaces, there will be two main keys that are equal, except for the unique part.

    Under each main key, there are the following sub keys:

    #MIDISPORT4X4ANNIVERSARYINA
    #MIDISPORT4X4ANNIVERSARYINB
    #MIDISPORT4X4ANNIVERSARYINC
    #MIDISPORT4X4ANNIVERSARYIND
    #MIDISPORT4X4ANNIVERSARYOUTA
    #MIDISPORT4X4ANNIVERSARYOUTB
    #MIDISPORT4X4ANNIVERSARYOUTC
    #MIDISPORT4X4ANNIVERSARYOUTD

    Under each of the sub keys, you will find a folder named "Device Parameters" containing an object named "FriedlyName". This objects holds the port names that will be visible to the DAW. Double-click the "FriendlyName" object to open it. In the "value data" field, you will see the port names the Setup programs have created. This will be "MIDISPORT 4X4 Anniversary In A", and so on. Those names will be the same for both interfaces - and that's what is causing the problems. To solve this, you must give new "FriendlyNames" under ALL of the eight sub keys for one of the interfaces. Personally, I have given new "FriendlyNames" to both interfaces, like this:

    Midisport 1 - In A
    Midisport 1 - In B
    Midisport 1 - In C
    Midisport 1 - In D
    Midisport 1 - Out A
    Midisport 1 - Out B
    Midisport 1 - Out C
    Midisport 1 - Out D

    Midisport 2 - In A
    Midisport 2 - In B
    Midisport 2 - In C
    Midisport 2 - In D
    Midisport 2 - Out A
    Midisport 2 - Out B
    Midisport 2 - Out C
    Midisport 2 - Out D

    After you have done this, both interfaces should be visible in your DAW.

    Annoyance: When you re-boot your computer, all of the original port names will probably be restored - and all of your editing will be gone. Therefore you should right-click each of the two main keys (or the one you have edited) after editing , and select "Export". Save the files as something like "Midisport1 Config.reg" and "Midisport1 Config.reg". You can optionally edit the two files to be one afterwards. After a boot, double-click the Reg-file(s) to automatically write your edits to the Registry again before you start your DAW.

    It's of course a little annoying having to do this after every boot - but it makes both interfaces operational.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Just by removing the MIDI Sport driver and using the default driver solves the issue even after reboot.

    Just install latest Win10.and make sure you DO NOT USE the one with MAudioMIDISPORT.sys.

    http://community.m-audio.com/m-audio/...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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