DAE Error -9019 & -9031 since PT 8.0.3

[The Dougfather]

Just started getting this today on LE.

-9019 > Long pause with beach ball and > -9031

Grrrhhhhh, new i shouldn't have updated. Seems to go nuts when melodyne or autotune are used.

[reichman]

Dougfather:

Be more specific about what you upgraded from and to. This is my biggest single problem with PT8. It's not clear from Avid support whether they're going to fix this, or whether it's a quirk of specific systems or drives we're using.

Best,

Nathaniel Reichman

[reichman]

Not fixed in PTLE 8.0.4! Oh well.

[handklang]

i'm working with 8.0.4 now and still have issues with 9019 & 9031. could deleting the digidesign database folders be part of the solution? resetting the RAM? i use only internal SATAs, one for applications, one for projects, one for samples, never had issues with 8.0.1. don´t make me downgrade, avid...

best,
daniel

mac pro 2,8 early 2008 10GB RAM
PT LE 8.0.4

[The Dougfather]

Reichman,

Sorry for the delay, i stumbled across this thread by accident and only usually post in the LE forum.

I have been using 8.0cs3 for a long time, it's not broken so don't fix it right???

So i tried updating to 8.0.3 and the hangs started, went back to 8.0cs3 and now i've updated to 8.0.4 with the exhaustive list of fixes and guess what the hangs are back.

To clarify:

1) I get a DAE -9019 Firewire Bandwidth Error
2) I click ok and get a long pause and beachball before another dialogue (DAE -9031 was Encountered)

Whatever i do now, Pro Tools will not recover, i have to quit out and reload the session and all is fine.

On top of this track solo isn't working probably and it's driving me nuts, i'm really tempted to ditch 8 and go back to 7.4.2, at least it all worked back then.

[The Dougfather]

Just to add, my sessions are on a lacie little disk FireWire 400 drive.

[micline]

Hello All

I am getting the same thing 9031 errors after a long pause, then it just keeps happening. I am using internal sata drives on a Quad Core 2.66 Going to reformat the drives and see if that helps.

Has anyone gotten any further with this?


Thanks

[reichman]

Has anyone gotten any further with this?

No. And it's the single biggest problem I have with my otherwise terrific PTLE/CPTK system.

I'm beginning to wonder if the problem is limited to Leopard. Any Snow Leopard users out there with this issue?

Also, I'm wondering if I should ruthlessly scan all my drives for illegal characters, and change them to legal- even ones not being accessed by Pro Tools. I get the error on small sessions that I know don't have illegal characters.

Avid support, any more thoughts on this?

[spoons]

I'm on snow leopard and get this every time i start Structure ... As long as I stay away from it i'm fine .. .. (i do post so can make do with out, but hey it would be nice to have a sample that works ) .

[micline]

Hello all,

I went back to 8.0 last night, installed from the DVD and the problem stopped. I ran session after session with no annoying errors.

I was going to go up to 8.0.1 just stay a little bit current, but I'm not sure if thats a good idea.

I hear that the fix is to partition your drives as GUID. because of the differences between a PPC and Intel Mac. I hear that the partition map is the culprit. Here is a step by step on how to partition as GUID its at the bottom of the page.

Since I went back to 8.0 and the error stopped, I"m not sure I"m going to try this. Although it does make sense. The only reason I would go up to 8.0.4 is that the import session data retains and imports all my track colors. hate to loose that but WTF, for a stable system its worth the extra time to color the tracks over.

Anyone wanna step up and give it a shot?