MOTUnation.com

If the BIOS isn't even coming up, it seems to me there's something going wrong with the PCI initialization of that card (by the BIOS). Try getting into the BIOS (without the card installed), and go to the PCI/PnP screen. Instead of resources controlled by "Auto", change to "Manual&quo...

You're using the latest driver from MOTU's web site (not the one on the CDROM)? That dump indicates the problem is the MOTU firewire driver. My Ultralite works fine in Win 7 64-bit with firewire, the standard Win7 firewire stack, the latest driver, and a Texas Instruments firewire chip. Just for a t...

Pretty simple really. Windows allows you to setup multiple "hardware profiles". For each hardware profile, you go into Device Manager, and choose which pieces of hardware you want to disable. If a device is disabled in a given hardware profile, then its drivers aren't loaded. When you crea...

both 32bit and 64bit went down at the same time Got to be hardware (or maybe BIOS) related if it simultaneously affected 2 operating systems. So, did you add any new hardware to your system? Doesn't matter if it's not a firewire device. Any new hardware could affect the system. For example, a new d...

Never knew about that setting. I haven't tried it yet, but I suspect that (when enabled), the MOTU automatically powers up when you turn the computer on. Normally, when the MOTU is drawing power via Firewire, it doesn't power up when you turn on the computer. You need to push the Volume knob. With t...

The "Inputs" page is just one group of settings for all 8 inputs. Whatever settings you apply here affect the recording, and all 8 mixes. But you'll notice that many of those settings are also duplicated on the 'Mixers" page. That's because each pair of output jacks has its own settin...

As far as I know, the reverb returns are only the reverb signal, not the dry as well. So yes, you have to bounce the 4 tracks to 2 if you want them combined. (Although maybe you want to just mix all reverb tracks to 2, so you still have the original dry tracks in case you ever want to remix). But if...

You can't do that directly. You can't send one mix to more than one set of stereo outs. (Although the headphone jack does mirror the main outs, so if you can use that for your headphone mix...). But you have a total of 8 mixes (ie, labeled "Bus 1", "Bus 2", etc). Just set Bus 2's...

The reverb signal is recorded separately (on separate DAW tracks) than the inputs to the DAW (which are always dry). The stereo reverb is labeled "Reverb Return 1" and "Reverb Return 2". Record those 2 DAW inputs if you want to record the stereo reverb. (And of course you need to...

The MOTU outs are at pro level (+4dB). Your powered monitors probably expect the much lower consumer level (-10dB), which your cheap audio card undoubtably was. Just keep the MOTU master level down low, or get an attenuator that converts +4dB to -10dB. (Or buy pro powered speakers that expect +4dB o...

The bug I mentioned is fixed in the latest driver. But in Audio Console, there is a box to check for "wave support for legacy software". Do not check this box. That's what forces everything to 16-bit.

So then it's just that one program (DAW) giving you trouble? What kind of driver is it using (ASIO, WDM, DirectX/DirectSound, legacy MME)?

P.S. Do not run Audio Console and check that box about wave support for legacy programs. MOTU should remove that. It was a bad idea/implementation.

I assume you tried a different USB jack, and disconnected all other USB periferals?

It's definitely a problem with the MOTU thinking you're plugging in a balanced 1/4" cable, and therefore expecting a +4dB signal. But your synth (and cheap mixer) is outputting only -10dB (ie, unbalanced). I had that problem when I plugged a Casio synth in which was -10dB. Even though I was usi...

Do you have any other software that uses ASIO? Even if you install some demo just to test out ASIO, you'll quickly discover whether the problem is the MOTU (or its driver), or that version of Pro tools.

Incidentally, you do see the MOTU listed in Windows Control panel's Audio devices?