Premiere Pro Eating Up A Lot of Memory Again

Hellmaster Inu · Post by **Hellmaster Inu** » Tue Sep 12, 2006 11:04 am

So it's been a few months since I've last made a video and I'm making one again. Everything was going just fine, but then all the sudden while I'm working on my video and I try to export what I have from Premiere Pro, my memory under the Commit Charge in Windows Task Manager keeps going up while I export my video and just a little bit before it can finish exporting, Premiere Pro ends up closing itself because there's not enough memory for it. The weird thing is, it was exporting it just fine, before I added a few .avs clips to my video timeline, so I had figured that was causing the problem and tried exporting my video again without those there, but even without them there, I'm still having the same problem where Premiere Pro is eating up too much memory. Other than that, I've made absolutely no changes to my computer that would have affected it and caused this to happen, so I'm at a loss at why this is happening. I've exported a video about five times the size of what I have right now and this hasn't happened in the past. Can someone please help me with this? I'm not sure what it is, but something on my computer has got to be causing this. I even tried scanning my computer with Norton for viruses, but nothing came up.

Hellmaster Inu · Post by **Hellmaster Inu** » Tue Sep 12, 2006 12:31 pm

And I've actually got another question regarding this. My total commit charge is 4902M and yet Premiere closes itself once it gets just above 2000M. Is there a way I can get it so that it will keep going even above 2000M? So that Premiere Pro can keep using the memory up to it's maximum?

Gepetto · Post by **Gepetto** » Wed Sep 13, 2006 11:17 am

It's quite possible that the "premiere shutting down" problem isn't related to memory. Yeah, it eats up a lot of memory but if you're only going up to half the available RAM, it's probably not it.

I suggest you split the AMV into peices and export them separately. That way, if it's a memory problem, you'll be able to export fine because you'll only use so many megabytes at a time, and if it's a problem with a specific part of the video, it'll be easier to identify which part. (Also try seeing if it stops rendering around the same number of frames).

About making Premiere use more memory, I've never actually heard of that problem, so I don't know how to help you. Perhaps increasing your virtual memory would help?

Hellmaster Inu · Post by **Hellmaster Inu** » Wed Sep 13, 2006 12:38 pm

Gepetto wrote: I suggest you split the AMV into peices and export them separately. That way, if it's a memory problem, you'll be able to export fine because you'll only use so many megabytes at a time, and if it's a problem with a specific part of the video, it'll be easier to identify which part. (Also try seeing if it stops rendering around the same number of frames).

I was going to do this even though it would be very annoying, but then I noticed that my memory starts to sky rocket even when I try to edit my video. Something is making Premiere use up more memory then it usually does and I have no idea what it is.

At this rate I won't be able to make anymore AMVs if I can't figure out how to fix this.

BasharOfTheAges · Post by **BasharOfTheAges** » Wed Sep 13, 2006 1:47 pm

Post the associated scripts from these avs files. It may be something in there.

sagarajack · Post by **sagarajack** » Wed Sep 13, 2006 4:32 pm

premiere pro is designed for professional editors, and it is linear I believe. Pros usually have good computers to handle their work. You can try some non-linear softs that is smaller and easier.

Kariudo · Post by **Kariudo** » Wed Sep 13, 2006 4:43 pm

other way around
premiere (as well as vegas, magix, ulead, WMM...pretty much every comercially avaliable software) is an NLE (non-linear editor)

premiere pro is geared twords professional applications...but it doesn't mean it won't work properly on home systems (works just fine on my laptop and desktop...specs in my org profile)

I'd have to agree with Bashar, it sounds like something in an avs script (some avs functions/plugins do take a massive ammount of memory/cpu power, putting some of these together can possibly halt any rendering when using avs scripts in premiere...it may even crash premiere)

Scintilla · Post by **Scintilla** » Wed Sep 13, 2006 6:07 pm

You can mitigate the AVS scripts' memory usage somewhat by using the SetMemoryMax option in the Premiere Pro AVISynth import plugin, or just manually putting SetMemoryMax lines at the beginning of all your scripts.

Hellmaster Inu · Post by **Hellmaster Inu** » Wed Sep 13, 2006 11:30 pm

BasharOfTheAges wrote:Post the associated scripts from these avs files. It may be something in there.

mpeg2source("C:\Documents and Settings\HP_Administrator\AMV Files\Frieza Fall of a Tyrant.d2v")
ConvertToYV12()
Telecide(order=1,guide=1)
Decimate(cycle=5,mode=2)
Crop(8,0,-8,-0)
LanczosResize(640,480)
#deen("a3d",4,10,12)
#temporalcleaner()
#mftoon(strength=128)
#Tweak(cont=1.0,sat=1.1,bright=1,hue=0)
AssumeFPS(24)

And the script for the other AVS file is exactly the same besides the file name being different.

Hellmaster Inu · Post by **Hellmaster Inu** » Thu Sep 14, 2006 4:33 am

Scintilla wrote:You can mitigate the AVS scripts' memory usage somewhat by using the SetMemoryMax option in the Premiere Pro AVISynth import plugin, or just manually putting SetMemoryMax lines at the beginning of all your scripts.

How would I go about using the SetMemoryMax option in that plugin and what exactly does the SetMemoryMax lines look like so I'll know that I'm putting the correcthing at the beginning of my scripts, since I have absolutely no knowledge of this? How will I know how much memory to set as the max?