In short, this behavior will occur each time you consolidate an alternate copy of a session and then reopen the original session file.The following scenario illustrates how Pro Tools deals with fade files (current versions: 5.3, 5.1.3, 5.2, 5.1.1):-Session "XYZ Original"-- a ton of edits and therefore, a ton of fades....perhaps a few hundred.-With the current session, you are happy with said edits/fades and therefore decide to consolidate regions to help reduce session overhead and maximize Pro Tools performance. However, just to be safe, you choose File>Save As to a new session file before you continue, just in case you need to go back and fix a few fades/edits.-So you save the new session file as "Session XYZ Post-edits" before you consolidate. You are now your ready to consolidate with a clear conscience, thinking that you can go back to session "XYZ Original" to re-edit. This is where things get funky.-As soon as you consolidate your regions and remove unused regions from regions bin (to keep this organized), when you save the session file, you may notice it takes Pro Tools a few seconds to complete the Save command. During this time, Pro Tools is deleting all of the Fade Files associated with the session (you can see the drive accessing, and you will see the fades from Original Session XYZ GONE from the Fades folder). This occurs under the assumption that although you are consolidating, you will no longer need to reference the fade files anymore...so in a quest to save space on your drive(s) it deletes them.NOTE:Upon opening session "XYZ Original", Pro Tools will in fact re-create all of the fades, however, it is a bit frustrating if you have to wait for Pro Tools to rebuild something like 3000 fades.