828MKII Problems/Questions

[The Mask AE]

Hi.
I've just purchased the 828MKII FW and i am new to this motu world. So i need help with a few things:

Ok. So the package arrived and the first thing i did was opening the manual. So i found out that i am supposed to install the drivers and then plug the unit etc. So i did that and turned the unit on. The unit turned on and this is what happened: random dots started flashing on the thing for a some time, then faded away but the display never turned on. Should the display turn on as soon as you turn the device on? Also the device is not recognized by windows (SP2) at all. Firewire connection is connected properly and working. So (as i usually do) i started panicking over it. Please help me fast so i can return it to it's owner if something is bad/damaged. Thanks.

[dicduc]

First post first issue...It's happening just the same to me with an 828mkII Usb 2.0. Vista x64 fails to recognize the interface, while uninstalling it I even got a bluescreen of death. Tried on a identical Pc x32 Vista equipped and the 828 runs like a charm. Now tell me who is to blame: the x64 OS or the Motu drivers?

[TheRealRoach]

First off, observe what happens when the MOTU is powered on without being connected to anything (other than the power cable). The unit should do its flashing-christmas-tree display for about 2-5 seconds and then display text information on the screen. The sample clock LED lights should stabilize as well. It should look like it's powered on and "ready".

If the display is still "dead" (which I presume to mean "no lights" as if the unit is off) then I would say there is something wrong with the MOTU. If it only does this when connected to a powered-on computer then it's a driver issue.

There are lots of posts about getting MOTU firewire units to work properly in Windows XP SP2 and SP3.

One of the best things you can do is get ahold of a Windows XP SP1 machine and install the unit. This usually works fine.

[The Mask AE]

Fixed the display. The pin that sends light to the rear side of the display was plugged off (probably during the transfer). Ok so now the dispay works but gives random characters exept in firmware update mode (power on+chan) where it gives a massage like it should be.

Connection problem still stands. I use pci firewire controler that works perfectly with my sony camcoder but does not recognise motu.

Help anyone?

[The Mask AE]

Tried on one more pc and two macs. Both pcs ignored the device but one of the macs reported unknown device. The drivers were installed.

[The Mask AE]

Help?!

[TheRealRoach]

It sounds like something is wrong with the actual MOTU hardware. Especially with mention of the weird characters on the screen.

Do you have the option of returning it to the point of purchase?

In all honesty I would return the unit and while you're at it, exchange it for something like an RME interface.

[The Mask AE]

Hmmm... It's not returnable. I fixed the problem with random chars. Here is what it was (help for future forum-friends):

1. delivery guy must have kicked it very hard so internal memory inside motu snapped out of it's place;
2. random characters started popping
3. opened the device, pressed the memory with my thumb
4. it made a click and went a little bit inside
5. turned on and that's it

The problem that still remains in that hardware is not recognized by cpu at all. It acts like it's not even connected. I would like some help troubleshooting the device with someone here that knows what i'm talking about (unlike motu tech support guy that said it's broken on the 2nd step of my techlink and offered me a 350$+handling repair). I was thinking about replying something like: "I know that it's broken a$$h0|3, i just need help fixing it. xD".

[acidrecords]

connect it to an apple pc and check if it works.

there are often different problems with windows, so check with apple if interface has problem or not

[TheRealRoach]

Ok, this could get a bit hairy, but you can try...
- first off, if you are at all green about registry editing then don't try this. If you're cool, then backup your registry before proceeding
- disconnect all MOTU hardware from the computer.
- uninstall all MOTU driver software
- reboot
- Run-> regedit
- search for all "motu" listings and delete them. (there may be other entries such as MFWaudio, which may also need to be deleted). This process will take a while as you must be careful and thorough.
- reboot
- Install driver Motu 3.6.7.0 available here: http://www.roachmouthrecords.com/MotuFW3670.zip
- reboot
- connect and power your MOTU up.

[The Mask AE]

Nope... That did not work. Still struggling with the following problems:

1. When i try to turn up the volume (ether in standalone or when connected) i get random cracks that are very loud instead of sound
2. Hardware not recognized

Anyone? Help! Thanks!

[The Mask AE]

Help!

[TheRealRoach]

I really sounds to me like something is wrong with the MOTU hardware itself especially since it was damaged straight out of the box. I would return it to point of purchase, or an authorized MOTU reseller and get them to send it in/return it.

[apefist]

I don't think it's a hardware problem. Most likely it's the new drivers. I had no problems with the last version of the XP64 drivers, but when I downloaded and installed the new ones, nothin'. Did someone really suggest using a machine with SP1? Seriously? That counts as good advice? No offense, but if the hardware and software can't capitalize on upgraded technology (with which other products seem to have less issues than MOTU and M-Audio) then it's a failed bit. I love XP64. I love firewire. The MKii just seemed like a match in heaven when I was at the store, but now, it has literally been my frustrating day in hell. Thanks MOTU!

[Mark S]

I don't think it's a hardware problem. Most likely it's the new drivers. I had no problems with the last version of the XP64 drivers, but when I downloaded and installed the new ones, nothin'. Did someone really suggest using a machine with SP1? Seriously? That counts as good advice? No offense, but if the hardware and software can't capitalize on upgraded technology (with which other products seem to have less issues than MOTU and M-Audio) then it's a failed bit. I love XP64. I love firewire. The MKii just seemed like a match in heaven when I was at the store, but now, it has literally been my frustrating day in hell. Thanks MOTU!

It does count as good advice. Read the thread and you'll find that sp2 firewire drivers and later will not allow multiple units to sync via firewire, which pretty well kills the reason to have many of these units in the first place. This fix was found first by high end audio (that'd be us) and video users. You'll find it elucidated on the RME site. It is, at it's heart, a Microsoft problem, but without any input from MOTU (they don't even acknowledge it happens) on this one, it is our problem too. Single units should work fine with almost any driver.

You have a complicating issue of XP64 which may not want to play nice with the drives you are trying to use. Every sound related forum I visit still has extremely mixed revues regarding 64 bit usability. Unfortunately for the next year or two it will still be considered on the cutting edge. As I said in another post, start a new thread to get input from other 64 bit users about how they are configuring their systems.

I feel you pain here. MOTU is no help whatsoever. And I have a couple grand in gear that I'll be looking to sell as my proof.