alesis multimix8 firewire

[spudsjr]

I have a problem with this device, I had 2 before until they got ripped off.
I replaced them,one works great the other not. Here is the problem
When I have the firewire plugged into the computer, the computer recognizes it, however as soon as I click on the file to update the firmware, the device disapperas and I get a message "device can not be located". I also noticed, when I do click on the firmware update, the firmware version on the device does not show up in the dialog box, however it does show the new firmware version, I have a feeling the chip that holds th firmware data or program is shot, I'm not sure, the device works great otherwise. Is there a way to fix this?

[brandondrury]

I replaced them,one works great the other not.

It sounds like you've already done some troubleshooting then. I hope that's not a bad sign.

You are entering the Screwy Firewire / Firmware World. I've dealt with this a few times.


I'm going to add this to Killer Home Recording: Setting Up, but I'll post the raw version here. (I'm getting a little dizzy so proofreading will have to wait.)

Screwy Firewire Firmware Goofiness

I've had hell a few times when updating the firmware on my Firewire audio interface and it appears that I'm not alone in this one. The most common symptom is the audio interface being lost by computer.

Make sure to re-read the instructions from the manufacturer. There can often be screwy requirements that you may not intuitively expect particularly with when you should turn it on or off.
If there are no not-so-obvious instructions and updating your Firewire card is supposed to be as simple as pressing “Update” we have to get a bit more aggressive and perform some random, psychotic behavior.
Try restarting the computer as is.
If that does't help, try turning the computer off, unplugging the audio interface from the back of the computer, and starting it back up.
I often restart it again. This is little more than mysticism, but it's my belief that it clears something out. What? I have no idea. I'm probably out of my mind, but I swear I've luck with this.
After yet another shut down, I plug the audio interface back in.
Often this clears up the problem.
If this doesn't solve the problem, I follow the same procedure (all the stupid restarts) but I plug the audio interface into a different Firewire port. This often requires a new driver install which may or may not be a big deal depending on the position of the moon and the color of your socks.
If that doesn't solve the problem, I physically move the Firewire card (assuming it's a PCI card) to another slot. I repeat the restart thing.

While I have no explanation for this behavior, it's gotten me through binds on several occasions.

[spudsjr]

Thanks,
I have the firewire plugged into the mainboard firewire slot, but I think I'm going to get a firewire card for the Pci slot, hopefully something will happen. Like I said though, the first one works great, so I have a sneaky suspicion it's probably the 2nd unit itself.