Menu
What's new
By:
Filters

PC: MOTU M2 dropping audio

D

David Lai

Member
Hi everyone!
After getting my MOTU M2 hooked up with my USB C port, I found that occasionally it would cut out the audio and then the audio would return again. I tried all other non-USB C ports (only 1 on my laptop), changed buffer size from 256 to 512 then back, checked all power settings on Windows and disabled all means of USB power management, and even updated my bios firmware. I can't look at bios because I'm totally blind and bios has no screen reader support. The diagnostics info presents the error code x00020002, and says that the USB host port has dropped audio. Usually this dropped audio occurs when I try to open or close a software window on the computer like the mail or web browser, and sometimes when I play the piano or listen to music, the dropping out of audio would hit too. I'm pretty certain that a buffer size of 256 samplesis the lowest latency I can manage without introducing additional pops and clicks, so we will stay at 256.
Any thoughts as to how to solve the problem? The MOTU tech support has also reported this to the development team, so I guess I'll wait for now.
Thanks!
David
Laptop: Dell Precision 3540 with an updated 32 GB of ram and a 2TB SSD. The CPU is Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz 1.99 GHz, and the operating system is Windows 10 version 2004 X64.
Click to read more...
 
The MOTU M2 has had constant problems with dropouts on Windows, which was frustrating when I had one, as it's a truly great interface, but I feel the drivers aren't too good unfortunately :(

I'd tried various buffer sizes and USB ports too. Still a no-go and unfortunately ended up returning it. Tech support gave me the suggestions you've done already. It's a shame to see these dropout issues still occurring.
 
Audio Birdi said:
The MOTU M2 has had constant problems with dropouts on Windows, which was frustrating when I had one, as it's a truly great interface, but I feel the drivers aren't too good unfortunately :(

I'd tried various buffer sizes and USB ports too. Still a no-go and unfortunately ended up returning it. Tech support gave me the suggestions you've done already. It's a shame to see these dropout issues still occurring.
Click to expand...

Really? Now that's tough!! Then, what do you suggest? I was hoping that this would be my ultimate final decision in purchase, sothat everything could be settled...
 
David Lai said:
Really? Now that's tough!! Then, what do you suggest? I was hoping that this would be my ultimate final decision in purchase, sothat everything could be settled...
Click to expand...
This is what I was most frustrated about too and seriously thought it was the best bang-for-buck, which it still is apart from Windows drivers :(. I've not got a new interface yet as most are silly prices due to covid and everything being out of stock most places too.

I've heard good things about Audient interfaces, great converters and they keep updating the latency amount with their driver updates which is cool. Also, the EVGA Nu Audio PCI-e sound card was tested by the Scan Pro Audio team and they recommend it.

I'm tempted by the Focusrite Scarlett 3rd gen series but not sure quite yet as drivers for the 1st gen were pretty bad, but have since improved a lot, still weary though.

I do kind of feel the whole "RME or nothing" bandwagon have a point, but the cost is out of reach for sure unless I spent a long while saving up.
 
Audio Birdi said:
This is what I was most frustrated about too and seriously thought it was the best bang-for-buck, which it still is apart from Windows drivers :(. I've not got a new interface yet as most are silly prices due to covid and everything being out of stock most places too.

I've heard good things about Audient interfaces, great converters and they keep updating the latency amount with their driver updates which is cool. Also, the EVGA Nu Audio PCI-e sound card was tested by the Scan Pro Audio team and they recommend it.

I'm tempted by the Focusrite Scarlett 3rd gen series but not sure quite yet as drivers for the 1st gen were pretty bad, but have since improved a lot, still weary though.

I do kind of feel the whole "RME or nothing" bandwagon have a point, but the cost is out of reach for sure unless I spent a long while saving up.
Click to expand...

That's interesting. Well, being blind means that it would be better if the controls were tactile, and the nobs are not endless encoders, which the MOTU M2 accomplishes beautifully. I only use the audio interface for latency issues, and since it provides balanced outputs for monitors, I can take advantage of that too. This audio drop out thing is the only problem I'm having... Sad!
 
I have the MOTU M4 which uses the same drivers. No dropouts at all. I'm using it with Cakewalk by Bandlab. Running the buffer size at 128 for rock tracks. I usually have move the buffer up 256 if doing classical tracks with about 25 VSTi instances loaded. I could run the rock tracks lower but the latency isn't noticeable at 128 for recording guitar and bass.
 
Not sure if it has to do with conflicts in your laptop.

Just in case (don't want to insult you, so don't be offended, just trying to help with basic stuff, going by elimination).

The Windows audio settings can be a pain sometimes, and sometimes I never know which combination to keep.



Sweetwater has some instructions too:


IMPORTANT: Windows sets the default playback device to Output Channels 3 & 4 on M4 interfaces. You will need to go into Windows Sound Settings and manually change the default output to Channels 1 & 2.
You need to download and install the MOTU M-Series driver in order to connect with a Windows PC. The interface won’t be able to connect without it. Mac computers do not require driver installation, but it is recommended for the lowest round trip latency and stereo loopback inputs. Install the driver software and restart your computer to complete the setup.

  • Windows: Change the Sample Rate and Buffer Size with the MOTU M-Series app.
 
Hi friends!
Replying to a couple of posts here at the same time, so I'll not quote each.
The first post -- really admire you that you don't have any drop outs! You've got yourself a wonderful audio interface in my opinion!
To the second post, you didn't offend me at all. I got the M2, and I did follow the instructions. In fact, my screen reader is echoing back the letters through the M2 interface to my KRK Rokit5 G4's as I type this reply. I'm pretty sure that all my Windows settings are up to date, and power management settings are turned off. According to the email I received from MOTU this past afternoon, they believe it's the USB chipset not being able to keep up with the audio data sent to it. But I'm connecting to a USB C port! I guess the only way to look at it is through Bios, but being fully blind means that I can't navigate Bios on my own, and my house mate doesn't speak very good English to read these things to me. I can't use Team Viewer to do Bios. Is there any way for the Bios to be projected through a phone's camera? ThatI don't know.
 
To the OP, sorry for your troubles. In search of a secondary portable interface (mainly just for location recording of one or two audio tracks) I looked long and hard at the M2/M4 on the interwebs, wanted to like it enough to buy it, but have read enough of these sorts of instability reports (in Windows, not MacOS AFAIK) that I got scared away and got an Audient iD14 instead...

...I figured I knew what I was getting at least: reliability and good pres, even if not RME level RTL, and so far the Audient has worked exactly as advertised and I'm happy with it. It would be great if MOTU gets their driver act together for the M2/M4, but quite a bit of anecdotal evidence suggests they haven't yet done so. It seems to be hit or miss with Windows users, which is a shame, because the feature/price ratio is otherwise extremely attractive.
 
Quasar said:
To the OP, sorry for your troubles. In search of a secondary portable interface (mainly just for location recording of one or two audio tracks) I looked long and hard at the M2/M4 on the interwebs, wanted to like it enough to buy it, but have read enough of these sorts of instability reports (in Windows, not MacOS AFAIK) that I got scared away and got an Audient iD14 instead...

...I figured I knew what I was getting at least: reliability and good pres, even if not RME level RTL, and so far the Audient has worked exactly as advertised and I'm happy with it. It would be great if MOTU gets their driver act together for the M2/M4, but quite a bit of anecdotal evidence suggests they haven't yet done so. It seems to be hit or miss with Windows users, which is a shame, because the feature/price ratio is otherwise extremely attractive.
Click to expand...
I agree with you completely! Actually, all I want is a high-quality output for my speakers, a low latency asio driver for my virtual piano software’s, and a function that allows me to capture my live playing through the high-quality internal recording audio. The MOTU M2 checks all the boxes, but the only problem I’m having is the fact that it cuts out audio from time to time. If there are similar audio interfaces that have easy control, and very important, rotary encoders with boundaries, then I’d be happy to try out another interface.
 
Last edited:
Reviving this thread a bit. Is it possible to increase how much power is fed into the USB port using BIOS? Or should I buy a AC-powered USB hub? Will this solve the problem completely or should I change to a different audio interface?
 
haydn12 said:
I have the MOTU M4 which uses the same drivers. No dropouts at all. I'm using it with Cakewalk by Bandlab. Running the buffer size at 128 for rock tracks. I usually have move the buffer up 256 if doing classical tracks with about 25 VSTi instances loaded. I could run the rock tracks lower but the latency isn't noticeable at 128 for recording guitar and bass.
Click to expand...

Are you using it on a laptop or desktop? Mine is a laptop, the Dell Precision 3540.
 
I build my own computers and pick the components carefully. The software is pretty stripped down and computer is only used for Audio or video editing. I have another computer for running Office apps, paying bills, internet and an occasional game of golf. I have very few issues with either computer. I may see a couple crashes a year.
 
haydn12 said:
I build my own computers and pick the components carefully. The software is pretty stripped down and computer is only used for Audio or video editing. I have another computer for running Office apps, paying bills, internet and an occasional game of golf. I have very few issues with either computer. I may see a couple crashes a year.
Click to expand...

You are certainly a person with lots of patience and determination. Good for you!!!
 
It looks like the dropping audio problem is most annoying after I played a DVD video. Indeed, the audio kept going on and off and on and off... as the video was playing, and after the video it still kept going on and off and on and off and on and off... I wonder if it was something to do with the driver for my MOTU, or is it that my CPU needs greater power?
 
David Lai said:
It looks like the dropping audio problem is most annoying after I played a DVD video. Indeed, the audio kept going on and off and on and off... as the video was playing, and after the video it still kept going on and off and on and off and on and off... I wonder if it was something to do with the driver for my MOTU, or is it that my CPU needs greater power?
Click to expand...
I honestly feel it's the driver that MOTU has made, as many on GS have experienced dropouts on Windows, which is frustrating since they ended up making ridiculously good macOS drivers for the M-series of their audio interfaces.
 
Audio Birdi said:
I honestly feel it's the driver that MOTU has made, as many on GS have experienced dropouts on Windows, which is frustrating since they ended up making ridiculously good macOS drivers for the M-series of their audio interfaces.
Click to expand...

Then do you suggest I hold on to it and wait for them to fix their driver? It's been 3 months since any sort of updates, and even MOTU tech support believes it was the power that's fed to the USB C port not enough for the audio interface, which I find to be really odd -- come on, it's USB C! They designed it for the USB C port and they say that this port doesn't feed the interface much power? That's really strange in my opinion.
 
I've heard other folks saying the MOTU drivers for Windows can have issues for some. If you have a MAC they apparently work great. I wouldn't wait for a fix.
 
You must log in or register to reply here.
Top Bottom