Participating Frequently

Question

problem with Premiere Pro CS5 project files bloating

Forum|Forum|15 years ago
May 26, 2010
19 replies
54069 views

Has anyone had the same problem that we're experiencing? - we have Production Premium CS5 installed on a machine with Win 7 Pro x64. We have three separate edits all of which are experiencing bloating of the .prproj project file. Often this bloating seems to occur when no importing of assets has occured, just changes in the edits. A project which started at 5mb has bloated to 1.5GB and we can no longer save it. Another project has bloated to 200mb and continues to grow in size. We have not brought in any weird assets, although we are using hi-def footage.

We upgrade from CS3 and never had this problem using Premiere CS3.

We can't fix the problem by 'remove unused footage' as this doesn't reduce the project size, although it does remove the unused footage.

We can't fix it by importing the project into a new clean project as the problem and huge file size just comes with

We can't fix it by using the project manager to collect up the project as it requires to save before collecting and the problem files can't be saved.

A couple of points to note - these projects were originally on Premiere CS3 and were upgraded to CS5. The footage is either Sony EX3 or Canon 5D - both HD.

The machine it's running on has 8gb of RAM.

Currently the projects I'm working on are gradually grinding to a hold with no way to make the files usable again.

Any suggestions are greatfully recieved as I'm at a loss. I've reported this to Adobe, and will report back if I get anything useful.

thanks.

This topic has been closed for replies.

Show previous replies

A

Anonymous

Guess I posted in haste. Thought at first I was suffering from the same issues as the rest of you: large project and cannot save. But although my project was huge, the project file was not nearly as large as these others. Regardless, I tried Jeremy's suggestion and tried importing the sequences into a new project. I first tried several times importing the entire project at once, but it kept freezing up. I thought it still had to do with the size so I tried a few smaller projects, each with only 2 timelines, saving it after each import. This seemed to work until I got to the last sequence. Every previous import took nearly 30 minutes, but this one would "import files" for several hours with no results. I even let it sit over ight and still nothing. There is obviously a glitch with this timeline, but it was identical in nature to the other timelines, just different footage of course. I now know I'm in the wrong thread, but does anyone have any suggestions so I don't have to rebuild this 2 hour video?

Entire project was a 7 day training course. Each timeline was 1 day's worth of video (from 1.5 to 3 hours, 1 video was over 5 hours so I split into 2), about 18 hours total. Added to this was about 400 powerpoint slides and titles. Shot with Canon XH-A1 through OnLocation CS3. I set up HDV 1080p30 sequences as that's what the the Canon shoots and imported the M2T files. Today I found out that these are AVCHD files. Could that be the problem? And how will that affect the video quality? If there's a big difference, I should just be able to use the track select tool and copy the whole timeline into an AVCHD timeline, right?

Premiere CS4, Windows 7

N

Nicketlareriksen

Participating Frequently

Importing the timelines worked. Project went from 8GB to 6,2 MB. If you noticed my last post, the file I mentioned just bloated from about 1 GB to about 8 GB. Only change was moving a few keypoints in the the timeline.

If any Adobe employees want to see how a faulty project looks like, I can make it available on my idisc. Just let me know.

tclark513

Known Participant

A little info on our project...

Mac Platform

HDV

15 minute timeline.

Titles from the titler in Premiere.

That's it!

This project bloated to 10Gig...

One more thing I forgot...I don't know if it matters but CS4 is still installed next to CS5.

A

acmputr

Participating Frequently

I was able to import my base sequence of the band's performance to a new project file. It's 4 cameras in 1920 x 1440 by 83 minutes long. I use it to cut out my indvidual songs. It took almost 1/2 an hour but it worked and my base sequence (minus structure) is now 1.3 MB. A tiny little bugger if ever there was one!

I'm picking the Adobe promo literature up off the floor now....no need to fear, no more stomping today.

A

acmputr

Participating Frequently

Windows 7 x64, CS5 Production Premium

Intel 58X MB, i7 Core 920, 8 GB RAM, boot from 10K WD Raptor, edit from RAID 0 = 2 Seagate 500GB drives run from a Highpoint RAID controller.

Project created in CS4 and upgraded to CS5, Music videos, 4 camera multi-edit sequences. All cameras are Sony professional or pro-sumer cameras.

At about 8 sequences the project file became bloated (825 MB) and I could no longer save, add or remove sequences from the time line or close the program. Basically it loads as it was, I can play the vdeo in the timeline but anything else locks it up.

I was able to copy and paste a sequence to a new project but lost all my structure, but it does save.

I have submitted a bug report and I started my own thread before this one was pointed out to me.

I have other projects both created in CS5 and upgraded from CS4 but not edited enough to experience this problem yet.

I have thrown the CS5 promo listerature on the floor and am stomping it as I write, I feel better with each heel grind.

Mel

jeremy d.

Participating Frequently

I commented early in this thread.

Have I really been relegated to nobody already?

Yeah...it's really a bummer that no one is acknowledging it. It's pretty serious!
I hope Dennis jumps in soon!

the_wine_snob

Inspiring

Have I really been relegated to nobody already?

No Jeremy. Like Harm, I try to ALWAYS read any of your posts, even it the thread does not affect me - yet.

Please keep up the good work.

Hunt

jeremy d.

Participating Frequently

Jeff will tell you, I am emoticonically challenged. I will try to indicate my level of levity in the future.

I was kidding, mostly. I was kind of shocked.

tclark513

Known Participant

Dennis,

I see you are posting at this time...

Can you suggest anything for the problem above?

This is starting to get out of hand.

Thanks!

FW_CC_MAINAuthor

Participating Frequently

TClark,

I'm shocked that you are having the same problem on a mac. This seems to suggest a problem that could be really widespread. You've also beaten my 1.5GB file bloat size.

What the hell is going on with Premiere Pro? I'm surprised to have heard nothing from Adobe either via my support request or on this forum, save for Jeremys useful work around, considering how serious an issue this is.

I've had to break all the projects I'm working on which have multiple timelines in each project into a new seperate project per timeline in order to reduce the file bloat problem and reduce the risk of me loosing all my work in one go on a bloated file.

Adobe - we could do with some help here. It's frustrating to have spent so much money on licences for this software only to have virtually non-existant help when a serious flaw in the software manifests itself.

Nat

tclark513

Known Participant

natswilson wrote:
TClark,
I'm shocked that you are having the same problem on a mac. This seems to suggest a problem that could be really widespread. You've also beaten my 1.5GB file bloat size.
What the hell is going on with Premiere Pro? I'm surprised to have heard nothing from Adobe either via my support request or on this forum, save for Jeremys useful work around, considering how serious an issue this is.
I've had to break all the projects I'm working on which have multiple timelines in each project into a new seperate project per timeline in order to reduce the file bloat problem and reduce the risk of me loosing all my work in one go on a bloated file.
Adobe - we could do with some help here. It's frustrating to have spent so much money on licences for this software only to have virtually non-existant help when a serious flaw in the software manifests itself.
Nat

Yeah...it's really a bummer that no one is acknowledging it. It's pretty serious!

I hope Dennis jumps in soon!

F

fredgilb

Participant

Same problem here. I started the file in cs5.

My back up files started at 4,000kb, 27,000kb, then 207,735kb and won't open.

Also the program is getting slugish. I can't drag the opacity slider but I can make the adjustment on the timeline. Hmmm

That is a great tip about importing seqences, thanks

8 gig ram

HP 8660

ati fireGL 5600

FW_CC_MAINAuthor

Participating Frequently

Selfishly, I'm somewhat relieved that I'm not the only person with this problem. It means that it's more likely that Adobe will look at finding out what is going wrong and fixing it. I'm concerned that Fredqlib is having this problem even with projects that were originated in CS5 rather than being imported from CS3 as this would seem to rule out the idea that it is an import problem which won't happen after the full migration from Premiere CS3 to CS5.

This is a huge problem for anyone experiencing this issue. It's not like an application error which can be fixed by doing a reinstall. Imagine if Photoshop users started experiencing a problem whereby their .psd files bloated and then became unusable, there would be uproar! The life saving work around suggested by Jeremy still has issues such as the fact that doing an import of just a program sequence looses all of the folder structure within the project and the comments from Fredqlib suggest that my fear that the files will just bloat again is likely to happen.

I wonder whether it's got something to do with having 8gb installed. Has everyone who's having this problem got 8GB x64 running?

I logged this problem with Adobe support a couple of days ago but still have heard nothing back. I'll post anything I hear back here.

FW_CC_MAINAuthor

Participating Frequently

I wonder if we can find something that all of us experiencing this problem have in common?

- this is my setup:

Hardware:

8GB ram

Win 7 Pro x64

ATI FireGL V3400 graphics card

Intel XBX2 motherboard

Windows fully patched

Kasperski anti virus

Software:

Adobe CS5 Production Premium, upgraded from CS3

Neat x64 plugin for CS5 for grain reduction

Also tried to install the free RedGiant QuickLooks plugin from Adobe, but it caused Premiere to crash and was uninstalled

Project media:

first project - 1080p, footage from Canon 5D

second project - PAL SD, footage from Canon EX3 and RED

Other:

The projects I'm working on are stored on an external RAID and have been opened and briefly edited on my laptop also, which is the same software setup as above, but without the attempt at installing QuickLooks.

Huntrex

Participating Frequently

these projects were originally on Premiere CS3 and were upgraded to CS5.

That may be your problem right there. Try creating a new blank CS5 project and see if it still happens. It's a best practice to finish the edit on the same software that you started it on. I just bought CS5, but am going to wait until all my CS4 editing is done before I install it.

FW_CC_MAINAuthor

Participating Frequently

Thanks for the reply Huntrex. I have exported my timeline on one of the projects that is almost complete and brought it into a new CS5 project to finish off, to see if that helps. The trouble is that the projects that aren't nearly finished have a load of work on things like grading and re-framing which wont come thorough if I export and EDL in order to get them into a clean CS5 project, which is what I'd need to do. I'm not completely convinced that this is the problem either .... but I agree it's definately something to consider / investigate. The reason we upgraded was because we were having so much trouble with CS3 crashing when handling HD footage from an EX3, so leaving the projects as CS3 until the end of the edit wasn't really an option.

What concerns me about this problem is that I can't seem to find anyone else with the same issue! It's always a relief when there are a whole bunch of you trying to solve the same problem! That combined with the fact that the corruption, if thats what it is, is preventing the projects from being saved is a real problem!

jeremy d.

Participating Frequently

Long Shot:

Have you tried to import the sequences invididually?

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