002R - constant playback issues

[Jaymz]

I'm constantly getting playback errors with my 002 rack (7.4). The errors are always one of three

1. The error that suggests lowering the H/W buffer size
2. The error that suggests raising the H/W buffer size
3. The error that states it has been overflowed

No tweaking to the buffer size fixes the problem.

Important note 1 : Upon starting protools, I always get the "update firmware" message. If I go ahead and try update it, Pro Tools will crash after 10mins of "updating". When I start it again, I get the same message. So basically, I can't update to firmware 1.21. I just click "later/cancel" to finish that startup process.

Important note 2 : Trying to play back windows audio through the 002 results in constant skipping/pausing. The 1394 light flashes during every skip/pause which makes me wonder if it's the infamous "power harness" issue. However, I don't think it is since the 002 does not restart (or at least, I don't think is does). Possibly the firewire cable or port, even though both are brand new

[AllAboutTone]

Originally Posted by Jaymz

I'm constantly getting playback errors with my 002 rack (7.4). The errors are always one of three

1. The error that suggests lowering the H/W buffer size
2. The error that suggests raising the H/W buffer size
3. The error that states it has been overflowed

No tweaking to the buffer size fixes the problem.

Important note 1 : Upon starting protools, I always get the "update firmware" message. If I go ahead and try update it, Pro Tools will crash after 10mins of "updating". When I start it again, I get the same message. So basically, I can't update to firmware 1.21. I just click "later/cancel" to finish that startup process.

Important note 2 : Trying to play back windows audio through the 002 results in constant skipping/pausing. The 1394 light flashes during every skip/pause which makes me wonder if it's the infamous "power harness" issue. However, I don't think it is since the 002 does not restart (or at least, I don't think is does). Possibly the firewire cable or port, even though both are brand new

was your 002 working perfect before this started happening ?

[PlugHead]

IMO,

This isn't the power harness issue, more like firmware/driver incompatibilities are crippling the system.

Did you recently upgrade to 7.4?

I'd first work on getting the firmware updated - that most likely is the culprit.

I'm not running 7.4 on a PC - someone else know how to resolve the firmware update for this gent?

[Jaymz]

Originally Posted by AllAboutTone

was your 002 working perfect before this started happening ?

Been like this out of the box. Got it on ebay a few weeks ago. Which has already caused one problem, the bloody ignition pack authorization codes are in Japanese! I hope the seller is not that much of a tool to sell me a defective unit on top of that...

Originally Posted by PlugHead

Did you recently upgrade to 7.4?

It came with 7.4 and I also got the latest 7.4 update from Digi.

[yarrick19]

Is your computer compatible with the 002 rack?!

Check digis website. They are very specific on what systems are supported.

[gearaddict]

I had KINDA the same problem with my 003r..I know this may sopund stupid but...are you shutting down the pc and then turning on the 002...If you try to start the 003 while the pc is on..you can get this problem.....outside of that..you need to update the firmware!!!

[Jaymz]

Originally Posted by yarrick19

Is your computer compatible with the 002 rack?!

Check digis website. They are very specific on what systems are supported.

My comp (Dell XPS M1730) is not listed at all for being compatible or incompatible. Though if this is the case, I'll have to budget for a new comp specifically for audio work. So much for getting the signature BLA mod then...

Originally Posted by gearaddict

I had KINDA the same problem with my 003r..I know this may sopund stupid but...are you shutting down the pc and then turning on the 002...If you try to start the 003 while the pc is on..you can get this problem.....outside of that..you need to update the firmware!!!

Tried what you suggested mate, no luck :(

[C Heat]

Originally Posted by gearaddict

I had KINDA the same problem with my 003r..I know this may sopund stupid but...are you shutting down the pc and then turning on the 002...If you try to start the 003 while the pc is on..you can get this problem.....outside of that..you need to update the firmware!!!

I had this problem too.

002R first then computer. Sorry it didn't work for the OP...

[samwinston123]

What condition was the 002 supposed to be in? Had the seller used it at all?

Before you do anything else, my suggestion would be to try it on a different system, so you can figure out if it's a problem with the 002, or your computer. If it's a problem with the 002, I would attempt to return it.

What OS are you using? (The answer should be XP)

You should check if there are any IRQ conflicts going on between your firewire port and something else. Right click on My Computer and go to Properties. Go to the Hardware tab, and then click Device Manager. Go to View and select Resources by Connection (or Type, doesn't matter). Expand the Interrupt Request (IRQ) category. Find your firewire port in the list, it will probably say Texas Instruments blah blah 1394. The number in parentheses is its assigned IRQ, if there is anything else with the same IRQ, then that might be your problem (especially if it's something like a video card).

This may or may not be the power harness problem; I'm not familiar with all of the ways it can manifest itself. I had it a few months ago where my 002r would never fully power up, it just kept clicking forever. The way I fixed it was to open up the case and plug/unplug the power harness several times, to clean off the contacts. You can try this and see if it helps anything. I don't remember exactly, but the power harness is on the lower PCB, on the right hand side (there are several wiring harnesses). All of the plugs are covered in hot glue, so you'll have to cut through it with a razor blade or something.

[Vum]

Make sure you don't have a cell phone or anything else plugged into your USB port that may introduce some anomalies to your OS.

I was having this exact problem when I would charge my RAZR via USB. I unplugged it, rebooted, and things worked out.

Also, try going to the I/O setting and choose default. Sometimes this helps. Could be a faulty video card as well.

Indeed, if you're firewire cable is plugged into a front ended port instead of in the back, that can cause some problems.

hope this helped.

[Jaymz]

Thanks a lot for all the help lads. I reckon Sam has the best idea, I should really try it on another system to make sure it's not the 002 itself.

[CasadeBomba]

hey man...I had a g4 dual 1.25 ghz go down 2 weeks ago and had a spare one for back up (same model but newer).

i had the same exact error on the "new" mac.

i installed a PCI card with 2 firewire ports and 2 usb ports. once I dedicated my recording firewire drive to the PCI card all was good. so...make sure your digi 002 and firewire drive are not using the same bus...separate them.

the error went a way....by the way..the power failure issue happens when you hear a clicking noise from the digi002 and the firewire light does not light up..that happened to me once...digi sent me a piece to replace inside it and that was that.

hope this helps..

ric

[Jonboy79]

If nothing mentioned here helps then check digi's forum at duc.digidesign.com You say your pc isn't listed in the list of compatible pc's. It very well just be that your pc isn't compatible. You should always check things like that out before you make a purchase like this.

[Jaymz]

I hear ya Jonboy. To be honest, I would much rather it be an incompatibility issue than otherwise. Since I plan on getting a dedicated audio PC either way.

[jerry123]

Just FYI, I had a similar problem, (non-sense buffer errors, blinking 1394 light) and the power harness seemed to be the issue.

I received the unit from a friend, it would only work for about 15 min. before resetting. So I opened the 002r, cleaned the power contacts and it worked fine for almost a year before I started getting errors and flashing lights again. Another contact cleaning fixed it it seems.

I dunno though, could be a ghost.

[thaart11]

Yea I'm having the same problem with a 002 control surface I had to update my operating system to a o sx 10.5.8 in order to run protools 8 and now the firmware won't update and i keep having problems and protools tells me to increase my buffer size. I don't know if its because of the firmware or the protools 8? Help?? I did also get my 002 from ebay I hope I didn't get a defective product.. I don't it because its fully refubished and it had brand new software including p8

[the donal]

Hi,

To resurrect an old thread, I've got a 002 rack with the blinking firewire light problem.

It's been fine for a couple of years with the same firewire card (VIA chipset).

It's a G serial no, so I've replaced the power loom inside. There are two lights inside- 1 lit and one blinking, which I understand to be OK.

I haven't (to my knowledge) hotplugged the FW cable (which I also replaced) and the link light works correctly- ie lit when FW cable inserted and not lit when it isn't, so I'm fairly certain the FW board isn't fried.

But- before I throw more money at the problem (TI firewire card), can anyone suggest anything else?

Ta

D