Unfreezing audio track moves the clip

Tthis is very strange.........
 
I froze a few completed guitar tracks prior to recording a new one on a different track. No big deal. Everything froze as normal. Recorded the new track. Fine.
 
Hit the "unfreeze" button, so I could do some editing. The whole clip instantly moved about 10 measures to the left. Tried it over and over with the same result. Tried it on other frozen tracks, with the same result. Bounced it to a clip, same result on un-freeze. Moved the clip to a new track, hit unfreeze, same result.
 
Not sure that there is any relation, but I also noticed very random crossfades being inserted at the beginning of certain clips, where I did not enter any fades.
 
Funny, I was just saying to myself the other day how well my system was running lately. But this one really has me puzzled.
 
Thanks for any help guys.
 
~Jeff

panup
Did you make changes to the song arrangement while track was frozen?
Frozen track's MIDI is not moved or cut if you for example insert or delete time.

Now that I think about it, I may have. I did move a few tracks around to make room for a new breakdown part, but I don't recall if the tracks were frozen at that time. But these are audio tracks, only, not midi.
 
Is there any solution to this, if indeed moving frozen tracks was the problem?

brundlefly
Probably not. I'd have to check, but I'm guessing 'Unfreeze' is basically restoring the state of the track before the freeze which would include any edits made to the clips after freezing, including their position. And if the restoration of the original positions caused overlaps, and Auto-crossfades is enabled, that would explain the unexpected crossfades. 

 
Thanks Fly. That actually does make sense regarding the freezing. Note to self......don't mess with frozen tracks. Always unfreeze before doing anything to them, editing-wise.
 
So, I guess my only solution is to try to unfreeze, then move the tracks back over to the exact position so the timing is correct; or re-record the guitar parts. The consolation here is, lesson learned, and it was human error, not a bug in my system. So that's good to know......
 
Thanks all.
 
~Jeff