Hi,
I Have this problem with my MOTU Ultralite MK3, I´ve just installed windows 7 x64 and I can´t get windows to recognize the Ultralite as an output device
Before with XP64 everything was fine...
I have Downloaded the latest drivers and I can control my Motu from Windows BUT I can´t hear any windows sound trough my card...In fact, even if I go to the Device manager the MOTU Audio, The MOTU Audio MIDI for 64 bit and the MOTU Audio Wave for 64 bit are there...
BUT The Output Audio in windows Still says...
"No audio output device installed"
HELP Please, i need to finish a project next days...
Help..."No audio output device installed"
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
-
navalguijo
- Posts: 1
- Joined: Tue Nov 09, 2010 6:33 pm
- Primary DAW OS: Unspecified
Re: Help..."No audio output device installed"
MOTU's Win7 64-bit drivers are badly written. The programmer is obviously a Mac guy who hacked some Mac driver written in C++ to try to work on Windows. His "Windows" driver does so many things all wrong.
Even with the latest drivers, which I thought fixed the problem, you have to be very careful how you power up the MOTU. First of all, it's best to fully power up the MOTU before you even power up your computer (if using the latest drivers. With previous drivers, it was best to power up after your computer was fully booted). By "fully power up", I mean the MOTU completely initializes itself. It will flash various messages (such as "Loading Cuemix FX...", etc) while it's initializing. After several seconds, the display will finally settle upon its input screen. The MOTU is now fully powered up.
If your computer is on, absolutely do not touch any dial while the MOTU is initializing itself. If you do, the MOTU will cause some activity on the firewire bus, which its badly written Windows driver may try to respond to. But the MOTU isn't yet in a state where it properly responds to the driver, so the driver gets hung up in some perpetual wait for the MOTU to do something it never follows up on. In fact, if you power up the MOTU and Windows simultaneously, and fiddle with the MOTU knobs while the MOTU initializes, the driver has a nasty race condition that will actually freeze the Windows boot. You just sit there looking at the remnants of your BIOS screen all day. Now that's a badly written Windows driver.
If you don't see the MOTU when you boot up, here's what you do to get it working. Leave your computer on, but turn off your MOTU. Wait at least 10 seconds before you turn the MOTU back on. It takes that long for the driver to figure out that "something disappeared. Maybe it was an Ultraltie. I better get prepared to check for if it reappears.". If you don't wait that 10 secs, the driver will not have time to figure out something disappeared, and therefore will not ever be ready to look for the Ultralite when you turn it back on. After this 10 secs, turn your MOTU back on. DO NOT FIDDLE WITH THE MOTU KNOBS. Let the MOTU fully power up. Like some sleepy housewife, it doesn't like to be touched until it's "in the mood". After the MOTU initializes, the driver will hopefully notice this kick in the pants, and it and the MOTU may actually talk to each other instead of miss each other like passing ships in the night. Within the next few seconds, you should actually see the MOTU outputs (other than just the SPDIF) listed in Control Panel's "Sounds". Hooray! The Windows driver and the MOTU hardware are now communicating. Don't ever turn either of them off for the rest of your life, lest they never "speak" to each other again (or MOTU finally hires someone who knows how to write a Windows driver).
Even with the latest drivers, which I thought fixed the problem, you have to be very careful how you power up the MOTU. First of all, it's best to fully power up the MOTU before you even power up your computer (if using the latest drivers. With previous drivers, it was best to power up after your computer was fully booted). By "fully power up", I mean the MOTU completely initializes itself. It will flash various messages (such as "Loading Cuemix FX...", etc) while it's initializing. After several seconds, the display will finally settle upon its input screen. The MOTU is now fully powered up.
If your computer is on, absolutely do not touch any dial while the MOTU is initializing itself. If you do, the MOTU will cause some activity on the firewire bus, which its badly written Windows driver may try to respond to. But the MOTU isn't yet in a state where it properly responds to the driver, so the driver gets hung up in some perpetual wait for the MOTU to do something it never follows up on. In fact, if you power up the MOTU and Windows simultaneously, and fiddle with the MOTU knobs while the MOTU initializes, the driver has a nasty race condition that will actually freeze the Windows boot. You just sit there looking at the remnants of your BIOS screen all day. Now that's a badly written Windows driver.
If you don't see the MOTU when you boot up, here's what you do to get it working. Leave your computer on, but turn off your MOTU. Wait at least 10 seconds before you turn the MOTU back on. It takes that long for the driver to figure out that "something disappeared. Maybe it was an Ultraltie. I better get prepared to check for if it reappears.". If you don't wait that 10 secs, the driver will not have time to figure out something disappeared, and therefore will not ever be ready to look for the Ultralite when you turn it back on. After this 10 secs, turn your MOTU back on. DO NOT FIDDLE WITH THE MOTU KNOBS. Let the MOTU fully power up. Like some sleepy housewife, it doesn't like to be touched until it's "in the mood". After the MOTU initializes, the driver will hopefully notice this kick in the pants, and it and the MOTU may actually talk to each other instead of miss each other like passing ships in the night. Within the next few seconds, you should actually see the MOTU outputs (other than just the SPDIF) listed in Control Panel's "Sounds". Hooray! The Windows driver and the MOTU hardware are now communicating. Don't ever turn either of them off for the rest of your life, lest they never "speak" to each other again (or MOTU finally hires someone who knows how to write a Windows driver).