DAE error 9031 in PT9, fixed?

[Ramtitam]

One of the most annoying errors that I have on PT8 is the DAE error-9031. I ok it and it is commonly followed by a new error saying "DAE is having trouble keepin up blabla" Saying that it is related to a fragmented disk or FireWire trouble.

Is that a bug or is it a problem I shlukd do something about?

If so, has something been done about that in PT9?

[suicune]

Are you talking about the error that began in 8.0.3 where you get a -9019 followed immediately by a -9031, and PT won't then play back again until it has been quit and relaunched?

I only ask because not all -9031s are created equal!!

[Ramtitam]

Originally Posted by suicune

Are you talking about the error that began in 8.0.3 where you get a -9019 followed immediately by a -9031, and PT won't then play back again until it has been quit and relaunched?

I only ask because not all -9031s are created equal!!

Yes, but it's first 9013 and then 9019

[suicune]

Sorry, yeah that's what I meant.

I've been trying and trying to get any information out of avid on this one myself. Full saga over here:

http://duc.avid.com/showthread.php?t=276550

Yesterday they sent me a new PT8 installer to try, but gave me no information about it, it just appears to be a full 8.1 installer. And they still haven't answered when I asked a) if it was definitely a known bug that they were working on and b) if it was fixed in pt9 or not.

[crizdee]

Hi,

I had that problem for a while when i moved to 8 and snow leopard. i found the problem was one of my firewire 800 drives. i now dismount all drives when using PT and haven't seen the problem since.

You're probably going to say you have no external drives connected

Well you could still try dismounting internal drives!! that aren't being used when PT is booted.


Chris

[suicune]

You're probably going to say you have no external drives connected

Got it in one! If you have a spare few hours of your life to waste you could go through that whole thread and see all the rubbish I've gone through trying to fix this including (but not limited to):

Upgrades, downgrades, fresh drives, full disk surface/structure/tree/map scans, permission repair, about 1000 pref and database trashes, RAM test, PMU reset, PRAM reset, reformat of all drives, disconnect of every non-essential peripheral, every system tweak recommended, fresh install (OS and PT) and a partridge in a pear tree.

Every now and again they stop for about a week and I think something I did worked then they'll start up again when nothing's changed and I'll get 8 in a day.

Can't unmount my internals as they are all needed, 1xOS, 1xsamples, 2xworking audio.

[shai_shaashua]

Hello Everybody,
we've hade the same error here at our studio and found that using "Pro Tools Prefs and Database Helper" to remove all pref. helps to make it better. it does come back eventually, sometimes after a few days but it takes only about 5 minutes to fixe it.
i know it's not a cure, but it works.

here is a link:
http://web.mac.com/jcdeshaies/applic...Bienvenue.html

[suicune]

At the risk of repeating myself:

about 1000 pref and database trashe

And I'm really not exaggerating by very much there.

[Ramtitam]

In the PT9 thread there is only one thread with similar problems. I wonder if that indicates that the problems, bug or not, doesn't appear like before?

Can DTS tell us if there are changes in 9 that can decrease the risk of these errors?

[Ramtitam]

I can add that today we had these errors several times. First in one session after trashing prefs and databases, copying the session to an internal disk and ejecting all external disks. And then in a different session with an external disk...

The sessions that was on an external disk contained one (1) instrument track, some auxes and masters. No Audio what so ever. The same session works great in two other identical systems that we have. I'll continue working on it now on PT9. Prefs and databases was trashed.