PREMIERE NOT OPENING FILES

The similarity would be that both the project file and the auto saves were corrupted. I did not realize that the final determinate was that the reason both the project and auto saves were corrupted is that: "The problem seems to be with an instance of warp stabilizer, applied to 'A012C062_240119XI_CANON' (in several sequences); specifically, the relevant effect data/settings saved into the project have somehow become corrupted, which led to malformed .xml getting saved into the project. Any auto-saves of the .prproj before Warp Stabilizer was applied, should work."  "Seems to be..." confused me as to whether or not that was the actual resolution. My bad. The two issues as you say don't seem to be related. Thanks.

Hi CDavid, 

I'm confused; the issue in this thread (warp stabilizer applied to some .mov trackItem) seems completely distinct from any corrupted project issues...

What suggests to you, that they are the same?

Hey Bruce. Was this issue officially resolved? Not having a similar issue at the moment but a while back (different version I think. I could get all the info if you like) Matt Christensen helped me troubleshoot a similar problem with a project being corrupted in a production and the auto-saves being corrupted as well. Matt had the projet "cleaned" into a standalone and resolved the issue. I then imported the project back into the Production and all was well. I think the problem arose when upgrading from 23 to 24. As I said I can get you all the details if you thought that helpful. Thank you!

just sent you a direct message with a dropbox link...

Good choice! I await your access approval.

I sent it as a private message on the adobe forum to you directly...  If you want to send me a message with a direct email address to you, I'll send it again...  Don't think it's fair to post Joshua's project to the world...  (or the entire adobe community).

I have received no such link...?

[Nevermind, hadn't checked the Forum inbox; presumed email]

and as I told you in a email earlier today, I did forward the link for the corrput project to Bruce...  Radio silence so far.

Joshua, thanks for getting back to us.  Hopefully Bruce Bullis will get back to us with some clues as to what's going on...  Had you quit Premiere and shut down your computer in that last 48 hrs?  Wondering if that might be part of the problem.... as I don't think the corruption of the project and autosaves would not have been evident with out doing this.   As I said, I maybe saw this issue 8 years ago or so, but not since.  My workflow of keeping my projects in a folder that's automatically mirrored on and Dropbox and my autosave folder on my media drive may be partly responsible...   And although I don't shut down my computer most nights, I do quit premiere at the end of the work day.