Activity › Forums › Adobe Premiere Pro › Way to check PPro project for integrity?
-
Way to check PPro project for integrity?
Posted by Ryan Patch on March 30, 2012 at 7:13 pmHello –
I am working on a rather large documentary project with a fair amount of footage (about 5 gigs). The project file has been growing and growing, and we’re at 80 mb now, expanding quicker now that I’m doing more cutting. I know this isn’t huge, but it’s getting unweildy.
Anyway, I was curious if anyone knew of a way to help check the integrity of a project file (like is done with a lightroom library) or “reset” the project file. I have been experiencing hangs on shut-down, long save times, and other things, and can’t get this project to be in a stable editing environment. Does anyone have a suggestion?
I have tried importing the project into another project, but it hangs on the “Import Files” screen.
Ben G unguren replied 14 years, 1 month ago 5 Members · 8 Replies -
8 Replies
-
Shane Ross
March 30, 2012 at 7:37 pmDo you mean 5TB? Not 5GB? Because 5GB isn’t even 30 min of DV footage.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Ryan Patch
March 30, 2012 at 8:03 pmUpdate:
I just waited it out… through the (Not Responding) messages… mainly because I opened up the system monitor and saw that Premiere was looking through every single one of my media and media cache files. 1.5 hours later, it has imported the project into a new one. The new project seems a bit more responsive, and also can exit without crashing!
However, when I exit, I still get an error in an after effects window – which is odd because I didn’t have the AE app open, only Premiere (although I am aware that AE starts when you have AE projects imported into Premiere.)
Runtime Error!
Program: C:Program File… (truncated, but I’m assuming it’s AE because it’s marked as AE in the taskbar)
R6025
– Pure Vital Function Call.Any insight would be great. Thanks!
-
Ben G unguren
March 30, 2012 at 8:09 pmA few ideas:
1. FCP XML + trashing your prefs to “cleanse” the system:
– Export your project as a final cut pro XML. This will strip the project of any PPro eccentricities that might be causing you trouble.
– Trash all your PPro preferences. I’d suggest saving your hotkey prefs so you don’t have to redo them all. But things like window arrangements, etc, I’d just redo them.
– Open your “cleaned” PPro app, and import the FCP XML that you exported into a fresh project.
If the problem was somewhere in the specifics of PPro’s architecture, this might fix it.2. Convert all H264 codecs to ProRes or DNxHD. Obviously, this is going to take up a LOT of space, but it takes longer for PPro to sift through interframe footage (H264, e.g.) rather then intraframe footage (ProRes of DNxHD), and this could be slowing you down.
3. With 5TB of footage, I assume you aren’t using all of it. It’s likely there are events you filmed that won’t be in the film. Remove all that stuff from your project so PPro can get it off its radar.
I’ve found that larger projects can take a long (looooong) time to load in PPro. Same thing with Avid, but not so much with FCP. I think that’s because PPro and Avid must be doing more to catalog or otherwise account for each clip in the project. Contrast that with FCP, where a clip doesn’t even have to be in the browser in order to be used in a timeline.
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Todd Kopriva
March 30, 2012 at 10:13 pmYou didn’t say which version of Premiere Pro. Make sure that you’ve installed the most recent updates. (Choose Help > Updates.) There’s a fix in an update for Premiere Pro CS5 that deals with project files growing too large, with related performance problems.
info about updates: https://adobe.ly/lsrkmJ
———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
product manager, professional video software
After Effects Help & Support
Premiere Pro Help & Support
——————————————————————————————————— -
David Ghast
March 30, 2012 at 10:51 pmHe was asking how to create a more stable project, not how to entirely destroy it by using fcp.
-
Ryan Patch
March 31, 2012 at 10:04 pmThanks for all of the replies –
I am definitely using the most recent version of Premiere, I am militant about updating.
Unfortunately, I don’t want to go to XML because I will loose much of my work with Advanced metadata that I’ve tagged in Premiere (at least that’s what I understand.) Given that the error comes from AE, I’m thinking of splitting out all of my AE comps that are in Premiere and not importing them until I’m back in the final stage of editing. Too bad to have to do that.
Speaking of Metadata, does anyone have any information about what parts of the Metadata you assign in Premiere are written to the file, and what parts are only tagged in the Premiere project? It seems like there should be something equivalent to the Lightroom command to “write metadata to files” or something like that to “bake in” the metadata to the files. This would help with conforming to online files in Davinci when you’re trying to link by reel name / #.
I have run into some more serious problems with a drive on this project, putting that fire out right now and will return to this problem at the beginning of next week. Any additional thoughts are appreciated.
-
Ben G unguren
April 2, 2012 at 3:22 pm[David Ghast] “He was asking how to create a more stable project, not how to entirely destroy it by using fcp.”
Funny…. But in fact, this technique never uses FCP — not the application, at any rate. It only uses FCP’s way of formatting an XML file. I assume this necessarily strips some of the PPro metadata that FCP doesn’t care about. You can then reimport the FCP XML into a new PPro project for a “cleaned” version of your PPro project file.
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
Reply to this Discussion! Login or Sign Up