PP “running low on system memory” can’t figure it out

[John Young]

I have also tried to open a new PP project and import the project into that. All to no avail.

Thanks for your help.

http://www.johnathanyoung.com

[Bob Dix]

John,

Had similar problem.Try typing “%temp%” in Windows address bar. Click enter, delete all temporary files from your system.

Freelance Imaging & Video
AUSTRALIA

[Andy Prada]

Ok you have quite a processor intensive, complex project here and a computer that, quite frankly, is a bit of a mess. It’s a bit like buying a mustang and hiring a cart horse to pull it to get you where you wish to go.

You have a reasonably fast PC with 12Gb RAM. Yet you operate 32bit which can only use 4Gb max. (Mmmm!) Out of that 4Gb – Windows uses a hefty chunk and Premiere simply cannot handle more than about 1.3Gb without becoming unstable. I know because I’ve tried.

You have a Quadro FX 3500 which is excellent yet it is wasted on CS3. You are trying to work HD Mp4 through external USB drives that, at best, work efficiently with DV but not much else.

I think you might be a little unrealistic here. An ugrade to CS5 will cost you $399. Vista 64bit or Windows 7 64 bit another $150. This may seem like a lot but it will seriously improve your editing capability and might earn you money by saving you valuable time.

As an adjunct: Every time Premiere loads it has to handshake with all the sequences and thumbnail all the media. 17 sequences, me lud! I rest my case.

[Bob Dix]

Hi Andy,
That 4GB max is a real problem in a 32 bit system ..

Freelance Imaging & Video
AUSTRALIA

[Bob Dix]

John,

If you have Premiere Elements 4 in a 32 bit system place the H264 mov files say 5 clips at a time probably less than 4GB, render the lot, and then Export to Movie as a Microsoft avi codec, uncompressed, and then Import into editing timeline in the other program,we were using Premiere Pro 1.5.1 the quality should be retained. A messy way but it works if you have the time.

To play safe you may need to open a new project each time and start again, the “running low on system memory” will disappear untill you exceed say 4Gb or less.

Note : I might add this has only happened since we started using the H264 Mov files from a Canon 5D mark II which are very big even for a 5 second clip, you need to work very slowly and do not add too many clips to the timeline, and save as you go or you will lose the lot.

Freelance Imaging & Video
AUSTRALIA

[Bob Dix]

John,

Do not import the whole project only small parts of it. Like us you will need to get a bigger system like us say a 64 bit designed for CS5 eventually. A bigger computer will get you round the problem to some extent, but, everything prior to CS5 is 32 bit?

Freelance Imaging & Video
AUSTRALIA

[Dexter Andrada]

The issues in your problem comes with the combination of your gear.

1. Windows Vista 32bit – (at boot up it can easily eat up 1.2gig of memory) I suspect you have to get the proper 64bit drivers to make it run as 64bit
2. MP4 footage – this is a beast in CPU usage. And if you pile up the layers with effects, etc. boom out of memory on playback. You will be able to play back MP4 better with 64bit OS, even if your using CS3

3. Shared USB connection – even if your running everything of a USB 2.0 drive, it would be better if your project files was in the internal drive, then have your scratch disks on another internal drive, then still have your footage in your USB 2.0 disks. So the access on the USB will be only when you playback your raw footages. But honestly that is not optimal. But maybe your situation forces you to work on that environment. Also i do hope you didn’t daisy chain them drives. Regarding the two clips you imported, i suggest just move it to the internal drive.

4. Tweaked System – did you properly configure your system? Just selecting it within premiere is not enough. Since your working with HD, your cache, temp folders, your scratch disks, your background services, etc. etc. should be properly setup. From placing it in the correct folder, to properly allocating virtual memory. This things matter in a limited 32bit environment.

These are the concerns on your hardware, that i hope if you had the time, you will give it the necessary adjustment.

Now on to your problem. Here are options that you can use to solve your issues.

1. Open new project, import your existing project. Then import one sequence at a time, if succesful, then save this project as PROJECT_SEQUENCE1. Then move on to making a new project. Do the same approach. If successful, save as PROJECT_SEQUENCE2. Do this for all 17sequences. This will eat up approximately 2-3 hrs.

2. Hunt for the problematic clip/s – Assuming you are able to open your project, offline all your files then manually link it file by file. Also make sure to delete your media cache and other premiere generated temp files. So when you place your newly link clip, it will conform. When successful on every stage, make sure you save in a different project everytime. Very time consuming, but it is important to hunt for the problematic clip/s

3. Your project file – the 5mb project file is relatively small. I would assume you are just starting or maybe on the first 20-30% of the edit workload. Usually once your at the end of your project the premiere project files would jump up to 20-30mb sizes. So if this is the case, your edits are still manageable to repeat. So its just a matter of asking your self what is more important given the time you have left on your hands.

Maybe you can convert everything to DV-AVI first before you continue editing, or maybe you can first solve your hardware problem. Your time left will dictate that.

4. Volume of sequences – having a 17 sequence project in premiere pro is a major major memory hog. If you really really wanna work in this manner, i suggest start first with the first chapter, save that as one project, then when completed, move on to chapter 2. And once you are at the end of your edit, you can combine all 17 projects into one project. Of course, when that happens, you will surely be hit with low system memory again. But at least you will be able to finish it per chapter.

You need take time out to first fix your issues prior to taking in more jobs. Lest you will have more of these problems. The guys above have chirped in the starting foundations for you. And besides, you don’t need to buy a new system. Just fix your existing one.

In the end if your project was all DV quality, there would be no issues on your workstation. And you can still work with your 32bit system. But in the HD world its a no go.

good luck

[Rolf Krohna]

I think you need to understand what this is really about. Dexter is absolutely right, technically, but it is a temporary solution he suggesting, looking over time. Microsoft is well known for this, and the real reason is that Microsoft is colluding with other companies, as Adobe or Intel, to force you to upgrade, and of course paying them more money. It is a sort of scam and cartel using technology as a leverage to extract money. There is absolutely no reason at all this should have to happen, if the software wasn’t written in the first place to create the problem to get more money off you when you are forced to upgrade to W7 and next generation Adobe. The long term solution is to go to another program, not Adobe, and those exist, and preferably to another operating system as Linux. Start using a better setup as a Live CD as Puppy Linux and Cinerella. You start the computer from the CD (or hard disk if you set it up that way) and the entire computer is dedicated to video editing, not with hundreds of useless not needed processes in the background. Try it, it is free.