|
|||||||||
|
Thread Tools | Search this Thread |
January 19th, 2009, 12:46 AM | #1 |
Regular Crew
Join Date: Jan 2009
Location: Kathmandu, Nepal
Posts: 26
|
premeir cs3 crashed
when scrubing premeir show the notice of "premeir runnung on low systen memory"
after some moment the premeir chashed it is happening after we edit two clip i am unable to work on it . please any body can help me processor intel 4core memory : 4 gb codec: cineform software
__________________
Milan Ratna Bajracharya Editor |
January 19th, 2009, 10:29 AM | #2 |
Trustee
Join Date: Jan 2008
Location: North Conway, NH
Posts: 1,745
|
This problem is not uncommon. Is your project large with many individual clips? This takes up memory.
I have to work around the same problem sometimes and I do the following: - Keep only one timeline open at a time - Remove any assets I'm not going to use (Project>Remove Unused) - Break the project up into sections, each in its own project When all the sections are complete, I'll remove all unused assets. It's important to manually delete any unused timelines. I will then create a new project and import the projects containing each section and assemble each section timeline on a master timeline. This generally solves the problem for me. There may be other ways that I am not aware of. |
January 19th, 2009, 07:07 PM | #3 |
Trustee
Join Date: Dec 2006
Location: Central Coast - NSW, Australia
Posts: 1,606
|
Hi Trip - sounds like a good workaround - I have the same problem.
How many clips is too many? One project I'm working on has 65 clips and 6 audio clips - It just keeps falling over |
January 19th, 2009, 09:26 PM | #4 | |
Regular Crew
Join Date: Sep 2007
Location: Mount Pleasant, MI
Posts: 177
|
Quote:
I'm still on CS3 - maybe CS4 has fixed this. People have said it has better memory management. |
|
January 20th, 2009, 07:15 AM | #5 | |
Trustee
Join Date: Jan 2008
Location: North Conway, NH
Posts: 1,745
|
Quote:
Last summer, I was turning out a two hour DVD every week with about six hours of video (long clips) in the project using multi-cam editing. It would grind the system down when I got to color correcting. That was the point where I had to start breaking the project up. I knew trouble was brewing when I started getting a lag between when I pressed the spacebar and the timeline started to play. |
|
January 20th, 2009, 10:43 PM | #6 |
Major Player
Join Date: Nov 2007
Location: Corpus Christi, TX
Posts: 640
|
I had this warning when working on a 6 1/2 minute program that was pretty basic. I was trying to add the credits and it kept giving me the "running out of memory" display. I shut down CS3 and restarted. Same thing instantly. I rebooted. No joy. I finally got to add one name on the credits. Got the memory warning again. I wanted to make sure it was all saved. So I rendered the one name and for some reason, the warning went away and never returned. One of the things I had checked earlier was if there was anything left unrendered and there was nothing. It doesn't make sense to me.
|
January 21st, 2009, 06:13 AM | #7 |
Regular Crew
Join Date: Jan 2009
Location: Kathmandu, Nepal
Posts: 26
|
hi
Is there any solution to get ride off from this problme with out breaking the project, Do u guys think that it is a hardware problem, If it is a premeir cs3 problem then how we can complain it to Adobe to get the solve.
Please help me ! i am in big trouble.
__________________
Milan Ratna Bajracharya Editor |
January 21st, 2009, 06:27 AM | #8 | |
Trustee
Join Date: Jan 2008
Location: North Conway, NH
Posts: 1,745
|
Quote:
One thing that's interesting lately is that when I get the warning, I'll make my simple title and close it and continue working for hours with no additional warnings or problems. Perhaps the error is getting triggered in error. |
|
January 21st, 2009, 06:44 AM | #9 |
Trustee
Join Date: Jan 2008
Location: North Conway, NH
Posts: 1,745
|
Milan... I feel your pain. I've been there. Unfortunately, there's no quick fix for this. Your first step is to go to the Adobe support Web site and go through all the steps they recommend for configuring and optimizing your system for Premier. This includes using Windows selective startup procedures. I cannot state emphatically enough how important this is. If you contact a live Adobe support person and have not done this, they will tell you to go away and do this.
If that doesn't solve the problem, your next step is to uninstall PP then carefully go through your system and remove any software you do not need, paying special attention to any audio or video software that might install and use audio or video codecs. Conflicting codec issues can be the source of endless headaches and could cause you to pull out your hair, assuming you have any to start with. Also, make sure that you have the latest QT and Cineform releases. I'll admit that I'm not a fan of Cineform and when I trialed it last year it created new problems for me. After nearly a week of waiting, their support person informed me I needed a new release as there was a problem in the version I had downloaded only a fortnight before. I ended up in much the same place you are now when I loaded CS3 on my new machine a year ago. After a month of ceaseless problems, I blew the machine away and completely rebuilt it from the OS on up, installing only what I needed to edit, composite, etc. Upgrading the video card to an nVidea 8800 seems to have helped stability a bit overall. A year later, I'm pretty happy with the stability of the system but it was a long and bumpy road to get here. |
| ||||||
|
|