Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Project could not be loaded error

  • Project could not be loaded error

    Posted by Eric Nicastro on September 6, 2012 at 10:33 pm

    I am using a new MacBook Pro, non-retina running Mountain Lion with Premiere Pro CS6. I’ve been working on a project for the past summer and today, as I opened the project file, I get the error “Project could not be loaded. It may be damaged or contain outdated elements.” In all of the years I’ve used Premiere, I’ve never seen this error. Yesterday though, the project worked fine. I ran the backup to my editing drive overnight like normal and now today, that project file is corrupt. I did go back and open the auto-save files. However, the newest auto-save was corrupted. But the next file opened without issues. Luckily I only lost about four hours of work. But this now has me really concerned. Why did this happen and how can I keep this from happening again?

    Eric Nicastro replied 13 years, 4 months ago 7 Members · 8 Replies
  • 8 Replies
  • Walter Biscardi

    September 9, 2012 at 8:59 pm

    Who knows. Bad sector on the hard drive? Corruption in the drive? Issue with the closing of the project on the last close?

    So many things could have happened both with Premiere Pro and your computer. When you first had that situation happen, what I would have done is to create a New Project and then Import the original project into that. If that worked, then just save the new project with a REV name and move on.

    Corrupted projects happen across all software, this is not unique to PPro.

    Walter Biscardi, Jr.
    Editor, Colorist, Director, Writer, Consultant, Author, Chef.
    HD Post and Production
    Biscardi Creative Media

    “This American Land” – our new PBS Series.

    Blog Twitter Facebook

  • Randy Warren

    October 11, 2012 at 10:04 pm

    I’m running PP CS6 on an older Quad Core Intel Xeon, Lion OS.
    I’m having multiple projects get damaged. I’m saving all my projects to DropBox as a backup solution.
    Do you think that has anything to do with it?
    All my media is local on internal fast SATA drives.

    Some of the projects do share the same AVC media.
    Is it possible that it’s located to one bad clip?

    I’ve found 3-4 versions back in the Auto-Save folder have been able to open.
    It’s SUPER frustrating, to keep losing work like this.

  • Gabriel Regalbuto

    November 19, 2012 at 1:31 am

    I’m having this problem tooo often myself. My files are also saved in a dropbox folder so I’m wondering if that has anything to do with it…

  • Bob Pierce

    November 28, 2012 at 10:20 pm

    Yep, same thing here. Started my project this morning and had the same error (I also store my projects in a dropbox folder). I tried Water’s suggestion but got the same error. Fortunately, you can revert to previous saved versions via the dropbox website which saved me. Scared the beejezus out of me!

    I won’t be storing my projects in a dropbox folder any longer!
    Bob

    Director of Photography • Editor
    http://www.lightstreamassociates.com

  • Gabriel Regalbuto

    November 29, 2012 at 3:42 am

    Out of the dropbox and no more problems! I’ll up the ante though… while the project was on Dropbox timelines that I rendered with Dynamic link through Media Encoder had missing assets. There on the line, not in the encode! Really hosed me.

  • Paul Whittaker

    December 14, 2012 at 9:28 am

    Hello,
    I’m having the same problem too! I’d even created a copy version of a project and now neither will load.
    I was wondering how to access these auto-save versions? that could really help me out.
    I havent been saving anything in drop-box though…

    Thank you

    Paul

  • Trevor Ward

    January 7, 2013 at 3:49 pm

    Auto save versions are in the auto-save folder for your project.

    I’m having the same problems, but I’m not saving my project files to dropbox. They are on the system drive. This is getting to be pretty frustrating. For a month now been using PP and am very frustrated with the experience. I want reliable software. Why is that so freakin hard to accomplish?!

    -Trevor Ward
    Red Eye Film Co.
    http://www.redeyefilmco.com
    Orlando, FL

  • Eric Nicastro

    January 7, 2013 at 5:31 pm

    I kept getting this error frequently across multiple projects. I haven’t had time to delve into why this keeps happening, but I did learn one thing. When the error pops up and asks if you want to restore the project from the auto-save files (at least I think that’s what it asks), hit no or cancel. The new project window in Premiere will open. Then open up the finder and double-click on the project file and it should open fine (it opened fine for me every time). Re-save it as another file name (I just added a numerical value to the end of mine to keep track of how many times I had to do this) and delete the old project file.

    This error may continue to happen, but as long as you’re saving the project and using the auto-save feature, you shouldn’t loose your work. You’ll probably have to do these steps until Adobe finds a solution. Every time this happens, I send the error report to Apple and one to Adobe so hopefully they’re taking notice.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy