SUCCESS! I now have ASIO support back and there IS a known issue with this. Thanks to Google and the Cakewalk forum for this info:
http://forum.cakewalk.com/tm.asp?m=1424 ... 2�
After installing the driver... and then turning on the MOTU, Windows will need to finish loading the WDM/ASIO/GSIF/etc drivers for the unit. This is normal behavior (no matter what the manual might say )
If you reload the 3.6.7.4 drivers, you'll have to manually remove the (newer) "mfwaasio.drv" file from the Windows/System32 folder before installing them (the uninstall routine doesn't get rid of it... and it's not backwards compatible).
I uninstalled 3.6.7.4, rebooted. Removed the MOTU folder from Program Files and then removed the ASIO driver from windows/System32. Rebooted. Re-installed 3.6.7.4. Rebooted. Went through the Windows setup as it found my "new hardware" and TA-DA! I have everything back with hopefully fewer/no pops clicks and whistles.
Hope this helps someone else having issues.
Regards,
Jeff
You will LOSE ASIO support if you rollback your drivers!!!
Moderator: James Steele
Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
Re: You will LOSE ASIO support if you rollback your drivers!!!
good catch. I had variable results but that explains why my problems went away after I started manually removing all motu references in the registry and manually deleting all files.
Then I set a restore point,...
Really, the process is tedious since there's close too 800 keys I remove every time I make the effort (about 90 min) These sloppy drivers make a restore point necessary
Then I set a restore point,...
Really, the process is tedious since there's close too 800 keys I remove every time I make the effort (about 90 min) These sloppy drivers make a restore point necessary