dae error woes and session corruption ??

[prophei]

for some reason, suddenly all my current sessions will not open, and give me an error -9022

i am running pt 6.9.2 tdm
hd3 / 192
osx tiger 10.4.1
g5 dual 2ghz
1.5gb ram

[Rail Jon Rogut]

Have you followed the advice in the sticky Troubleshooting thread?

10.4.2 hasn't been approved yet though.

Rail

[prophei]

yes, i have tried all that...
and i changed my os version... i wrote it wrong =]

[prophei]

it seems that only sessions i have opened and saved from within 6.9.2 are having this issue. i can open older sessions just fine. no matter what i do, i get that error on my newer sessions.... this is very frustrating!

[prophei]

bounce

[DigiTechSupt]

This is a very unusual error.

You could try copying the sessions to another drive, umount the drive that they're currently on and then try open the session. You have to unmount the drive they're currently on to keep Pro Tools from trying to access the audio files on that drive.

Alternately, try creating a new session at the same bit depth and sample rate as the session you're having problems with and use 'Import Session Data' track by track to see if you can narrow down the possible corruption to one particular track.

Beyond that, it may be best to revert to your backups of these sessions.

[AINSLIE]

I have been strugglibng with this error too. On two different systems. G4 / 10.3.8 / PT 6.9.1 / 2GB Ram. And a G5 with 10.4.5 / PT 7.1 cs6. One work around has been to delete the fades folder. The session will then open but do not allow it to recreate the fades. Instead I broke it down to two smaller sessions. The smaller sessions worked fine. BUT watch your fades folder. Once it gets over 30000 fades it will error again.

The other work around is to make a new session and import half the tracks. Consolidate, then import the other half. This is very anooying to me and interrupts my work flow. Surely PT could warn when the fades folder count gets too high or something about the edit density becoming too high .. not just shut us out of our session. This is unacceptable for a pro applic ation in my opinion ...

Ainslie