Lost communication w/the audio interface (-6097)

[Meko511]

This never happened before with Pro Tools 6.x version.
I recently upgraded to 7.4 a few days ago (aprox a week ago) and now I get an error message.

I can work in a session, record and playback all day....I've used Pro Tools for 7 years now.
But when I stop the session and I'm just sitting there sipping on my cup of coffe or something......
about 30 seconds later I get a popup error message that reads:

"Lost communication with the audio interface. Please try increasing "H/W Buffer Size or removing some plug-ins, and make sure you have a valid clock source. Press OK to reset device. (-6097)"

I have a Mac
Model:........PowerMac3,6
CPU Type:...PowerPC G4 (3.3) 2 MB L3 cache per processor
Dual Processors 1.25 GHz each w/ 1 Gig of DDR SDRAM ( Speed: PC2700 )
Running OSX Tiger 10.4.9 From the Combo update and Pro Tools 7.4 with Digi002

I have tried nearly everything I can think of. I never ever had any problems of this kind with this computer.
Increasing the Hardware Buffer size to the fullest will still cause the error. Sometimes it does it while working in the session.
When I installed Pro Tools I did upgrade the firmware in my Digi002.

I guess the only thing I haven't tried is unplugging my second monitor screen.

Any advise?

Meko

[Forum Member LE]

Don't overlook the 002/002R power harness problem, it's shown up in units with the "G" or later.
If it is you will know eventually since it will lose communication more often and then go to the not power up properly mode.

If you were running external drives (or FW devices) they can also cause your FW bus to drop the 002/002R.

[Meko511]

I'm pretty comfortable saying that I don't think it's related to the power issue on this one. I remember reading about that a little while back, that's a good one to remember. Thanks. The only thing that I am running firewire are the 2 devices listed below which are the 002 board and the external that I am recording on.

How can I tell if I have a "G" ?
This is what I have:

Digi 002:
Manufacturer: Digidesign
Model: 0x1
GUID: 0xA07E0000A30000
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
Digi 002 Unit:
Unit Software Version: 0x1
Unit Spec ID: 0xA3

And I have always recorded into external. I'm recording right now on this:
EZQuest IDE Device 1:

Manufacturer: EZQuest Inc.
Model: 0x1
GUID: 0x30E002E002008A
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
EZQuest IDE Device 1 Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x102
Product Revision Level: 3.54
Sub-units:
EZQuest IDE Device 1 SBP-LUN:
Capacity: 111.79 GB
Removable Media: Yes
BSD Name: disk1
OS9 Drivers: Yes
S.M.A.R.T. status: Not Supported
Volumes:
Pro Tools:
Capacity: 111.79 GB
Available: 79.74 GB
Writable: Yes
File System: HFS+
BSD Name: disk1s9
Mount Point: /Volumes/Pro Tools

I also found this in the log:
Dec 28 14:53:43 Pro-Tools-Mac configd[42]: target=enable-network: disabled
Dec 28 14:53:43 Pro-Tools-Mac mDNSResponder: Adding browse domain local.
Dec 28 14:55:32 Pro-Tools-Mac kernel[0]: ERROR: couldn't open provider
Dec 28 14:55:36 Pro-Tools-Mac kernel[0]: ERROR: couldn't open provider
Dec 28 14:55:48 Pro-Tools-Mac MIDIServer[222]: Driver '/Library/Audio/MIDI Drivers/DIOOSXMIDIDriver.plugin' not loaded because of UUID conflict\n

I wonder if that means anything?

[Forum Member LE]

How can I tell if I have a "G" ?
This is what I have:

It's refers to the last letter of the s/n of the unit.
Digi orignally said the problem had been fixed after a certain s/n but units after that s/n showed up with the problem as well so it's still hard to say.
The real problem is that hard failure of the harness or power supply is pretty obvious, it's when it's intermittent or causing fluctuations that it harder to see.
It can easily make yoiur computer lose communication with the 002/002R without the unit looking like it had any sort of problem.
Also don't forget the 2 most obvious things to try
1) switching which connector on the 002 you have your fw cable attached to
2) try a new fw cable

[Meko511]

Awsome, thanks for that info.
Well so far so good.
I have been working on a session today for at least 5 hours now and haven't had any problems yet.

Before starting today I switched something tho.

In the playback engine screen I changed the "DAE Playback Buffer (disk buffer)" from

1500 ms; Level 2 (Default) to 3000 ms; Level 4

Not exacly sure what's happening here or what that does in detail but I'm good today so far, and trying not to expect the error.

It's a pretty heavy session with all my audio tracks used up. I'm running it on 512 Samples with 21 plug-ins right now. I'm keeping my fingers crossed! Hopefully I'll be done with this song soon because I usually don't run it this heavy. This was a session that was started by someone else at another studio and I'm laying all the vocal work and man is it heavy!

Well..... Thank you so much for all your help. I will keep you posted.

Meko

[Meko511]

Now I'm not getting that error any more but I'm getting a new error and it freezes pro tools completely for about 45 seconds until this new message comes up about exceded or using up too much bandwith and cpu or something between the firewire connection to the hard drive I guess. I didn't get the exact message. I will if it happens again. I just got it again for the second time in the past 2 hours. Then if I open and close the session I get popping sounds in playback.
I have to close Pro Tools completely and restart for the pops to go away. Could it be because I have used up all 32 audio tracks and my hard drive firewire connection can't handle it?
I guess I'll wait til I get the error again and make a new post. Unless anyone else ran accross this before?

[Meko511]

A few Days past and no (-6097) Error!
I added an internal additional hard drive to aleviate the firewire bandwith consumption and so far so good!
I had 32 audio tracks running / 21 plugins and both firewire devices: The external hard drive (400 FW) and the Digi002.
Now all the firewire traffic is all from the 002 and back.


*CLOSING POST*