HELP HELP – Premiere Pro project files are corrupted

[Mike Velte]

I suspect;
Cutting, trimming and moving clips in the timeline records every move into the Project file. Often this can be as many as a dozen or more moves with the mouse for what amounts to 3 keystrokes in the Source window..
Setting In and Out points in the source window and using the Insert command results in much less being recorded into the Project file.
50 Megabytes of editing decisions is probably more than Hollywood editors create for a feature length film.

[Scott Howard]

Hi,

I am most assuredly a newbie, and I’m encountering a host of problems. I won’t burden you with them in this thread–most of them stem from the stupid propensity that XP has to randomly disconnect my 1394 external drive (this is all too well documented online in connection with many brands of drive, many different computers–cold comfort).

Why I’m writing here: if I can manage to fix that crippling 1394 connection problem, I still might be in for “newbie” sorrows, because currently my project file is 20 megs, and it’s only about 1/5 into the film (it’s going to be about 50 minutes long)! I try to do as much in the source window as possible, like setting in and outs points, but then I drag them down into the timeline and edit from there. I think I might just not understand the extent to which one can ‘edit in the timeline’. I remember seeing it in the Help, but I didn’t really understand the principle. All the editing I’ve done before, in earlier versions of Adobe Premiere and in Final Cut, has been timeline-centric.

If you have any tips, please tell me how to cut down on my apparently-out-of-control file size in the future…also, is there a way to go back through the editing I’ve already done and keep the same sequences, but somehow reduce the amount of space they take up???

Thank you,

Scott

[Elizabeth Aria]

I have a corrupted project file as well, and am searching for a solution. I’ve had Premiere CS4 for about 10 months on my computer, and a few months into using it, it developed the charming glitch of not being able to open an auto-saved file at least 70% of the time. It also randomly crashes (“Premiere has encountered a problem …” msg) or just hangs up (“not responding”), quite often.

In an attempt not to loose my hard work so often, I learned to personally save the file every 5 to 10 minutes or so, and under a different name at least a few times per day. I’ve always been able to open a file I saved myself, but hardly ever an auto-saved version of the project.

While I was exporting/rendering my project file through Encore, Encore froze, I closed it, saved the project file in Premiere once again (Premiere was not frozen) closed Premiere and rebooted. After that I could not get the project file open, or any of the auto saved versions open either. Rather than giving me an error message, the yellow loading bar would load all the way to the end, and then just stay stuck. I had a friend try to open the project file on their computer to see what would happen, and they got an error message about the file being corrupted or damaged and that Premiere would not be able to open it.

The project file is around 30megs.

I’m running on a quad-core processor, 8gigs of ram, Windows Vista, terabyte hard drive system that is rated at a 5.9 Windows performance score on every aspect other than the hard-drive.

All other recently saved project files from this film open without a problem, but unfortunately they are missing the clip-by-clip detailed color correction effects that I recently adjusted. And of course, a major film festival deadline is just a few weeks away…