-
CS3 suddenly running slowly; disappearing render bar to blame?
Hi,
first time posting. Allow me to say that I am almost completely computer-illiterate, so if you are kind enough to reply to this thread, please, PLEASE speak slowly, and in terms that an 8-year-old might understand.
I have PP CS3, and a relatively new Vaio NW with 4 GB of RAM and 320 GB of memory.
Last night I was editing for several hours, and everything was going swimmingly until Premiere started acting REALLY lag-gy. I closed and re-started, but nothing changed. I opened the task manager and noticed that Premiere was using over 1 GB of memory, which, I believe, is well over what is usually does. This morning I tried everything again, and now it is using over 2 GB (!) of RAM. My rendered project won’t play back w/o significant lag, even when I shrink the monitor window WAY down.
The only clue I can offer to you is that I noticed last night, when sh-t started going down, that the red/green “render bar” has disappeared altogether from my timeline (the project I’m working on is very edit-heavy and I am the type to render every minute or two; so the entire project was “green” when whatever happened happened).
Any ideas? I just ran a registry cleaner, and am currently running Defraggler, but I suspect there is a more elegant solution.
Hugs
-
3 Replies
-
Hi…
the joy of a 32bit application that happens to be a RAM hog.
Is your CS3 running the latest patch of that version.
Early versions of CS3 would lose connections to renders.Also….it is my understanding that it’s not just the clips in your project window that PPro has to keep track of (which uses RAM), but PPro also appears to keep track of iterations of renders (not just the most current one). I could be wrong about that, so others might want to chime in.
This is what, for example, allows you to undo after making a change, and having PPro show a green bar from a previous render so you don’t have to render it again. So this also may take some RAM as well. This might explain why your project became so bloated.
If the worst thing that would happen is that you’d have to render again. Might want to consider shutting down Premiere, deleting the render files from wherever your project scratch disk is set to. Then moving forward, being a bit more judicious with how much you are rendering. Not sure the length on the render is as important as the pure number (iterations) of renders.
Another thing that helps is to clear your source viewer history every so often while working. At least I’ve noticed this.
Hope that helps. Anyone else?
Alex
-
*** LOCK THIS THREAD*** if that’s the sort of thing that’s done here.
So, long story short, I am an idiot.
Short story long, apparently I had accidentally clicked a button I did not know existed, one in the top-left of the timeline which “enables or disables previews.”
So, although I got no editing done for several hours, I *did* clean the bejeesus out of my computer.
Alex, thanks for the help.
-
Reply to this Discussion! Login or Sign Up