Premiere Pro Is Eating Up Too Much Memory

The old Video Software Help forum, left visible as an archive.

Premiere Pro Is Eating Up Too Much Memory

Postby Hellmaster Inu » Thu Jun 29, 2006 11:13 pm

I'm having the same problem I did before with Premiere Pro except now on my new computer. :roll: When I go to render my project, under Windows Task Manager the Commit Charge keeps increasing rapidly and once it gets up to about 2000/4801 (which is usually around when it's almost done rendering my project), the program keeps closing itself. I went under my Control Panel and went under my System Properties and changed the initial size of my virtual memory to 2973 MBs out of the maximum size of 4092 MBs, which is the recommended size. This doesn't seem to have fixed my problem. I also tried doing a System Restore to yesterday (which is was rendering my video just fine yesterday and before then) and it didn't fix it. Anyone got any ideas how to fix this?

I'm also wondering why this started happening. I haven't installed anything today and it was working just fine earlier today. I don't see what could be causing this to happen besides the fact that I made three avs scripts using Huffyuv avi files because I had to crop three clips in my video. Why would this be causing the problem if it is?

Ok, actually while I was typing this, I'd figure I'd try to see if this was causing the problem. It looks like it is, since I rendered my video without those clips and while my commit charge did go up to about 1900/4801, it was able to render my project just fine. What can I do to fix this problem, because I can't really go without cropping those few clips? I want my next video to be as good as I can get it for once.
User avatar
Hellmaster Inu
 
Joined: 16 Feb 2004
Location: Bryans Road, Maryland

Postby Kariudo » Thu Jun 29, 2006 11:40 pm

how much phsyical ram do you have?
in my experience, virtual memory doesn't really help at all (the latency is really high for virtual, since it uses part of your hard drive)

You may want to go into msconfig (start, run, msconfig) and turn off unnescesary services and programs that start up when your computer boots (like music services, IM services, video players, etc)
this could free up some more memory while running windows

What are your project settings in premiere?
EADFAG suggests using video for windows, and for the preveiw, not using a codec like huffy

you can always crop after you're done with the video in vdub.

Although imprting avs scripts can come in handy, the editing process slows down when doing this.
It takes a lot of system resources to run an avs script through vdub (depending on what plugins/functions you use), and premiere naturally takes a lot of memory, so that might be your problem.

you could run those clips through vdub and get the avi files and import them into premiere (should eliminate the problem) but don't forget to use lanczosResise() [or the vdub resize] to make all your clips uniform in display size
ImageImage
Image
User avatar
Kariudo
Twilight prince
 
Joined: 15 Jul 2005
Location: Los taquitos unidos
Status: 1924 bots banned and counting!

Postby Hellmaster Inu » Fri Jun 30, 2006 12:31 am

Kariudo wrote:how much phsyical ram do you have?
in my experience, virtual memory doesn't really help at all (the latency is really high for virtual, since it uses part of your hard drive)

You may want to go into msconfig (start, run, msconfig) and turn off unnescesary services and programs that start up when your computer boots (like music services, IM services, video players, etc)
this could free up some more memory while running windows

What are your project settings in premiere?
EADFAG suggests using video for windows, and for the preveiw, not using a codec like huffy

you can always crop after you're done with the video in vdub.

Although imprting avs scripts can come in handy, the editing process slows down when doing this.
It takes a lot of system resources to run an avs script through vdub (depending on what plugins/functions you use), and premiere naturally takes a lot of memory, so that might be your problem.

you could run those clips through vdub and get the avi files and import them into premiere (should eliminate the problem) but don't forget to use lanczosResise() [or the vdub resize] to make all your clips uniform in display size


Thanks. Actually I was able to render my project just fine this time, though my commit charge went up to about 1900 before it finished rendering. I just edited the original AVS script and cropped out just a bit more off the top. I'll see what I can do with msconfig and disabling some stuff that I don't need.
User avatar
Hellmaster Inu
 
Joined: 16 Feb 2004
Location: Bryans Road, Maryland

Postby Hellmaster Inu » Fri Jun 30, 2006 12:34 am

Oh I almost forgot sorry. Looking under System Properties I have 1.93 GBs of RAM. In Premiere I'm using video for windows and for preview I'm using the PICVideo M-JPEG 3 VfW Codec.
User avatar
Hellmaster Inu
 
Joined: 16 Feb 2004
Location: Bryans Road, Maryland

Postby Kariudo » Fri Jun 30, 2006 1:28 am

hmm...well I can render on my laptop with 1gig of ram (using huffy I think)
perhaps it's just throwing too much information, and the ram can't handle it fast enough, so you get a "program not responding" message.

couldn't really say...if your video has lots of effects, it could slow down/halt rendering

hope your problem goes away (or someone else comes who can assist you better)
ImageImage
Image
User avatar
Kariudo
Twilight prince
 
Joined: 15 Jul 2005
Location: Los taquitos unidos
Status: 1924 bots banned and counting!


Return to Video Software Help Archive

Who is online

Users browsing this forum: No registered users and 1 guest