Assertion in error when stopping recording.

[Kai Guy]

Hi All

Just wondering if anyone would know a cause for this error and how to troubleshoot. The error was replicable on the same system by doing the following.

Record for <1m, stop, undo recording.
Record for <1m, stop, undo recording.
Record for 1hour (Live concert), stop. crash with following dialogue.

Assertion in "/Volumes/Development/vb_protools_8.0_cpr_2/AlturaPorts/NewFileLibs/CoreFoundation/MacBuild/../../Sys/MacOS/Sys_FileUtilsMacOS.cpp" line 528 while deleting "Perc_02.wav"

Session file became corrupt and a new session had to be created to import all xxxxx_03.wavs

We have also had issues when recording video via the Mojo into ProTools. When Undo-ing record and then stoping the record of any subsequent recording, ProTools will error and and fail to save the video data. The issue does not occur when not using "Undo" of a recording at anytime in the session.

Anybody seen this before or have a possible solution? Your help would be appreciated.

Kai.

System Details.
ProTools HD8cs3
MacPro Quad 2.8Ghz
Mac OSX 10.5.7
HD3 Accel
D-Command
Avid Mojo

[the dude]

Assertion and Neo Access Errors

If you encounter an Assertion Error—an error with a long file path after it,
and ending in a “Line” with a numerical value, you will need to delete your
databases, preferences, and volumes. This error is likely related to
improper maintenance and unmounting of external hard drives.

If you have external hard drives connected to your system, you must
always properly unmount them before turning them off or removing them
from the system, and before shutting your system down. By not properly
doing so, Pro Tools database and preference files can become corrupted,
resulting in these (and other) errors. You also run the risk of corrupting the
Root Directory of those drives, which can result in drive failure and even
data loss.

Deleting databases, preferences, and volumes can resolve other issues as
well, such as I/O Setup issues, graphic or display problems, and other
intermittent errors that are not specifically hardware or compatibility

[Kai Guy]

Thanks for that info.
With students coming and going with all sorts of USB / FW Drives I'm not always able to keep track of their mounting/dismount habits (and maybe I don't want to know). I have applied a logout script to remove all Digi databases on logout, PT prefs are already being deleted and replaced with a default set when a user logs in and out, so I'll see if this improves any.

cheers!
k.