DAE error 9131 / MAC NOOB!

forgot to post a potentially important detail: the content library files (.dat) for strike and xpand! were already on the external firewire drive (along with many VI libraries) that i use with the windows system. so i deleted the .dat files the setup utility puts on the system drive and moved the "set content location" app to redirect the VIs to the external drive. both strike and xpand seem to be happy with this, they play just fine without audio in the session, but is it possible the .dat file is slightly different for mac and windows and is somehow confusing protools? just a thought...

1 more thought: just went thru the recommended digi optimizations again and realized the FW drive wasn't listed in the "spotlight" exceptions under the "privacy" tab. so tried to drag it in there but it won't take! what's up with that? does it matter? digi recommends all drives in use should be listed there... 1 more session: also created another session with no VIs whatsoever, put up a single audio track and tried to record to it. armed the track, press spacebar and error 9131 pops up immediately! PT frozen.

The non-Mac formatted FireWire drive is most likely the problem. Try removing it and then resetting your system using the . After that, make a new session (no VI's) to test again. If it runs fine, then you might need to transfer your sound libraries to a Mac formatted and possibly internal drive. What drive had the audio that you imported? VI's might run okay from a non-Mac formatted drive, but audio certainly won't. Also, a couple other issues might come into play here: 1) You are not supposed to combine drive types for a session (internal + FireWire) 2) Make sure your dual 1.8 isn't the one that's not supported .

hi scott & c-tone, thanks for your replies. scott - is definately not a midi thing all the VIs are running flawlwssly. c-tone - re-checked all compatibility docs etc, the machine and all my hardware is suported. and reading from a FAT32 drive is totally supported (not writing, but i was never writing to that disk--it's only for sample libraries) had another idea and it seemed to work! just created another a test session on the host drive and was able to record audio to it, which tells me my audio drive is the problem. the audio drive was originally used on a windows system and i just did a quick format when i put it in the mac machine--so that may be it. just in the process of re-formatting the audio drive from the mac again, maybe it didn't take the 1st time... will post back results. fingers crossed...

Better yet, try this and also get Super Duper for doing smart backups from your system drive to a partitioned firewire drive. Here's the other link:. The software if free and it works wonders for general Pro Tools and Mac permissions, database trashes and all the preference files.

yup that was it! re-formatted audio drive to OS Extended (Journaled), this time selecting to write new zeros over the entire disk, and presto--problem solved! scott - thanks for the tip, i'll check out that software for sure. sounds alot like the digi "tech support folder" utility, which i use all the time to trash prefs etc. similar? c-tone - yup, you gotta steer clear of the GUID partition map deal, i read that on answerbase too. good eye... cheers - steve :)