Participating Frequently

Answered

Premiere CC corrupt project files including auto-save

Forum|Forum|12 years ago
July 19, 2013
12 replies
69391 views

Every single premiere cc project file I have including my auto-save prj files will not load. I get the error message "The Project Appears to be Damaged, it can not be opened". This is for all my Premiere CC Projects. I have uninstalled and reinstalled Premiere with no avail. Is there anything I can do in order to salvage these corrupt files and the work/effort associated with them?

Correct answer Mark Mapes

Thanks, Jim--I've checked through the XML in ExtendScript (couldn't get XML Wrench on a Mac), but always get the same "damaged/outdated" message when trying to open the project again in Premiere. (If XML Wrench has some spiffy built-in debugging thing, I'll [try to] try it, but beyond unclosed tags/basic errors, I'm not really sure what I'm supposed to be looking for in there.)

As it is, I ended up just manually reconstructing the main sequence I needed by laying the footage over a fine cut export. I'm tempted to think that another sequence or two from the corrupt project would be salvageable, though, if I could clean up the XML. ...so the file's still up there in case someone on the Adobe side/anyone more familiar with .prproj file structures is insanely bored and wants another case study to dig around in...

Sorry to hear that you're having such problems.

One thing worth trying in CC:

Create a new project
in Media Browser, go to the old project. When you double-click it, you'll be able to see all the contents--sequences, bins, assets...
try importing your sequences one by one. (I recommend saving after every successful import.)

In this way, you can sometimes access most or all of the edited content in a project that cannot be opened on its own.

W

William Fridh

Participant

Hello everyone with corrupted files,

I recently had a corrupt session with Premiere Pro which cost me multiple project files along with my autosaves. After a long 12 hour intense struggle of learning about .prproj-files and XML code, I've managed to successfully repair my entire project.

Feel free to send over your corrupted project to info@lefourguys.com and I'll have a look.

Also send me information such as:

Error message (when opening project)
Premiere Pro version and OS
Amount of specific effects used (Warp Stabilizer, Twixtor, Magic Bullet Looks etc.)

I'll only charge if I manage to fix the file and I'll send you the cost before I begin the recovery.

Estimated time is between 1-2 weekdays.

Regards

C

Colin5EEC

Participant

Hi LeFourGuys production,

I know this thread is old, but I'm in desperate need of a corrupted project file to be fixed. If you're still able to work on them please let me know. I've tried everything and now my only hope is the code.

avidzombie

Participant

I am reporting the same issue. "The project could not be loaded, it may be damaged or contain outdated elements"

The only thing that changed from yesterday and today was that I logged out of CC on the machine in question to use my laptop at home which I logged in, then out of. Then this morning I logged back into CC and went to resume work and received this message.

I have tried the import project from Media Browser work around and Premiere just hangs... Very frustrating. This is a long reported issue that really leaves the user in a bind, clients breathing down necks... Oh sorry I know the project that we were working on was fine yesterday, but today it just isn't opening, oh and all of the auto-saves are also not opening!!!???

Kevin can you please help?

jeffery wright

Inspiring

I have a deadline today, to render and deliver the project I've been working on all week. Any guesses as to the condition of my project file and ALL the auto-backup files?

That's right - corrupt and unable to open!

Importing into a new project, via media media browser? Deleting the preview files and try re-open the project file? Take another guess as to how those desperately futile attempts worked out.

I have used NO closed captioning or plug in, in my project other than opacity. This 'feature' appears to go back to 2013... and it still continues to inspire people to reflect on the career choices that led them to rely on software like this.

If I had an employee who sold themselves as Professional, and were this unreliable, I'd fire them without a seconds hesitation.

I would much prefer to spend my time working on my projects than spending time hunting down why Adobe products do not do what they say they should do, reading about other people pointing out the same, and having enough time in my day not working, to weigh in with my own hauntingly similar experiences. That and the every other handful of days spent installing the endless stream of updates for each and every program. (Oh look! The progress bar is still sitting at 49% after 10 minutes! I guess I'll just read The Onion instead of working.)

C

chande a k

Inspiring

I had also this type of problem some time ago. Video file appears GREEN in project monitor., I can't edit video. I converted my original video file which I got from my canon mark III., and replaced corrupt video file with this converted file and it worked... I suggest you to try this solution

D

daveg78802948

Participating Frequently

What do you mean by convert? I have built a whole new timeline of the original clips that were corrupted, saved it, rendered it, and exported it to my desktop. When I imported the new timeline into the timeline in question, and saved, the new timeline got corrupted also.

I am using my CC 2014.2 only for closed captioning, and building everything else on my CS6. I don't know if I can trust it every again to build a whole project. Someday, when I am not building shows for TV, and I feel that I have 80 hours to waste building a new timeline to test, I might try CC 2014.2 again.

Why do I have to be in the 2% of editors that have this problem. The channel I am airing on has never hears of this with any of the shows airing on their network.

Dave GatesDakota Sportsmen TV

patshiPJZ

Participating Frequently

I get this regularely on a recent project file in the latest Premiere CC 2014.2. I fixed it by deleting all the preview files in the project folder.

Cheers,

Partick.

D

daveg78802948

Participating Frequently

I must not be understanding you, because when I try to delete a video clip in the project file I get a message on the screen which says if I do this I will delete the clip in the timeline.

Dave Gates

D

daveg78802948

Participating Frequently

The problem I have been having the last few days is that when I save the timeline and go back some of the files are corrupted in the timeline and in the project panel. I have deleted both, and tried to reinsert the original file, but it comes up "green" with good audiio.

It is like the project will not except the original video file again, but I can watch the video in VLC.

I bought CC but I am on a trial basis yet. It is almost like I can't trust this software. I might have to build and render in my CS6, and when done import it to CC for closed captioning.

Anybody have a solution for this? I do not want to get into a situation where I have to build a whole new timeline and import the files one-by-one, then save only to find out it is still doing this.

I just completed a 8:30 second hunt (40 hours) to send to FTW ranch, and I had to cut out one part about the owner and the perfect ending because they both got corrupted and I could not replace them. I was really aggravated because I had no time left to redo, and I had to send them the exported video not up to my normal standards.

Kevin-Monahan

Community Manager

Hi Dave,

Sorry you are having trouble.

The problem I have been having the last few days is that when I save the timeline and go back some of the files are corrupted in the timeline and in the project panel.

It sounds like you have a different issue than a corrupt project file. Your issue has to do with the media, it seems.

I have deleted both, and tried to reinsert the original file, but it comes up "green" with good audiio.

It is like the project will not except the original video file again, but I can watch the video in VLC.

Which camera did this file originate from? Did you ingest it via the Media Browser or some other way?

I bought CC but I am on a trial basis yet. It is almost like I can't trust this software. I might have to build and render in my CS6, and when done import it to CC for closed captioning.

You bought CC but are still on a trial? Sorry, but I don't understand that. Do you mean you bought CS6 but are on a CC trial?

Anybody have a solution for this? I do not want to get into a situation where I have to build a whole new timeline and import the files one-by-one, then save only to find out it is still doing this.

I think we need a lot more info to help you diagnose the issue. I have no idea about your media, computer, etc. It would be helpful to answer these questions: FAQ: What information should I provide when ask... | Adobe Community

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

D

daveg78802948

Participating Frequently

I don't know what model of camera Andrew Garay is using, only that when I drag it in it has 4 audio tracks. Andrew films for Larry Weishun who has had a show on the Outdoor channel and The Sportsman Channel for years, so I feel pretty sure he is using a camera which should not cause problems with CC since the editors for the show are pretty much required by The Sportsman Channel to use Premier Pro so the show producers can add to the content.

I just drag the file unto the project file like I always have been in CS6.

I bought CC and I am paying the monthly charge to use it, but it still asks me if I want to register or continue using the trial.

I am using a PC based computer with Windows 7, which was built by my computer engineer son with a really beefy graphics card. I keep my PC clean at all times and continually scan. I have never had a problem with my PC and CS6.

L

livm77556929

Participant

I am in the same boat. Every CC file is corrupt, the auto saves are damaged, and even the XML I exported as back up won't open. I've lost a week's worth of editing and my edit is due next week. If I have to start over I am going to tell everyone I know how much trouble CC (and CS6 did this once as well) has been.

E

Editing_Guy

Known Participant

ANOTHER WORK AROUND.

I just ran into this same exact problem and this is RIDICULOUS.

Adobe had a similar problem before, but at least the project would open with 5.5.

This is what you have to do, and from what I have read not even the Adobe people here seem to know what to say. (From what I saw so far) This is the best work around that I know.

As soon as you slow down any footage, or use the Warp Stabilizer, etc, you have to render the footage right away by Exporting the Media, and after it is rendered, bring it back into the Project as a new clip. In days gone past, if you trimmed a project and/or copied all of the file of a project, anything that had the speed changed, or reversed, or when using certain plugins, effects, etc, the footage would not make it into the trimmed, and/or copied project properly, but the project would always open and work, unless you Trimmed the Project, and/or copies all of the files.

This was the only time that it was a problem, and I learned the work around at that time, and that was to export the clip right away, and import it back in after it was rendered. (using a Lossless codec, such as Lagareth, and using the best settings)

The technicians at Adobe should be concentrating on getting this problem fixed right away. This is an OUTRAGE!!!

Because of my past experience with Premiere Pro 5.5, I do know that another work around is making a new project and importing the corrupt project in sequence by sequence.

I have seen that solution as a work around,but what is shocking is the Adobe people don't seem to have a clue as to what is going on.

The bottom line is that when you slow or speed any clip, and/or do other things to various clips, use warp stabilizer, etc, it will screw up the program.

That is the bottom line, and this problem needs to be fixed right away!!!!!

Mark Mapes

Participating Frequently

MtlAls: I'm not sure what the relationship is, if any, between the ComponentFactory error message and the damaged/outdated message. We've investigated a few reports of the ComponentFactory.cpp-69 crash (see, for example, Re: Premiere Pro CC2014 error ComponentFactory.cpp-69). With each of the projects that customers have provided, we were able to get only as far as confirming that the project was corrupt. Until we can get a handle on what's causing the corruption, we have little if any chance to resolve the root problem. So the more information you can provide about the project, the better our odds of nailing it down. In particular, did the project originate in an earlier version of Premiere? Did you import anything from an XML, AAF, EDL, ...? In the interest of keeping threads focused, please post to the thread I linked to above. Also, in case you're able and willing to send your project file, I'm going to send you a private message with my contact info.

Barryjedmonton: Thanks for the great detailed information about the case you isolated and your workaround. I'll investigate. Can you clarify what you mean by "trim the project"? If I had to guess, it would be a reference to the old Project Manager's "Create New Trimmed Project" option, but better to confirm than to presume... Also, exactly which version of Premiere are you running? In case you're on a release prior to 8.1 and are not aware of changes to Project Manager, it's been substantially overhauled. Among the changes, "Create New Trimmed Project" has essentially been replaced by "Consolidate and Transcode," which is much more versatile.

By the way, since an element of your outrage seems to be that "this problem" has been going on for so long, I'Il repeat what I wrote in Post #30 above: a common error message is not evidence of a common root problem. That is, a number of completely different issues could lead to projects failing to open & triggering the "project may damaged or contain outdated elements" error message. A quick search of our bug database turned up two fixes in CC2014.0 for bugs that triggered this error message, and two more are open & slated for attention. My point is merely that the error message can be kind of a red herring; it's a relevant data point, but focusing too much attention on it can obscure more important details. To your credit, while you hammered us for not yet fixing "this problem," you also provided excellent details to guide our investigation. Thanks again for that.

E

ebenabbaan

Inspiring

Having the same problem... lost a morning's worth of work, media browser and dynamic link aren't working for me. All Auto-Saves are corrupt.

M

mikeveldstra

Participant

Hi Guys.

Tried al of the above. Updated it yesterday.

1.Reinstalled premiere cc

2. Opened autosave files. (sometimes work then don't work )

3. Open in a new timeline through media browser

When I was able to open old autosaves the playback is choppy but plays until I render.

Then everything starts over again.

error opening file etc.

I have a deadline and really need to open my files....

Any help would be apreciated.

Thanks

T

Two_River

Known Participant

I have a similar issue where I can acutally open my project and edit but when I render or export it crashes or just sits at 0%. Doesnt do me any good when I cant get the edit out of software.

Tried copy and pasting into a new project, replacing all the media on my RAID with the field originals, XMLs, changing sequence settings, etc.

Also while editing it will work for a bit then no video or audio playback then a total freeze.

Any help would be apreciated.

E

EXL_Films

Participant

How can Adobe even call this a professional product! A product that we pay so much per month and then it stabs us in the back! Seriously?

We edited a project for last 2 weeks and we were about to do an export - then adobe crashes. Sorry a serious error has occured. After that the project and all autosaves were corrupt

Adobe if you dont step up your game soon and resolve these issues then I will get our lawyers and sue you for the time and money you have completely wasted not to mention the loss of clients as a direct result to us not delivering on time. You better resolve this and come up with a fix for this corruption. If you dont take all of our project files and fix them and give us back a file that will work then I will go to the next step and I am serious!

I don't want to talk to your tech support who will waste my time

I don't want the blame to be put on somehting i did wrong.

You need to sell software that works.

What is your answer to this?

Also if you dont resolve this our entire company is dropping your software for good!

Kevin-Monahan

Community Manager

Hi EXL films,

Which version of Premiere Pro are you running? This should not be happening as of Premiere Pro CC 7.1, and later.

See Editing Finesse Enhancements-Auto Save Enhancements

"When you specify auto-save to occur at regular intervals, Premiere Pro auto-saves a project on detecting changes to the project file.

The auto-save occurs irrespective of whether you manually save the changes to the project or not. Earlier, Premiere Pro would not execute auto-save if you manually saved within the interval setting.

If the system goes idle for a period beyond the interval setting, Premiere Pro forces an auto-save."

Hope that helps.

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

I

ICAN Entertainment

Participant

Kevin; Its Nov.2015 and I'm running the latest Premiere CC and I get the same issue after saving and the hours I'm wasting trying to solve this issue while still paying you people for a subscription is so very unprofessional !

I never had this problem with Final Cut or CS5.5 are you encouraging me to go back to Final Cut or move to Avid ?

What up with the continued failure ????

No excuses just Fix it or I'll drop it

Lance Gilson

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded