DAE 9060 error- solved!...somehow

[sglittlz]

I think this is the first time I've actually figured out a bug myself. So I had saved a recorded session to an external hard drive that I switch between computers. It played back fine on the mbox and laptop that I used during the session, but my G5 that I use for editing with an 003+ rack kept giving me the error message off the same hard drive. I was surprised because this comp is much more powerful.

My friend suggested I open a blank new session and import just the audio files, not the whole session. I tried it and this did not work, although it did separate each region nicely into different tracks which ended up being individual songs we had recorded. How convenient!

What I ended up doing was copying the entire session data (audio files, wave caches, session data) etc. to the computer's hard drive from the external, then disconnected the external one. I opened the new copied session from the finder off the host comp, not Pro Tools and it plays back fine now, no error messages.

I have absolutely no idea why this worked but I hope it saves others as much frustration as I went through trying to figure this out! ;D

[injectedsenses]

I retrieved this from the Digi site. I assume you read this already, but here is for everyone else:

1. Pro Tools does NOT support RAID arrays. This error can occur if drives are connected to a RAID SCSI controller, or if drives have been striped or formatted with a RAID formatting utility such as "Soft Raid".

2. Corrupt audio files can cause -9060 errors. In this scenario, the -9060 error message will come up in exactly the same spot in the session. A simple workaround is to set the track containing the corrupt audio to "inactive".

3. In one case, a bad Volume Bitmap on the audio drive was the cause (Disk Doctor reported "the contents of the bitmap do not agree with the locations of all files in the catalog").
Run a disk utility on the drive to check it. If an error is found, backup your data, initialize the drive, then restore your data.

4. In one case this was resolved by removing a Jaz drive from the SCSI bus.

5. Norton AntiVirus, Norton SystemWorks, and Virex have been reported to cause DAE -9060 errors on OSX. To remove them run the Norton uninstaller or remove the anti-virus files from Library>Startup Items.

What type of ext. drive are you using? Everything seems to point to your external drive being the conflict

[saudio]

Since you were using one drive between two different computers, I'd assume you had different LOGIN IDs for each computer, hence different permissions. Whenever we use external drives for ANYTHING, we always set the drive to IGNORE PERMISSIONS. This is done in the finder by highlighting the drive and Command-I (get info). At the bottom left of the window that opens is a CHECKBOX. Check it to "ignore permissions" and try again.

This can ONLY be done with external drives and NOT internal, system drives. Internal data drives, other than the system, can also have this applied.

g'luck