That Infernal Sound

Moderator: James Steele

Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
Post Reply
saturnius
Posts: 9
Joined: Fri May 16, 2008 8:04 am
Primary DAW OS: Unspecified

That Infernal Sound

Post by saturnius »

No, this is not the name of a punk rock band. . .

I'm referring to the ear piercing, heart stopping "beep" that the 828mk3 is wont to make on occasion. Firmware update 1.05 was designed to resolve this issue, but it hasn't for everyone. My unit, which has the update installed, is back to its old ways again.

The beeping occurs irregularly--sometimes when other programs are running, sometimes not--and not as often now as before the update was installed. I liken it to a heart murmur. It seems most likely to happen during an internet session, esp. when streaming audio. The problem is sometimes severe enough that the 828 has a complete breakdown, and there is for a short period of time (anywhere from a few seconds to a few minutes) no sound at all, neither input nor output.

Last week I was optimistic that the beeping problem had been resolved. I even went so far as to write a positive review of this new device. Ahh, what a fool I was! The fact is--as many of you are already well aware--this unit is defective, and unfortunately there is at present no infallible remedy.

I just got off the phone with MOTU tech support (yes, I actually didn't get a busy signal this time). Here's the lowdown. The problem area seems to be a computer's firewire card. They recommend two kinds of chipsets, TI or Lucent, and one card specifically: Belkin model F5U501. (This has already been pointed out somewhere in this forum I think.) They also recommend a dedicated firewire card, i.e. one without any other devices attached to it, since the 828mk3 "requires alot of bandwidth". Alas, mine is a combo card, with multiple firewire and usb ports, three of which I'm using. MOTU says these kinds of cards are very likely to pose a problem, esp. if more than one port is being used. It is important to note at this point that getting a new and dedicated firewire card is not certain to fix the problem, and can only be a temporary solution at best. It's no guarantee, in other words, that an 828mk3 will work flawlessly on your computer.

That's the bad news. The good news, however, is this: MOTU is very much aware of the problem, and they are working on a new firmware update. Ideally no one should have to get a new firewire card. The 828mk3 ought to be more compliant with more types of cards and computer systems. That's what they're working on now. The tech's last bit of advice for me was "keep checking the website for the latest update", as if to say it should be arriving soon.

So I offer all this for those of you in the same boat, and also for those who haven't yet bought an mk3 but are considering it. Supposedly help is on its way. . . :?
thehowler
Posts: 42
Joined: Mon Nov 12, 2007 6:43 am
Primary DAW OS: Unspecified

Post by thehowler »

Also, check your IRQs and use ProcessExplorer (http://technet.microsoft.com/en-us/sysi ... 96653.aspx) to determine what is going on in your PC at the time of the audio glitch/dropout. My guess is that you'll see the "Hardware Interrupts", and consequently the "DPC"s (Defferred Procedure Calls) spiking which means that you CPU is having to work hard to service the IRQ Steering. This maybe a result of your Network Card and/or your Graphics Card being assigned the same IRQ as your fireWire interface.

I know it's not ideal, but people recommend not using a Network Card whilst doing audio work. I personally don't have the problem with the Network Card being in use and also think that in this day and age it is unrealistic to expect a DAW to not have network access.

Let us know how you get on
Post Reply