Pro Tools 5.1 loosing audio files.

There are a number of explanations for these occurrences:- Before 5.1, Pro Tools located files in part based on a MacOS “folder ID.” This ID remains the same even when folders are moved around on a HD. This could lead to the confusing situation where it was impossible to “hide” files from Pro Tools, even in the trash. In 5.1, file locations are “path-based.” i.e., if folders are moved around the HD, Pro Tools will ask the user to locate the files. It may be that some subset of users depended on the “smarter” folder location logic and are now missing it.- In PT 5.1, file id’s for files in a session must be unique. I’ve heard of at least one user who has run into trouble with this because in some cases he imports multiple copies of the same file into the same session. I’m not sure why he does this. In any case, when a file is imported that has the same file ID as another file in the session, Pro Tools requires that the copy be “stamped” with a new unique ID. The problem with this is that any sessions that are linked to that file will now find that its unique ID has changed and not “recognize” it as belonging in their session (and the find dialog will come up.)- “Save Session Copy In” when copying media creates files with new unique id’s. That means that if you “Save session copy in” and then try to link an old copy of the session to the new media, you’ll find that Pro Tools asks you to locate every file unless you uncheck the “Require matching file id’s when locating files” checkbox in the find dialog in which case Pro Tools will ignore the file id’s and just match based on file names. This is an intended behavior since it prevents users from accidentally trashing audio files with destructive modifications that are used by backed-up versions of their session.- Fade files are deleted and replaced with new files when they are trimmed or deleted. That means that previous versions of a session (created with “Save as”) will very likely find some fade files missing when opened. Pro Tools being unable to find fade files should be considered an expected behavior. The alternative would be to leave dozens or hundreds of orphaned fade files scattered across users drives.

Knowledge Base