-
PPro2 sucking up memory then crashing
Hi all
I have been working on a project for over a year now and am trying to make the final fixes then put to tape.
Stats: PC 3.2 2gig dual ram windows xp pro sp2 nvidia GeForce FX5200, 300GB sata mobile rack drive. I have no capture card it is all dv.
The project file is 280MB in size and length is 80 minutes.
My problem is that it is not only running very slow to render out work area’s ( 2-3min for 15 seconds)it’s very slow for anything I do especially opening up a title to edit ( as in end credits etc).
If I save invariably not long after I will get an out of memory error or some system error or serious error etc etc. It’s not only saving either, if I play a part of the time line then trim a couple of clips or adjust opacity etc the same thing. I have had the Task Manager open as I am doing things and I have noticed that as I do stuff the memory usage just keeps getting bigger and bigger and doesn’t reduce at all then I get the crash.
Do I simply need more memory? If so I didn’t think PPro could access over 2GB anyway.
Your help would be most appreciated as I have missed far too many deadlines with this one and everyone is getting rather ticked off.
Regards
LanceOne Good Eye is all you need!
-
24 Replies
-
I have seen project files of 50-60 MB bring systems to their knees. I am quite curious how a Premiere project file could possibly get to 280 MB. Does it in any way have anything to do with working on this project for a year? How many hours do you have involved in editing? Do you have only one hard drive?
I would be thinking about a bailout strategy. Delete all video and audio preview files. Try to export your project as a DV.avi file. Put this file in a new project for further editing or export to tape. Failing that, export 20 minute chunks and reassemble in a new project. -
What sort of project is it? How do you get a 280 MB project file?
As Mike states, PPro 2 is pretty well known for having issues with project files of 50-60 MB…even a bit less sometimes. It seems to be a combo of the number of clips combined with the complexity of the edit that do it.
Is the cut pretty much made? Maybe you could use the project manager to trim unused media and cut down the size of the project… Make sure you delete the preview files as well to free up some space.
TimK,
Director,
Kolb Productions,Creative Cow Host,
Author/Trainer
http://www.focalpress.com
http://www.classondemand.net -
Thanks guys for your replies.
How did it get to 280MB? Can’t say I really know it just did.
It’s a documentary 80 minutes long, I thought Premiere could handle that. I had read where it can’t handle over 3 hours on the timeline so thought I was well safe.
There is about 300 hours of editing, the project has been trimmed, There is a fair bit of slo-mo and I have luma corrected the whole thing and colour corrected about 7 or 8 clips.There are about 8 or 9 high res photos which I have panned in after effects and exported as quicktime and I have 10 minutes of subtitles which I created in Premiere’s titler.
I am virtually there, 4 more things to change and she goes out, I’m just struggling to make those last changes. I don’t understand enough how PPro handles things to figure out the issues here. I have been contemplating buying a decklink card, would this make a difference?
I will probably get it out in pieces and start a new project, thanks for that I never thought of it.
One Good Eye is all you need!
-
Once thing I recently noticed is an issue withy color finesse (versions prior to 2.0) with PP2. I’m not sure how you color corrected, but it’s just a thought.
Vince
-
I cut a weekly show and I have found that project size grows based on the elements and number of clips more than the length of the project. When I run into problems with project size save a duplicate project and then I pare down the unused media clip by clip in my bins and that helps me make it through the final innings. Since the main work is done I then do what is needed to get it on tape. Success in Premiere at least for me revolves around keeping the workflow clean and lean. hope this helps….
Steve -
Vincent: I colour corrected using Premiere’s tools.
Steve: I have learned the hard way about Premiere’s limitations. I normally work on 2-3min promo’s and tv adverts so have never had to deal with this before. Is this limitation normal for this level of app? How does Final Cut handle it?
Cheers
L
One Good Eye is all you need!
-
Sounds like nested sequences to me. Do you have any? If you are working on an original sequence that has been nested you are going to bring the system down to a hult. The trick is to turn the little eyeball off on the video track for the nested sequence. This way premiere is not trying to display the results in both places. This way you can edit the original sequnces as fast as it was from the beginning.
-
…or it could be the number of sequences. In Avid land I would save a sequence for every day. In PPro land I use 1-2 sequences and save a new project file everyday.
Brian
-
Lance,
In my experience FCP is pretty solid and I have even used the first version of Final Cut Express on a second rate mac with 1 USB hard drive and I have never had the issues that I have had with Pro with crashes and hang ups. I have made it a point not to say too much about it because Cutting software is like politics and everyone has a take. However even the most hard line apologists have to admit the serious limitations that come with project sizes. I say it is a glaring issue especially if you do not plan ahead for it. Adobe is a pig with resources and frankly that is definitely a deal killer depending on if you have a paying client sitting right over your shoulder that has a hodge podge of footage and elements. All that being said I do like the software now and the direction it could go and I have learned to lean out my projects as they progress if there are any usused sequences and elements. This can be tough if the client is wishy washy though. The issues can come up anyway if there is a certain degree of complexity and that can be the most difficult part of things. I have lived on a number of boards and researched and there is no clear fix on this. My hope is that Adobe does not put off releasing a new version because of their foray into Mac. If they make it more efficient and burn the bridge and just merge AE and Pro then watch out, if they sit on their hands or take to much time taking on FCP on the Mac side of things then they might just become a footnote. Time will tell.
Steve -
I decided about 3 years ago to the PC Adobe route thinking that one company’s software would allow for more integration and therefore a more powerful, easier to use and more efficient toolbox. I think we’ve started to see this happen with the latest releases of PPro and AE but Adobe seems to have had this resource hungry product line and it can be quite frustrating at times. At the company I work for we are still humming and haring over mac/pc PPro/FCP. I like PPro but we do have problems with crashing/ hangin etc even on small projects. So many variables as to why when it comes to pc’s it seems.
I haven’t used any nested sequences etc but I see the memory being eaten up realtime till 1.5GB then crash. I guess it’s a case of knowing the limitations and working with them, tell me it’s not a truck so I don’t try and tow a trailer of logs, if you know what I mean.
Cheers
One Good Eye is all you need!
Reply to this Discussion! Login or Sign Up