Motu ultralite mk3 hybrid driver windows 10

• Fixed a bug in CueMix FX that could lead to a crash or prevent the analysis tools from working. 

• Improved support for Windows 11.

• Added macOS Big Sur support
• Added Apple Silicon support

• Adds support for macOS Catalina 10.15

It has been 5 years since last drivers update for my audio interface. Since the day i bought it i have problems in windows 10. The driver is very unstable.
Motu released the new interfaces and left to die the old ones ?
I see brands like RME supporting drivers for 20 years old hammerfall ADDA´s , user were never forgotten despite the fact they come out with new converters ..
That being said i have to say my days with MOTU are at the end and i will not recommend MOTU devices to anyone. Lack of support and updates for their products

I´m using the mk3 hybrid in USB mode, i had to get a behringer UMC 404 HD to have a proper driver in windows 10 for standard playback, things like youtube, spotify , etc..the MOTU is always crackling and my only workaround is to close all audio apps , reset the buffer size and go back to work.
Even inside the DAWs this happens, no matter what SR or Buffer im using
I did downgrade the firmware, installed the recent one again, etc etc, installed voicemeeter banana so the driver could be always «ON»,replaced USB cables and everything that you might think possible. I did post here in the forum a long time ago and the only support was from users not MOTU. This was a long time ago.

mikehalloran wrote:Do you want to spout nonsense or solve a problem? It’s hard to tell.

Thanks for you reply, i see no help for 5 years, maybe it´s time to get nonsense indeed.
So, what is your expert answer to my «call» ?

I have the same problem … between some things and others, I switched to a Motu UltraLite Hybrid a few weeks ago, because I needed all the analog inputs and outputs it has, with Windows 10.

At first it seemed that everything was fine, but from one moment to the next it’s like he was disconnected!

The inputs, being a digital mixer, if they work and can be monitored. But nothing happens on the PC! I open the CueMixFX and the METERs do not show any type of activity, neither entry nor exit. But I can control the interface from the CueMixFX: volume, monitoring settings, mixes … everything! but nothing goes in and nothing comes out.

It’s like they partially communicate, but not on the audio input and output!

Yesterday nothing of normal reproduction worked (Youtube, some player, etc), but yes Pro Tools, today not even that !!! It is very disappointing, but it is the one I have at the moment …. if you know of any possible solutions, please tell me !!! I am losing a lot of time, and money, for not being able to use it!

I tried these steps: viewtopic.php?f=14&t=36522&p=514355#p514355

But nothing worked …

Yeh, that’s my post from several years ago. Windows 10 has evolved a lot since then, and I’ve found simply reinstalling the (admittedly old) MOTU drivers usually fixes the broken meters in Cuemix by itself. It seldom returns, but it is sporadic and you just never know what triggered the disruption.

On some machines, I have to disable the Motu Audio Wave for 64-bit driver (that’s the Windows audio WDM driver) in the device manager for the rest of the system to work ok, and use Voicemeeter in its stead so that system audio (YouTube, etc.) sample rate changes don’t destabilize the hardware. (Select the MOTU Audio ASIO from the A1 output selector in Voicemeeter and it will sync to your buffer and sample-rate settings, and Voicemeeter does pretty decent sample-rate conversion keeping the hardware unit solid and not having to shift gears internally to accommodate.) That step right there really stabilized things a lot on most of my computers. This Intel Dell (i7 4790) I’m using for audio now doesn’t even care about that — I have the Motu Audio Wave for 64-bit driver enabled and this particular chipset chugs along just fine with it on. The two AMD machines I use now primarily for feeding Vienna Ensemble Pro both hate that driver.

Once these units stabilize, they are pretty stable. Their weakest link seems to be the darn Firewire ports which physically are loose-fitting no matter what cable you buy. I have an Ultralite mk3 hybrid coming in as USB with MOTU Audio Wave for 64 bit disabled on one machine (an HP AMD powered «Edge»), and a previously unstable 828 mk3 hybrid coming in as Firewire into a TI-chipset Siig card (as I need the USB ports!) working pretty stable on this Intel Dell unit with the drivers enabled, like I said. I don’t think it is entirely the hardware — the computers and their chipsets seem to contribute a lot to this puzzle.

Good luck! Try turning off/disabling Motu Audio Wave for 64 bit and reinstalling the driver software. I can also recommend that you go into the Device Manager and go right down the entire list right-clicking and choosing «update driver», let Windows search, and it will likely find some drivers that need updating that COULD possibly be contributing to the problem.

Terry

pepe44 wrote:I opened a techlink and got some fast responses from MOTU.
one that i´m still under test is this recommendation.
If you happen to have a USB intel chipset you might have a go too, and lets hope we get this interfaces to worked properly.

https://downloadcenter.intel.com/downlo … NF-Utility

Thanks for sharing that! As I stated above, most of my problem machines (and chipsets) seem to be in AMD boxes, and my Intel one is working ok, but you know with chipsets it is all the «luck of the draw» what the heck they install along with your CPU at these companies! I look forward to your report back on this.

Terry

Pepe,

I think I am following you but not sure. Are you suggesting that Chrome or Edge (which run in the background even when not browsing) are interrupting GPU resources by using hardware acceleration that way and are thus messing with the thread streams for realtime audio?

…because I can see how that might be possible!

I saw an Nvidia driver mess up realtime audio and MIDI so badly once that MIDI didn’t even work right!

I’ll try it, but I am on a stable system at the moment already, so I’m not sure what will result on my end.

Terry

pepe44 wrote:Yes, correct. I did disable and now my MOTU has been very stable since! Incredible work from the motu tech that was very patient and very professional trying to solve my problem.
Thanks

That’s fantastic!!!!

• MOTUNATION Main Forums
• ↳   Digital Performer [MacOS]: Usage, Techniques, Tips & Optimization
• ↳   Digital Performer [Windows]: Usage, Techniques, Tips & Optimization
• ↳   Digital Performer [MacOS]: Troubleshooting/Criticism
• ↳   Digital Performer [Windows]: Troubleshooting/Criticism
• ↳   Digital Performer: Film/Video Scoring & Post Production
• ↳   MOTU Hardware & MacOS
• ↳   MOTU Hardware & Windows
• ↳   Digital Performer: Tutorial Videos
• ↳   Digital Performer: User Showcase
• ↳   General Recording
• ↳   General Macintosh
• ↳   Music Business
• ↳   MOTU Theoretical Discussions, Gripes, Petitions & Off Topic
• ↳   Composing, Orchestrating, Songwriting, etc.
• ↳   Unisyn
• MOTU Virtual Instruments
• ↳   MachFive
• ↳   MX4
• ↳   Symphonic Instrument
• ↳   Ethno
• ↳   Ethno (OSX)
• ↳   Ethno (Windows)
• ↳   Electric Keys
• ↳   Electric Keys (OSX)
• ↳   Electric Keys (Windows)
• ↳   BPM
• ↳   BPM (OSX)
• ↳   BPM (Windows)
• ↳   BPM (General Chat)
• ↳   BPM (Rants, Gripes)

UltraLite-mk3 Hybrid Update FAQ

Lives for gear

Motu Ultralite Mk3 and Windows 10

Gear Head

Windows 10 and an mk3 here. My setup works great (although i connect with firewire). Have you done the system optimizations? If not, try the guide from Avid…

https://avid.secure.force.com/pkb/ar…e#adjust_power

I think the most important change is the power options.

Lives for gear

I’m on USB2, no firewire on my PC unfortunately.
I’ll try that and post back.
Did you ever had problems or your setup worked right away?
Are you on a laptop (I guess not since only a few have firewire and most chipsets are incompatible)..
Also, what is your buffer size/ latency?

Gear Head

I previously had a Focusrite Saffire Pro 14. Then last year I decided to upgrade to Windows 10 Pro (on a desktop pc) from Windows 7 Pro. I had exactly what you described….. ALOT of crackles and pops. Once I did those optimizations I posted above, everything was great. I then purchased the mk3 a couple months ago, and everything is still fine. While recording I keep the buffer between 64 and 128, depending on how many virtual instruments i have going. When mixing, it can be 1024.

Lives for gear

You actually give a bit of hope as I really thought about selling it and go for something else in this price range but I need DC coupled outputs for my modular rig and MOTUs are the only affordable interfaces that offer such a thing.

I’ll try to mess with all these settings and see if it fixes the problem.

One other thing:
Have you set the sample rate to 44.1 or 48KHz ?

I’ve switched all sample rate options to 44.1 but I think I should have actually left it as is since 48KHz seems to be the preferred rate for most windows applications.

64 to 128 samples is totally workable.Hope to achieve similar results myself.

Joined: Sep 2007

Posts: 59

🎧 15 years

Lives for gear

I think have better perfomance after I’ve done the power options optimizations.
What certainly helped was to close all applications before running Live.
I now have my buffer set to 128 and it seems more stable for the time being.
I’m going to make some use case tests and see if it’s actually stable enough to work with.
Maybe try with 64 samples as well.

I was initially dissapointed since my rme fireface 400 runs flawlessly at 64 samples in a non-optimized Win10 PC r so there’s definitely a driver difference between the two although the other computer has a Xeon processor and a TI firewire card, don’t know if USB 2.0 is comparable.

I’ll make some more tests and post back.

Gear Head

Cool. Glad it’s more stable now.