Suddenly my MOTU Ultralite Mk3 Hybrid no longer works in ASIO driver mode in Sonar X3e.  It was working fine, I was working on 2 different projects lately.  I closed Sonar earlier today, then opened it again later and when it came up, it told me that there were no audio devices connected for it to use.  I checked and Windows still had the MOTU listed as working and as the default (all other devices have been disabled anyway).
 
I rebooted and that didn't work. 
 
I went into sonar's properties page and changed the driver mode to WDM, let it run the wave profiler and it comes back and says that it can run the MOTU in 16/44.1 only in WDM.  well, that's not acceptable anyway.  I then try to go back to ASIO driver mode and when I do, it's the same as it was before.  there are no ASIO drivers that it has available anymore.  in ASIO driver mode, there are no recording or playback devices listed and if I click on the ASIO button, nothing happens.
 
What in the world could have caused this and how do I fix it? 
 
thanks in advance for your help.
 
[SOLVED] SEE SOLUTION BELOW

Try reinstalling your MOTU drivers. But before that check for any updates on the MOTU site. 

Maybe try System Restore? (Of course, first back up any project data if necessary).
 

I mostly get that behavior with my UltraLite Mk3 (not hybrid) when I leave the unit on a long time like a day or 3 without powering down. I have to power it off for hours, then turn it back on and it's OK. But in my case, the MOTU isn't detected by SONAR at all, but Windows sees it, as the Inpits/Outputs are listed in the Windows control panel. 
 
 
Sometimes it happens when the unit hasn't been on that long and usually, powering it down and making sure the firewire connection is connected tightly, and then powering it back up fixes the matter. And sometimes SONAR has to be closed before powering off and back on.
 
Don't know if you're connected via USB or firewire, but you can try powering off and then back on to see if that fixes the problem. And if that doesn't fix it, a re-installation of the drivers may help.

Thomas, I've had mine for a long time and have never had it behave that way.  I leave it on a lot.
 
but I did try powering it off and on before the reboot and that didn't solve it.  I'm currently connected via Firewire.
 
John - I was downloading the latest drivers while I was away.  That didn't solve the problem either.
 
JonD - ugh.  I might have to go that route, it might have been a windows update that broke it. 
 
I also tried resetting sonar using SHIFT-click to launch and let it reinitialize.  that didn't help either.

Beagle:
 
I've had my unit since 2006, and it never used to exhibit this kind of behavior until the recent last year. Maybe it's a problem resulting from wear and tear. IOW, it's being worn out so these issues are starting to occur.
 
Just a thought.

Awkward.
 
 
 
 
 
Hardware forum? 
:-)
 
 
 
I don't have any useful ideas about why you can run WDM and not ASIO, but seeing how you have mentioned that you did a recent Windows update, you may want to check this out as a basic early troubleshooting step:
 
from: http://avid.force.com/pkb...oubleshooting/en349411

Enable Legacy FireWire Controller Driver (FireWire interfaces only)

This will change the FireWire controller on your system to the legacy controller previously used on Windows XP and Vista. In many cases, the legacy controller improves FireWire performance on Windows 7 and can resolve many Pro Tools issues such as DAE errors, freezes, and pops and clicks.

• Open the Start menu. Right-click on Computer and choose Properties.
• Click on Device Manager in the upper left corner.
• In the Device Manager window, double-click on IEEE 1394 Bus host controllers.
• Double-click on the controller (or port) that your FireWire interface is connected to.
• Click on the Driver tab.
• Click on Update Driver.
• Choose 'Browse my computer for driver software'.
• Choose 'Let me pick from a list of device drivers on my computer'.
• Choose '1394 OHCI Compliant Host Controller (Legacy)'.
• Restart the computer.

 
Windows updates have been known to install the newer drivers that don't seem to work as well as the legacy driver.
 
Another thing I might try is to completely unplug the device rather than just power it down. Restart Windows so it can cycle through fresh and then shut it down.
 
Connect and power up the MOTU, then start Windows again from a cold boot. See if that gets you up and running.
 
If that doesn't work you might try the old driver that you have been using recently. Don't count on MOTU's more recent drivers making things better. Use one that you know did work. If you try newer ones make sure you have a back up plan to go back to the last known good one, because MOTU, Windows firewire and progress don't always go hand in hand.
 
If that doesn't work use a disc image backup (Acronis, Paragon etc.) to get to the pre update state and see if that gets you back to where you were running as you are accustomed to. If that works... don't re-install the update, until MOTU can comment on the situation.
 
If none of that works, try a different piece of MOTU hardware to see if it is appliance specific.
 
Good luck.
 
 

Also, be sure to check MOTU's free standing driver dialog: MOTU Audio Console.
 
I keep a shortcut on my desktop for easy access, you may have to go look for it in the start menu under MOTU or something like that.
 
Checking out that dialog should give you an idea if this is specific to SONAR or more generalized throughout Windows.

ah, McQ humor! 
 
thanks Mike.  I had the legacy drivers set for 1394 before, I checked and they were still being used, but I reinstalled them anyway just in case, but to no avail.
 
and yes, the audio console works fine, actually, windows media player and streaming audio works just as it always did, it's only in sonar that I can't choose ASIO driver mode where the problem is.
 
I do wish I had another MOTU device to check.  I used to have a MK2, but I wasn't using that many channels, so I sold it. 
 
However, I'm not convinced yet that this is a sonar issue because I tried connecting the MOTU up via USB.  I use firewire because I get better latency with firewire than I do with USB, but USB does work.  or it did.  now it doesn't.  when I try to power the MOTU on connected via USB (even with the power adapter ON), it doesn't boot at all, it just has a blank screen.
 
so this might be a MOTU hardware problem.

thomasabarnes
Beagle:
 
I've had my unit since 2006, and it never used to exhibit this kind of behavior until the recent last year. Maybe it's a problem resulting from wear and tear. IOW, it's being worn out so these issues are starting to occur.
 
Just a thought.

Thomas, very possible.  like I just wrote above, it doesn't seem to want to work at all in USB mode now, so it might be the unit.  I would think that it would be built better than this tho.  I mean, I've only had it about 5 years?