Help get this topic noticed by sharing it on Twitter, Facebook, or email.

M-Audio 2X2 works bad on Win 10. Win 7 was fine !!!

Hi M Audio team! I recently got troubles with my 2X2 interface

I got my 2X2 in summer 2018 and firstly couldn't make it work in on Win 7 64bit. Later I used small utility to avoid checking driver digital signature an 2X2 started to work fine!!! at that time i had Intel 2500k cpu and 4gb of ram. Even quite complex projects with a lot of VSTs and fx worked fine in my Magix Sequoia 13 !!! No problems appeared until cpu load was about 80%

Few weeks ago I got new pc ( MSI Z390 A Pro motherboard, Intel i5 9600k, 16gb of ram, 2 fast ssd) and moved to Win 10 64bit. And the troubles began! I installed the latest 1.0.12 driver and firstly all seemed well. But then I open huge projects in my daw Magix Sequoia 13 it starts lagging clicking and interrupting sounds while daw internal meter shows cpu load is about 20% (win task manager also shows about 20% for all 6 cores) I think it's not normal.I tried all different settings in Win 10 itself and in my DAW (buffer settings, bit resolutions, try all usb 2.0 and 3.0 ports, checked if any irq conflicts occur, used no hub - tried all ideas found here on the forum etc )
I use the right driver version for win 10 64bit !!!

So i think it's really problem with 2X2 driver itself !!! It's not a win 10 problem (all may 2019 updates installed, not a pc problem (it's modern and fast).
Then I change the sound driver in my DAW from M Audio 2X2 driver to Magix Low Latency 2016 driver IT IMPROVES PERFORMANCE but I still can't work normal with cpu hungry projects because this driver is just for emergency cases and not optimized for 2X2 audio interface !!! Formerly I worked on Focusrite Scarlett 8i6 1gen audio interface and had no problems with it for 6 years!!! even at high cpu load and complex projects but now I can't use all the power of my pc !
I got only music production related software, the system is absolutely clean and optimized!

I grabbed focusrite 2i2 2gen interface from my friend for few days for the test and everything works excellent even at 5ms latency

I see the latest driver version in my M audio account is 1.0.12 so almost 1 year has passed. Do you plan to make an update the driver version? Or it's abandoned?
Maybe any firmware update is available?
Maybe you have beta versions I can try?
Maybe I try 2X2M or 8X4M drivers just for test?

I really love my 2X2 because of this big volume knob and don't want to sell it but can't use it properly now..

Thanks in advance!
Alex
1 person has
this problem
+1
Reply
  • Also I replicated my tune in latest Presonus Studio 1 daw (same vst's, fx, busses, wave samples) and get the same problem - sound glitches starts at 20% cpu load and different buffer sizes (tried all from 64 to 4000)
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Eliza (Official Rep) May 21, 2019 13:07
    Hey Alex,

    Thanks for posting!

    Sorry to hear that you are having trouble! Driver 1.0.12 is the most recent version for Windows 10. There haven't been any firmware updates or beta drivers released.

    DPC latency issues can result for a variety of reasons. Essentially, this is the part of your computer that handles driver efficiency. You may find that one particular driver is slower to process, effecting the response time of all others. I recommend using a diagnostic program, like LatencyMon, to assess the M-Track's driver performance as well as any other possible causes for lag. Refer to this helpful article for more information:

    Solving DPC Latency Issues

    If you are able to confirm that the M-Track driver is overloading the DPC, I suggest installing an ASIO4ALL Driver which is optimized for WDM audio.

    Try this and let me know how it goes!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Thanks for reply!
    I installed latency monitor and here's the result I got

    Tried to find solution for this issue but finally got confused of that amount of different information.

    Also I installed ASIO4ALL driver. It seems equal to Magix Low Latency 2016 driver (interface is the same). I gave it a test and the result is similar - you can work quite comfortable at 512 buffer but still few sound dropouts occur every minute (15-30% cpu load)

    Now I'm not sure if it's M audio driver problem, or Windows or Sequoia 13 daw problem or something else..
    And finally I'm so tired of that googling and testing and will continue working with asio4all driver for sometime..
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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