Pro-Tools Empowered ASIO error and MAudio HW error
Posted on 2010-09-12
This is too specific for this forum and no EE category really matches this topic but anyway.
I am an independent tech; this is for my customer.
ProTools M-Powered is SW used by professional musicians. I believe it is made by AVID technologies.
ProTools M-Powered Essentials worked fine on Windows Vista for months with the M-Audio USB mic attached. Then one day out of the blue, when starting the app my customer got the following error (wording of error is approximate but close, not necessarily exact words)
"Doesn't support ASIO interface". Error appears as soon as app finishing loading.
WHAT IS THE SOLUTION, I.E. HOW DOES MY CUSTOMER GET PRO-TOOLS TO WORK AGAIN.
Note: Since the error occured, my customer connected and Windows Plug and play installed a driver for the Yamaha PSR E423 musical keyboard. Now the error when the app starts is "Unable to locate M-audio Hardware". Note: Both the M-audio mic and the keyboard ARE plugged into usb jacks.
Based on a Google search the latter error is driver related and I can PROBABLY solve it.
AND THEN THE ASIO ERROR WILL REAPPEAR and HENCE that ASIO error is the one I really want a solution for in this thread.
If you have a solution for the 2nd error that is Yamaha (or Music) keyboard specific and you are 80% certain your solution will work please ALSO post it here. Otherwise stick to the ASIO error.
PLEASE NO LINKS TO ANYBODY'S FAQ'S OR SIMILAR. Please post ONLY solutions specific to the above error messages, not links to places with solutions to many different M-powered error messages.
ALSO NOTE THAT M-Powered worked fine for months and NO CHANGE (or obvious ones anyway) occured just before the ASIO error. I believe that this will ELIMINATE 90% of the reasons you might come up with for these errors; ie these are NOT errors at initial install of M-powered. The M-Audio HW error above did occur immeidately after Windows Plug and Play installed the driver for the Yamaha keyboard.
Also note I have NOT looked at the Windows Device Manager yet. I will do that when I go onsite ONLY so I cannot tell you about what relavant drivers are or are not installed or which ones have yellow error symbols next to them.
The purpose of this Question is to provide a solution or Diagnosis technique BEFORE I go onsite and have more info. It must be replied to with ONLY what is above.