Corrupt Premiere CC project

I hope this is already elevated to Adobe Support, but nevertheless:
One morning on opening our big project we got the following error message:
[/sirreact64/releases/2013.03/shared/adobe/MediaCore/Backend/Make/Mac/../../Src/Video/Vide oPreviewCache.cpp-75]
And all the backups stated the same message.
I had to roll back an entire day.
The only thing i could think of was that we had lapsed on renaming and saving as new project for a few days, so we had 20 backups in the list. None of them was possible to open.

The only thing i could think of was that we had lapsed on renaming and saving as new project for a few days, so we had 20 backups in the list. None of them was possible to open.
Better backup practice is 'Save as a Copy". Regularly.
What has happened in your case most likely is... the auto backups are saving a corrupt project file.

Similar Messages

Does anyone have corrupt premiere projects and autosave files?

A Premiere CC project that I have been working on for weeks now is corrupt and will not open. I get a message "the project appears to be damagaed". All of the associated autosave files are also now messed up (some are a month old). Everything else on the drive that contains the projects is fine. Even other older Premiere projects are fine. I open the bad autosave projects in notepad and it is filled with jibberish compared to the other uneffected projects. Is this a bug or have I been hacked by the recent Adobe securiy issue? Here is a link to the project file http://adobe.ly/1awiNVO
All of my autosave files look like this too. How could all of my auto save files change to this jibberish too? I could understand if a save to my current project goes to left field, but how do all of my autosaves get corrupted too?
I have written out large portions of the project to finished movies, but still have a few I will need to start over from scratch if no one has a solution to my problem here. I would really like to have a chance to go back and re-edit if I see anything I want to touch up in the exported movies I have. Thank God I at least have what I do otherwise it would be a months worth of work down the tube. Has anyone else had this issue, or better yet have a fix?

Thanks Jon, I was not aware of the new zip files for the project files in CC. As Ann had confirmed, the project file was actually intact. I moved all of my assets and the project to another machine and it opened just fine. I still do not know why the project will not open on the other machine. Premier will open and start a new project, but I get an error code if I try to open that project. I did start the project in CS6 and convert it to CC when we upgraded, but a bug there still does not explain why the same project works on one computer but not the other. I will do a better job of asset management next time I work on that computer just in case:)

How do I Fix This XML Error From my corrupt Premiere Project?

So I've been trying to recover a corrupt Premiere Pro CC project for the past 3 and a half hours and I think I'm almost there. I kept getting the error "The Project appears to be damaged, it cannot be opened."
Back Story & Info
After hours of searching and trying to repair the project I stumbled upon a thread that said to use an app called "XMLWrench" to repair the raw XML file of the project.
Upon trying to open the project's XML data in XMLWrench I was greeted with complete and utter non-sense code composed of 90% random symbols and alien looking text. But, upon further research I found out that Premiere Pro CC vs CS6 stores the XML data in a some what compressed format. So what I did was add the file extension ".zip" to the end of my project and tried to extract it. Success! The extracted file was the un-compressed XML file which I was able to open and recognize as a Premiere Project.
Now here's where I need help
Now that I can import the XML file from the project into XMLWrench I'm able to scan it for errors. Apparently there appears to be only one. (Thank god, I think...). I'll add an image of the error message below along with a download link to the actually XML file to examine.
Project XML File: MEGA
Thank you!
- Matt

i was able to rename extension to .prproj and it opened in premiere. what happens if you do that? i did open and save it from notepad++, but that shouldn't have done anything to the file...

FAQ: Can I open my Adobe Premiere Clip project in Adobe Premiere Pro?

Yes. When you are ready to export your project to Premiere Pro, begin by tapping the share button in the upper right corner of your screen. Next, simply tap the Edit in Premiere Pro button. Within a few minutes, this will send your project and media to your Creative Cloud folder. Open up Premiere Pro on your computer, and from the Welcome Screen select the option to “Convert Premiere Clip Project” under the “New” heading. Next, choose the project XML file you wish to continue editing in Premiere Pro. All of your project edits will show up in your Premiere Pro timeline, making it easy to continue working.

Since PrPro project is an XML file, you can open it up in any script editor (e.g. Adobe ExtendScript Toolkit) or even text editor, in fourth line find Version="25"
<?xml version="1.0" encoding="UTF-8"?>
<PremiereData Version="3">
<Project ObjectRef="1"/>
<Project ObjectID="1" ClassID="62ad66dd-0dcd-42da-a660-6d8fbde94876" Version="25">
and replace it with Version="23".
Although it works just fine most of the time, bear in mind: everything is at your own peril.

Error Importing Premiere Elements project into Premiere Pro CS5

Hi,
I am working on a multi-part video project that I started in Premiere Elements 8. I put in hours upon hours of editing on the first part and I found that the more I edited, the more often the program would crash (infuriating!). So I started using Premiere Pro CS5 to produce the second part, resolving to come back to the first part later. Well, I've come back around to needing this first part done, and it is just undoable in Elements (crashes every 20 seconds!). I'd like to import that project into CS5 if possible. The help documentation says this should be perfectly possible... but I'm having no luck.
When I attempt to open my Premiere Elements project in Premiere Pro, it tells me the project must be converted from Elements .prel to Pro .prproj, and I click through the prompts as normal. But then as soon as it starts trying to open the project, I get this:
"The Project could not be loaded. It may be damaged or contain outdated elements."
I downloaded the Premiere Elements 9 trial to see if it would be less crashy (and it is), but I'd really prefer to have all my video in one program, and CS5 does the best job (and has most of my hours invested). Elements 9 opens the "damaged" project just fine and I can edit and export normally, so why can't CS5?
Am I stuck recreating the project from the ground up in CS5?

In very general terms, a contemporary PrE Project (PREL), will Open in PrPro, with the steps that you outlined.
Now, there are all sorts of considerations, for aspects that will not likely work:
Instant Movie/Themes, as PrPro cannot read those
Some Effects that PrPro does not have, like the NewBlue FX
Some Transitions that PrPro does not have
Some Title animation Presets, that PrPro does not have
Do you have any of the above in your PrE Project? There are probably other circumstances, but those are all that come immediately to my mind.
The simpler the PrE Project, the greater the likelyhood that it will Convert to a PrPro PRPROJ file.
PrE 8 and PrPro CS5 should be close enough to work, again in those general terms. I can Open simple PrE 4.0 Projects in PrPro 2.0, but cannot Open PrE 7, 8 or 9 Projects in PrPro 2.0.
Good luck,
Hunt

Premiere Elements project imported into Premiere Pro CS5.5 becomes unusable after first save

I have Premiere Pro CS5.5, and I have been trying for some time to successfuly edit an old project that was originally created in Premiere Elements (not sure which version--probably 7.0). It has the .prel extension. The project imports just fine, and I am able to edit it initially. However, if I save my new Premiere Pro project, close Pr and try to open the new project again, I get the "The project could not be loaded, it may be damaged or contain outdated elements." error message. I have tried many of the various project recovery suggestions people have made in this forum and elsewhere online, but none of them seem to work. I even opened the project in XML Wrench, but there were no errors returned when I clicked "check is well formed." Once I close the project after doing some initial editing, it is gone. Is this a known issue? Is there any way I can be able to edit the old project in Pr and save my work? Thanks!

Have you tried using the project manager to re-copy all elements and timeline etc into a totally new directory. I'm just curious to see if that would make a difference. I'd be intrested to see if when making a new project in this manor if it would because as you have stated the normal save methods haven't.

Is it possible to export, and include AE compositions used within a Premiere Pro project, via project manager?

I've several Premiere Pro CC 2014 projects I want to relocate via project manager (one at a time). They're excessive in size (many long and unused footage files), so "Create New Trimmed Project" is the setting-option, within project manager, most attractive. BTW I love how project manager does this... However, when I check on its new location, I don't see any linked AfterEffects files. Fine, I try the other setting "Collect Files and Copy to New Location". This option allows me to now copy everything including rendered scenes featuring my AE compositions (and a lot of excess, unused files)... but still no AE files!
Is it possible to export a Premiere Pro project, excluding unused files, yet include all used files... especially linked files such as AE compositions?

Though not exactly the solution I seek, I've tried an alternative approach... it works (if anyone's interested)... but my original question still stands.
Alternative approach (and probably the only option now):
When I copy & trim my Premiere Pro project via project manager to its new location, I can open the new file and see the track editor now includes broken links to AfterEffects compositions. Since I don't wish to relink these to the current .AEP file, I may package** the original AE project to a location near my newly-located Premiere Pro project folder. To do this, I open the original .AEP file containing any compositions linked to my original Premiere Pro project, and use File < Dependencies < Collect Files. This feature copies all files (and a new .AEP copy) from this AE project to my newly selected destination (as long as no files are missing).
So at this point, when I open my newly-located PP project, I can relink the broken AfterEffects composition links in PP to the new .AEP file. Yay!
**package (for those unaware) is the term used within Adobe InDesign. This feature gathers all linked files that makeup the overall design and layout, and copies into a new folder.

Premiere CS5 - Project Monitor playback is jerky after resintall of operating system and CS5

PROBLEM: Premiere CS5 - Project Monitor playback is jerky
This had NOT been an issue prior to reinstalling the operating system and all software. I have read numerous articles on the forums and have tried everything I can find...with no results.
STEPS TAKEN TO RESOLVE THE PROBLEM:
I have scoured the articles here http://www.adobe.com/cfusion/search/index.cfm?loc=en_us&term=choppy%20video&cat=support&pr oduct=premierepro and others at Cretive Cow
I have installed all updates for CS5 Master Collection, immediately following a fresh install of the operating system and SC5 Master Collection.
I have ensured that sequence settings match resolution and frame rates of footage - the problem persists.
I have tested by importing both standard def AVI files created from tape and high def SONY MP4 files - the problem persists.
I have ensured the latest Video drivers are installed (clean installation selected, so that the Windows default would be removed) - the problem persists.
I have tried the 3D settings in NVIDIA control panel | Program Settings tab... selected Adobe Premiere Pro from the drop down menu | and chaged 'Multi-display/mixed-GPU acceleration from the value of 'Multiple Display performance' to the value of 'single display performance'; although, I ran two monitors before using this latest NVIDIA video driver and I didn't experience this jerky footage issue - the problem persisted after affecting that change; so, I switched it back.
Since I have 96 GB of RAM, I don't use a pagefile. A zero MB page file is the same setting I had prior to rebuilding the C: Regardless of whether I have a pagefile or not, the problem persists.
I have tried creating a fresh user profile, where the user profile is created on the C: drive by default; and, where I left it there on C: to test for the jerky playback in a new PrPR project - the problem persists.
Regarding the C: (system drive) and why I reinstalled everything, it had become unstable and was locking up. I ran DISK ERROR CHECKING with the FIX parameter and the system was still locking up on me. Keep in mind that the System drive is a solid state drive. Anyhow, I had no choice but to dive in and reinstall everything. I wiped the system partition of the SSD using quick format and started installing the operating system. Now, I've read the CLAIM that this cuases performance issues; but, the only place I see issues is in the video monitor playback in PrPr. Everything else - Office applications...printing...browsing the Internet...works just fine, everything is responsive, whereas, I couldn't do ANYTHING with it before.
SYSTEM CONFIGURATION:
The Operating system and all software is installed on C:
All data files and most profile related folders are stored on D:
C:\ (one Intel Solid State Drive - SYSTEM DRIVE) Used Space: 57.5 GB Free Space: 388 GB
D:\ (four Western Digital 2TB drives in an on-board INTEL hardware RAID5 array & hotswapable backplane) used space: 1.28 TB Free space: 4.16TB
Adobe Premiere Pro CS5 VERSION: 5.0.3 (005 (MC: 218798))
Operating System    Microsoft Windows 7 Ultimate Version    6.1.7601 Service Pack 1 Build 7601
System Manufacturer    Intel Corporation
System Model    S5520SC
System Type    x64-based PC
Video    NVIDIA Quadro FX 4800 driver v.320.78
Display        Dell 27" LCD (DisplayPort)
Display        Dell 27" LCD (DisplayPort)
Processor    Intel(R) Xeon(R) CPU           X5680 @ 3.33GHz, 3326 Mhz, 6 Core(s), 12 Logical Processor(s)
Processor    Intel(R) Xeon(R) CPU           X5680 @ 3.33GHz, 3326 Mhz, 6 Core(s), 12 Logical Processor(s)
Installed Physical Memory (RAM)    96.0 GB
Page File Space    0 bytes
PREMIERE PRO CS5 SETTINGS:
Monitor PLAYBACK RESOLUTION: Full
Monitor PAUSE RESOLUTION: Full
(regardless of this setting, the problem persists)
PREFERENCES:
MEMORY:
Installed RAM: 95.9 GB
RAM reserved for other applications: 10 GB
Optimize rendering for: Performance
(Changing this setting to 'memory' does not resolve the problem)
MEDIA:
Media Cache Files
X - Save Media Cached files next to originals when possible
LOCATION: D:\Users...\AppData\Roaming\Adobe\Common
(User Profile folders were relocated to D:\ from within the properties of each folder's 'LOCATION' tab. This is the same configureation I had prior to rebuilding the C:\drive. Testing under a new profile where it's allowed to stay on teh system drive does NOT resolve the problem.)
Media Cache Database
LOCATION: D:\Users...\AppData\Roaming\Adobe\Common
PROJECT SETTINGS:
Scratch Disks
Path: D:\Users...\My Documents\
General
Video Rendering and Playback: Mercury Playback Engine GPU Acceleration
(Setting Viideo Rendering and Playback to 'Sofware' does not resolve the problem)
If any of y'all have any other suggestions, I'm all ears.
Thank you.

I'VE RESOLVED THE PROBLEM!
PREFACE:
OK, I am hoping that through this week-long Operating-System-and-Software-reinatalltion excerise of mine, I have revealed something that everyone -- whom have been cursing Adobe over -- can apply to their systems to resolve this jerky video problem within PremierePro CS5 (and quite possibly other versions, too).
If you've read my post above, you've seen all the steps I've taken to resolve the problem. I've read many posts, some of which have mentioned hardware upgrade / opitmization steps that one may take to enhance performance, and hopefully resolve the problem. I've read where people have taken these steps and have still experienced the problem...and then they curse Adobe. Fer-shame, fer-shame, fer-shame! (nod to Gomer Pyle).
In my case, I knew it wasn't an Adobe issue, as it had worked flawlessly before; and, it wouldn't require a hardware upgrade or reconfigureation, as my system is completely maxed out with two processors, a system drive and a hardware RAID5 array, a CUDA-suported nVIDIA 4800 FX card, and 96 GB of RAM. bla bla bla, puke...whatever. Bottom line is this:
It's not a software issue. It's not and Adobe issue; and Gawd no! It's NOT a PC vs. Mac issue! HA HA. The software had worked swimmingly well prior to the reinstallation / 'lobotomy' I perfomed on the system drive.
SOLUTION FOR ME:
Download and install the updated drivers for the motherboard. Mine is an Intel Workstation Board S5520SC. Intel has an INTEL DRIVER UPDATE UTILITY which automatically scaned my Intel system and identified drivers which needed updating. A very handy, time-saving tool!!! Here's the URL: http://www.intel.com/p/en_US/support/detect?iid=dc_iduu
The scan revealed two Intel drivers needing an update:
Intel Chipset
Wired Networking
and one non-intel driver:
Creative Labs Sound Blaster X-fi
I downloaded and installed these three drivers, rebooted, and tested PremierePro, and was extatic to find this resolved the problem.
If you have a motherboard from another manufacturer, then you may want to navigate over to their wibsite to locate chipset and other updated drivers for your motherboard.
ROOT CAUSE:
While Microsoft Windows 7 Ultimate was able to install certain default drivers during the Operating System installation (keeping in mind that this was done on an Intel Solid State Drive that I formatted using Quick Format) these default chipset drivers apparently weren't current and were ultimately the root cuase of the jerky video playback within PremierePro CS5.
Peace

Can't open Premiere CS4 project in CS5

Having issues opening a premiere cs4 project in cs5. The machine I was using with Cs4 has died, so I'm trying to continue the project with CS5.
Whenever I open the project I get a message saying "this project contained a sequence that could not be opened, No sequence preview preset or file or codec could be associated with this sequence type."
I have the latest version of premiere cs5 installed, and quicktime. The footage I was using was from a Canon 7D.
Thank you!
Patrick

Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037?tstart=0
What is a CODEC... a Primer http://forums.adobe.com/thread/546811?tstart=0
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037?tstart=0
Report back with the codec details of your file, use the programs below
For PC http://www.headbands.com/gspot/ or http://mediainfo.sourceforge.net/en

What is the most efficient way to use Remove Grain from After Effects on large Premiere Pro project?

I've tried to use Dynamic Linking both ways but it doesn't the effects don't appear no matter how dramatic I make them. Why couldn't there just be Remove Grain in Premiere Pro so I wouldn't have to go through the headache of figuring this out. I've tried importing the Premiere Pro project into After effects where everything comes up and, since there's so many files, it doesn't seam feasibly or convenient at all. Trying Dynamic Link vice versa didn't lend results either. What can I do??? Projects range from about a half hour to an hour and a half. Thank you.

The situations are well lit; it might be lack of knowledge on the camera settings itself.
Sort that and your workflow issue dissapears instantly.
There's nothing more efficient?
Yep...read above... but ...any Plugin. eg Neat Video... will take long processing time.
Fixing grain..actually "noise"...is always an image degrading process as well. It blurs!

Keyframes in Speedgrade with a Premiere Pro project

I'm using Speedgrade to grade clips in a Premiere Pro project. I'm trying to adjust a primary layer grade across a clip using different keyframes. It is not working: when I set up a second keyframe, I try to make adjustments to the offset, gamma, and gain in the second keyframe and, while the sliders slide, I'm not seeing any results in either the clip or the scopes.
It's working fine when I create a Speedgrade project. But it's not working with an imported Premiere Pro project.
I can't find any indication of a bug related to this. Anyone have any suggestions?

I've submitted the bug report.
Here's a bit more information about my environment:
MacOS 10.10.1.
Macbook Pro Retina (mid 2012)
2.7 GHz Intel Core I7
16 GM memory
Intel HD Graphics 4000 1024 MB
I have some 3rd party plugins installed in Premiere, but none used in the test case. And in fact I can reproduce the problem with a fresh project by following these steps:
1. Create a new project in Premiere.
2. Import a video file. (The video file is one that I recorded with my Canon 5D mk iii, but the original problem was using files gotten from a GoPro, so that detail doesn't seem to matter.)
3. Create a new sequence.
4. Take a 3 second clip from the video file and put it in the sequence.
5. Take a different 2 second clip from the video file and add it to the sequence.
6. Use the File/Direct Link to Speedgrade menu option to load the sequence in Speedgrade.
7. In Speedgrade, select the first clip. Make changes to the Offset and Gain brightness sliders for that clip.
8. Select the second clip. Position the cursor over the first clip and hit "c" to copy the grade changes from the first clip to the second.
9. Position the read head about midway through the second clip.
10. Hit the diamond to add a keyframe.
11. Make changes to the offset and gain brightness sliders at that keyframe.
12. Hit the keyframe left arrow to move to the initial keyframe in the clip.
13. Notice that the brightness changes made on the original keyframe show in this keyframe. This is unexpected behavior.
14. Attempt to make changes to the offset and gain brightness sliders at this keyframe. The sliders slide, but there are no changes to the clip itself. If you bring up the scopes at this point, making changes to the sliders don't change the scope values either.
Joe

Converting AE project into Adobe Premiere Pro project.

I have found the way to convert AE project into Adobe Premiere Pro project.
I use the following line of code:
app.executeCommand(app.findMenuCommandId("Adobe Premiere Pro Project ..."));
It works. But unfortunately it opens the SaveFileDialog window for the file name to be assigned.
I'd love not to see this window. I'd love to assign the file name programmatically. It would be great!
Is there any way to prevent the dialog window from opening?
Thank you.

Depends if you are on the cloud or not or the new 12.0 version. One way to do it is to import your AE footage into PP as pending on your puter....
Important to tell your version and OS when posting. What seems clear at your end is being asked from someone who has not seen your challenge.

Premiere pro project suddenly degraded

My 50-minute Premiere Pro project suddenly degraded between work sessions. It contains mixed footage - mov files the smallest and the sequence settings match that - and dv footage.
It looked perfect, but when it was opened to resume work on another day them image quality had degraded badly. When rendered It plays ok but is degraded in pause. Color correction is now impossible.
I hope you can help.

For starters, you can't perform a proper color correction using the built in monitors. They are not designed to show you an accurate image, as you're now discovering. You MUST get the signal off the computer and onto a properly calibrated TV. This will ensure you're seeing the signal accurately, which is the first step in color correction. Trying to remove too much red that was put there by an inaccurate display is an exercise in futility.
Having said that, click the wrench under the Program Monitor and make sure Playback Resolution is set to full.

Editing AE or Premiere CS4 projects in Audition 3?

Is there a way to import an After Effects CS4 or Premiere CS4 project with muitiple audio tracks/layers into Audition 3 and edit/balance each track individually? Have been using Soundbooth to clean up audio from individual video clips, but want to balance & add effects to multiple audio tracks prior to rendering final video. Thought Audition 3 might be a better option than using Premiere's audio mixer?

You can't do it quickly and easily but it is possible by making a rough rendered version (DVavi works well) to work with picture in Audition. Import that into Audition where the video and rough audio will be split to give you a guide track. You can then import all your individual audio tracks saved as .wav files into Audition to work on them and make a final mix to re-import back into Premiere for the final render.

Bringing Premiere Pro project into After Effects

I tried importing Premiere Pro projects to After Effects, but I only got the various files, not the timeline. I just watched a tutorial about Dynamic Link, but when I clicked Adobe Dynamic Link/New After Effects composition in Premiere, I got a layer that was all black, with no sound. I have CS3 Production Premium and Windows XP Media Center SP2.
Right now, I just want to keep what I edited in Premiere, but I get better quality video if I export it to H.264 MOV in After Effects than anything I've found in Premiere. I can't understand why that's so, but until I find something just as good in Premiere, I want to save everything in After Effects.

Create a project and a comp. Copy the timeline from Premiere Pro and paste it into the timeline of After Effects.

Corrupt Premiere CC project

Similar Messages

Maybe you are looking for