You can always roll back again if necessary. I was really hoping the clock source setting on the second unit was the problem. This has worked without issue for over 5 years with M-Audio Lt’s. Restart Windows so it can cycle through fresh and then shut it down. I’m not daisy-chaining any other hardware into it via ADAT or anything. I used to have a MK2, but I wasn’t using that many channels, so I sold it.

Uploader: Tygoshicage
Date Added: 18 March 2012
File Size: 17.54 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 74980
Price: Free* [*Free Regsitration Required]

The incoming audio is all zeros and outgoing audio doesn’t make it to the ‘s.

– Downloads

Microsoft owes me half a dozen tylenol I did notice that Windows 7 ran some sort of huge update on both my systems recently with at least one if not two reboots before it was applied which may or may not be relevant. I’ve taken to using Voicemeeter Unzip and double-click installer, enter OSX Administrator password, and follow on-screen instructions. Of course, first back up any project data if necessary.

It’s the first time I’ve heard of MS Updates causing an issue like this in these forums. I have changed the second unit to get its synch from the world clock input instead of adat. I am really sorry that an update put you through this!


Windows 98Windows AwioWindows I will also try another pc. It did seem to be the machine s were losing sync and freezing up. Supported MOTU products include: Trying to cover across the board here I don’t know if it’s my imagination or not, but it does seem the number of reports of weird behavior increases after Windows updates.

I don’t need security updates. Supports Mac OS X Use WinZip to expand.

[SOLVED] (sort of) MOTU no longer working in ASIO driver mode

I don’t even think adat b is enabled. I have two mk III’s that mot a couple of months old and few actual operating hours. Most likely, there’s either some corruption or confusion within the registry concerning installed drivers.

IOW, it’s being worn out so these issues are starting to occur. Don’t count on MOTU’s more recent drivers making things better. Use this install if you are using one of the supported interfaces below, and are running OSX This time we were also getting random MIDI and “adat b” activity indicated on the front panels with nothing connected. I typically never turn off my mkIII hybrid as its also the desk mixer, but suddenly I lost mkII as audio device.


I used to have a MK2, but I wasn’t using that many channels, so I sold it. And the Oscar goes to Essentials Only Full Version.

One thing I didn’t try was plugging the on it’s own outlet. But I don’t use mine for professional recording, and it has to be a multipurpose computer. I also had a very high pitch tone going out on a different channel.

Google [Bot] and 1 guest. I do not want the latest firewire drivers, I’d rather stick with the legacy which have not changed in several years. I tried deleting and rebuilding the AUD. An old trick I learned back in my Unix days was how to activate a microphone on a remote computer and route it to my own workstation.