Premiere CS3 - I'm out of MEMORY?

hi guys
im makin a video, all clips are 640x480 AVI (they quite big though - Canon A480), now i have created 2minutes 40 second video and my 1.5 GB RAM is gone..! premiere warns me all the time, i cant import, i cant export, i cant render.. im simply stuck.. (i tried rendering optimization set to Memory but no change there... is there anythin i can do? Or I have to buy additional RAM to finish my project? (but honestly- its got only two n half minutes, and it takes 1.5GB RAM ... how much ill need for one hour video - 45GB of RAM or what??? - isn that weird??
(procesor is Intel Pentium 4 - 2.8 GHz
any help appriciated:))
thanks
Peter

You need to read and understand your camera
http://www.camera-catalog.com/compares/popular/canon_powershot_a495_vs_canon_powershot_a48 0
That is a STILL camera with a video mode, using the MJPEG codec
MJPEG edit with Morgan or MainConcept http://www.morgan-multimedia.com/
http://www.mainconcept.com/site/prosumer-products-4/motion-jpeg-codec-785/information-797. html

Similar Messages

Premiere Pro CS5 runs out of memory

I have the same problem with Premiere running out of memory loading a project with lots of images in it. Running task manager, you can see it eat memory at 250MB per second until it pegs the meter after a short time and then things start failing. The CS4 version does not have this problem and opens the project without error.

What are the pixel x pixel dimensions of those still images? If they are overly-large, there is a very heavy load, when working with that Project. For Scaling them to fit the Sequence Frame Size, with automation in PS, see this ARTICLE.
If one's computer is already on the borderline for resources, overly-large stills can shove it over the brink. There are few reasons to use overly-large images, as one can only ever see the pixels in the Sequence's Frame Size. The only reason for using images larger than that Frame Size are to Pan on Zoomed out images, with Effect>Motion>Position.
Good luck,
Hunt

Error compiling movie: out of memory !!! Premiere CS3

Hey every1 --- desperate need of some guidance here. I've been all over the internet and these boards --- have seen this come up with a lot of people but no real solid answers that I'd seen or that have helped.
First off, my comp is an imac 3.06 Ghz Core 2 Duo, 4GB memory. (just bought the computer last year)
I'm shooting with a canon 7d in HD (1920 x 1080p) and I'm editing using Premiere CS3. I've noticed that editing has become very difficult since I started using HD; playback is very choppy and the 'quality settings' in the preview monitor are a joke and do absolutely nothing whether it's on draft or automatic.
Anyway, despite the choppiness and slow editing, I was able to get a 3 min clip completed. These are my export settings:
Export > Movie
H.264
960 x 540
23.976 fps
Square pixels,
100% quality,
recompress: unchecked.
Once exported (I was able to export smaller timelines previously--- say, 50 secs of footage or so) the files look AMAZING and from there I use them for online video via vimeo -- stuff looks really awesome.
Anyway, recently I'm getting: 'Error compiling movie. Out of Memory. Change optimization preferences to memory', etc. etc. Well, I did as it asked and that did absolutely nothing.
So, I decided to open up my activity monitor and watch what's going on with my memory while premiere is exporting. I also closed ALL unused applications. System runs at about 2.16gb free memory before I start exporting. Memory seems stable during export UNTIL around the 50% exporting mark, and then its starts climbing like crazy and my memory just gets eaten up --- finally resulting in a crash at about 70% render.
I really don't know what else to do. Does my computer not have the power to export 3 min of HD footage??? This seems surprising to me ... I don't know what else to try.
Thanks for any help !!!
-Mark

Hi Mark,
Hope you are having a wonderful day.
Sorry to hear that you are having such a hard time. Although I did not specifically get the out of memory error, I can only be convinced that that is the problem.
Although I am not a computer whiz, I have learned my share of things. I have been troubleshooting a video all this week (really, a couple of months), but I had to put it aside and come back to it.
I tend to be talkative; so I will get back on topic or at least try to stay on topic, so bare with me. Smile....
Here is what I have learned and maybe it will help you with yours if you have not found a solution already.
Based on your hard drive specs and ram, I was thinking the same thing e.g. hard to believe that you are not able to render 3 minutes of video in HD. I primarily work in HD/1080p.
The place where we are similar is that I eventually could get the video to render by reducing the workspace that is rendered piece by piece until I was able to render the entire file. When I tried to encode the video, I kept getting error compiling messages. I tried different codecs, deleting xmpses, not rendering xmpses, etc. I could not figure out the keyframe trick so I just put in a black video from after effects. By the way, all of my videos intro the same and no problems with the other videos fading from black to a still photo.
Here is the problem from what I could gather.
Simply, out of memory. I was rendering and trying to encode a 45 minute video with after effects compositions and the dynamic linking kept timing out once the file reached a certain size. There were no other true fancy effects. I do alot on the green screen and just use after effects to make a white background. Smaller videos, rendering has been slow, but doable. This massive video would never compile. I won't bore you with my system specs, but know that similar to your situation, the system in theory should have been adequate.
Work around...
I ended up exporting the video as 3 separate 15 minute video clips. I could not get them to encode as .wmv files so I encoded them as .mp4 files. By the way, I still encoded in HD.
Here is the kool stuff.
After what seems like forever, I found a converter that could convert .mp4 to .wmv and rejoin the files to play as one large file with the same quality as my source file and no audio synching issues. By the way, I do not work for this company. I just found this encoder at 4 o'clock this morning after trying all of these other converters that were straight garbage or were free to try and not really free if you wanted quality. By the way, the conversion tool is not only user friendly, but free which is awesome.
The name of the software is Media Cope. Just visit www.mediacope.com.... Be sure to send the owner an e-mail to thank him and let him know that Mark sent you. I just sent him an e-mail earlier to let him know that I was going to post on Adobe what a wonderful software he created. I just needed something free, quick, easy, and user-friendly.
Whoops... got off topic....
I'll do a summary at the end for my recommendation to you.
Here are some other tidbits that I learned as well that may save you some time.
When editing this is what I do now...
1) I use CCleaner from www.piriform.com to quickly clean my system especially temporary files before I start editing and if I am switching from project to project.
2) In all of my troubleshooting this week, I found a kool little software call Smart Close. (Just google to find this one.) It closes all of your non-critical background files in order to maximize system resources. (When I am done editing, I just reboot and all of my background programs start up again. You do not have to do it that way, that's just how I do it. The nice thing is that it is a wizard interface; so you do not have to try to figure out if a process in the background is critical or non-critical.)
3) Depending on my mood and if I did not forget, smile.... I change the priority to high for the adobe products in the task manager.
More things that I learned...
1) We are not able to change the temp file for how Adobe encodes. My logic was if I could change the encoding to a hard drive that was simply empty so Adobe can render there, then I would be good. Wrong.... Adobe does not allow you to change the temp location. (Note: This is what I discovered in the different forums; so encoding to an external hard drive is not the best move. Read more to se why.)
2) It is best to have your scratch disks as your internal disk. If you have multiple internal disks, then you shoud check some other forums for the best way to set up your scratch disks. When I was just starting out, I bought an external hard drive enclosure with the thought that I would work primarily off of those external drives with the option of doing some RAID work. Bad idea... Even the simplest of tasks took forever. It was best to work off of the internal drive. By the way, I still use the enclosure hard drives for backups in order to allow me to free up some space on the primary hard drive. When rendering, it is truely a use of the RAM and the hard drive space in the editing process.
I'll leave you with this...
I take back what I said earlier, you do need a new computer with more RAM. If you can get 16 GB, great. The primary reason is that if you are editing in Premiere and if you do anything with dynamic linking into your after effects, it will cause your ram to climb as the file gets larger. Of course, be sure to get the largest hard drive possible as an internal drive, the maximum on processor speed, 64 bit operating system, etc.
I know you are like by now, Mark, what is the point of all of your gibberish... Really, it was to share with you and others on some really kool work arounds.
My recommendation for you are as follows.
1) You have already proven that you can render and encode 50 second clips and you are very happy with those clips, so create separate smaller clips for this particular project.
2) Once you have the final clips outputted, then use Media Cope to rejoin the files as one large file and you are done.
(Note: The one thing that I did notice is that there is a small break right between where the files are merged. The nice thing is that as a video editor/film maker, you will be the only person likely to notice it because you know where the breaks are. The other nice thing is that the untrained eye will not notice it and if you had to submit your work to a television station especially on DVD, the video system should recognize the file as one large file and play all the way through. Note: For the last sentence, I said 'should play all the way through' as I have not had a chance to check this one yet as I just finished this project today and still have to turn in all of my videos. I still have some more videos to merge.)
By the way, the only specs that I will share are that I work on a PC and it has 8 GB of ram.
The summary of the summary is that sometimes an error compiling message could simply be that your system does not have resources to render and the encode that large of a file. At least that is what I learned this week or at least my specific situation. The confirmation is that I just finished shooting a documentary which was one hour and some change and was able to render and encode to .wmv with no problems. Of course, I was not using after effects for this particular project.
In either case, hope all the information helps you with your project.
Have a wonderful day and happy holidays everyone.
Mark

Error Message Premiere Pro CS3 running short of system memory; then closes

Lately Premiere CS3 is giving me the error message "running very low on system memory, save project and proceed with caution" and then it frequently closes on me unexpectedly. Hints?

If you are getting a "real" error, then the first thing that I would recommend is to study your programs and Processes in Task Manager. Look closely at the Processes tab. What is loaded and running? A screen-cap of the Processes list might help people to spot many that are totally unnecessary and can safely be removed from the boot files via MSCONFIG.
Next, when you're going to edit, Exit from ALL anti-virus, spyware blockers and pop-up blockers. Obviously, you will NOT want to be surfing the 'Net, once you do that. If you are editing, you will not be using other programs, except as required for actually editing - might be Photoshop, Encore, Illustrator, but no e-mail, messaging, iTunes, etc.. Next, use a program, like EndItAll2, to close down all unnecessary programs and Processes. It used to be freeware, but is now shareware. When installed, it surveys all running Processes and builds a database of the ones that it believes are unnecessary. It's really good at this, but you can tweak it easily, should it overlook one, or included one, that is really necessary. The reason that I Exit from things like AV and spyware detectors, is that by design, they will "lie" to programs like EndItAll2 and say that they ARE necessary. That is the way they works against Trojans, etc., that will try to close these to duck detection. There are other such programs, and many are freeware. I just use this one on every machine. Luckily, I got copies, when it was freeware, but would gladly pay for the shareware version, since it's so very good.
Now, your system is clean, lean and mean. You have rid it of some programs and Processes on a semi-permanent basis with MSCONFIG and then closed out of others. Last, on a session basis, you have eliminated many more.
One more step that can make a world of difference: check your Windows' Virtual Memory settings. Study the location of the Page File and also the management configuration. I like a static Page File, off of my C:\ and not on my media file HDD. I set to 2.5x my physical RAM. Others will locate this file elsewhere. It might take a bit of experimentation to find what is best for you.
Last, more HDD's, properly used, of adequate speed and size, will benefit you. Always defrag all HDD's on a regular basis. Much gets written to, read from, and often deleted during editing. This can fragment a HDD in a hurry. See the articles that are linked HERE. There is a wealth of info on setting up one's physical HDD's, plus other tips.
Now, you are ready to edit efficiently and smoothly, provided that you have good Assets, that PrPro likes. Still, as has been mentioned, there is a false error, and it often pops up with Titler.
Good luck,
Hunt

Encore CS3 - Out of Memory & C++ Runtime Error

I'm running Encore CS3 and I encounter several problems with a recent project that have made Encore practically useless.
When I try to preview the project, play a timeline or preview a menu I get this error. Out of Memory - Please Save and exit immediately to avoid data loss. I also get the c++ runtime error sometimes while trying the same actions.
I've also had Encore hang while trying to import .m2v files, although this appears to happen randomly. Clearing the media cache seams to fix it, sometimes.
All video was compressed with Cinemacraft Encoder 2.70.02.12 and all audio was normalized with Adobe Audition CS3.
I've read through the forms and tried deleting the media cache in the registry and re-installed Encore once. Nothing appears to work, I'm about ready to ditch Encore and go with another authoring program.
Please help.
My Specs
Windows XP X64 (Current Updates)
Dual Opteron 275
Tyan Thunder K8SE
4 GB ECC/Reg RAM (Corsair DDR400)
1x 74 GB Raptor for OS
1x 74 GB Raptor for Cache/Temp
2x 500 GB For project/storage
Quadro FX 3400
Sound Blaster Audigy
Pioneer 112D
Sony CRX320E

Why would XP64 be the problem if its worked fine for over 30 projects?
I also tried loading the project on one of our 32bit XP workstations with Encore CS3 and had all the same problems.
At this point the problem appears to be a bug with Encore, because after starting over from scratch I got the project to work fine.
It also appears that if you copy/paste anything it will corrupt your project somehow.
So, the bottom line its this, XP64 is not the problem.

Premiere Elements 7 OUT OF MEMORY - how to get more????

Hello all, I have a MAJOR problem. I know i am running on an old program - premiere elements 7. But I assume that all premiere elements versions do this. I made this video for my sister in law for her bridal shower. It's complete, but when i go to export it will not work. I have tried everything. It now says "System low on memory, please save your project and proceed with caution" All I want to do is export this so I can play this video for the bridal shower (in 2 days!!!)
I am not a computer wiz whatsoever. Can anyone out there dummy this down and help me get more memory? Or ANY suggestions just so I can export this to play this at the bridal shower?
I went to all the adobe files in my computer and deleted everything in there. That didn't help. I have plenty of space on my actual computer, but I don't know how to tell this to use that space! I think the problem is the video I am using is HD. The video is 25 minutes.
ANY HELP??
thank you!!

cmferg
Just a mention...."memory" as it relates to computer can include installed RAM (physical memory) as well as virtual memory (which is
actually an allotment of hard drive space). There are detailed articles on the subject which seem to get more complex the deeper you go into the subject.
Although most Out of Memory messages relate to installed RAM, it can also relate to hard drive space under certain extreme conditions.
And, there are instances where the particular video format has been associated with getting those low memory messages. Computer can have memory "leaks". And so on. References can be supplied if needed.
And, if you have a 32 bit computer, only 4 GB of installed RAM are supported. So, the reason for the starter question...how much RAM installed? And, if less than 4 GB, how many computer slots does your computer motherboard have to add more to bring the total installed RAM to 4 GB?
So, please supply the starter information (as requested in post 1) so that we can sort in or out factors related to your "Out Of Memory" from your Premiere Elements 7 (32 bit application) project
a. installed RAM, available RAM
b. free hard drive space
c. format and duration of video source on Timeline...you say HD and 25 minutes duration....do you know the video compression and file extension or brand/model/settings of the camera that recorded the video?
d. when are you getting this "Out of Memory" message - while you are still in the Edit area or after you hit Share/ and try to make
your export choice?. What is your intended export under Share?
We are eager for you to succeed and as quickly as possible to meet your schedule.
Again, any questions or need clarification, please do not hesitate to ask.
Thank you.
ATR

"Out of memory" while importing AVI type (AJA) file with AE CS3

With After Effects CS3 (version 8.0.2.27) when we import an AVI type (AJA) file greater than 2Gigs captured by an another PC with a Xena board AJA , a message window appears : After Effects: Out of memory.(945949kK requested) (23 :: 40). If we import the same file with After Effects CS2 (version: 7.0.1) we have no problem. If we import an AVI (AJA) file smaller than 2 Gigs with AE CS3 no problem
appears. If we capture an AVI type (Matrox) file greater than 2Gigs and import this one with AE CS3 no message appears. If we import a MOV type (AJA) file greater than 2 Gigs no problem appears with AE CS3. So to bypass this problem we are working with footage captured in MOV type file AJA. The PC which the AE CS3 is running has 4 Gigs of RAM with 2 Xeon Quad CPU.
Thanks
Marc

Most likely an issue with MediaCore trying to take over and then not getting it right... Have you checked with AJA? maybe they know something about it.
Mylenium

Cannot re-open project after Out of Memory message

Hi,
Problem with Encore CS3.
Here is my problem: I have spent about 2 weeks working on a DVD project made of 2h movie (about 100 files and 2h of subtitles) and about 20 slideshows with a few hundred pictures and music for each slideshow. There are about 15 pages of menus and submenus. All in all it was getting longer and longer to save and open but it was okay.
I eventually tried to produce the DVD in a hard drive folder. Then, after about 14h of computation I got the message "Out of memory". I had to quit at that point. Since then I cannot open the project anymore!
When I open the project I get a window telling me how long it will take to open the project (with an incredibly wrong estimate by the way), once reached the 100%, it never gives me control back anymore. I have to kill the process with the task manager. I have tried to let it work for hours but that does not change much.
The hardware configuration is the following:
At the crash time: Windows XP pro SP2, Duo core processor, 2 GB RAM, a couple of 500GB hard drives connected in USB.
I have since added 2 more GB RAM and now have 4GB with 3.4GB detected (as we all know Windows 32 cannot handle the full 4GB). I thought the add of the memory would make a difference. It does not! Encore uses up to 1.5GB of Ram while trying to open the project (the task manager tells me).
I have tried many many times to re-open my project as I spent too much time on it to give-up easily.
I actually managed to reopen the project a couple of times in a kind of degraded mode by removing some files from the "Transcodes" directory. I then get an error message and sometimes manage to get in. I managed twice amd twice immediately saved the project under a new name (over 7GB of files).
The problem is: I have got a couple of error message while trying to re-setup the project as I left it (remember it was a degraded mode with missing files). I never managed to go to the build stage again and I cannot reopen my project consistently. I now have 3 versions of it. None is working. I am back to starting point, unable to open the project.
If anyone has a solution to recover my project, it is much more than welcome! I hate the idea to start from scratch again. If I have to do so, I am seriously thinking to switch to Vegas and DVD architect because Premiere is unable to handle my new HDV files and I start to be fed-up with all the CS3 bugs. Saying that learning these 2 tools was long enough to not wish to learn 2 new ones.
Thanks for taking time to read all my message.
Thanks in advance for your answers.

Well, here is the solution to my own problem. I give it to you in case you get the same problem one day.
The solution is as simple as impossible to find on your own: launch Bridge before launching Encore! Yes, that's it. If Bridge is running when you start Encore and open your project, it all works just fine.
In my case, the project was a bit damaged as many files where not located properly. I just hit the "Skip all" button when prompted and got into my project. Then I re-assigned each unfound file (in italic) with the original one. That was quite easy in the end.
I find it incredible that Encore will work only when Bridge is launched. In that case, I can only recommend to have plenty of RAM. In all cases it is a nasty bug.
I hope it will help someone some day.
Cheers.

Large project in Premiere CS3 causes Windows XP64 to reboot

Ok...I have a rather sizeable project going in Premiere CS3. It contains a rather large number of animations created in Autodesk Maya (most between 10 seconds and 3 minutes long) and a large number of stills, as well as scrolling background (a .mov file I created using Photoshop and Premiere) and a soundtrack created by myself (in Cakewalk/Sonar). The total project is about 18 1/2 minutes in length....around 8 video tracks and 3 audio tracks at the moment. The main problem is that when I start working on it...either importing files and especially moving files around in the project or even just hitting the playback button, the system just reboots. I have seen the infamous Windows "blue screen of death" flash briefly once or twice, but it doesn't hang...just goes right to the system BIOS screen. The ONLY thing that seems to help is basically saving the project like every 30 seconds. Import a file, save, conform file to widescreen, save, bring file into project, save, move file around a bit, save, add crossfade, save....you get the idea.
Now before I go too much futher here, I suspect the problem isn't actually with Adobe/Premiere as I had this happen a few times while I was creating the sound track in Sonar 4 as well. The sound track is basically a pseudo-orchastral piece and is equally around 18 1/2 minutes long....currently with around 42 tracks of audio and 5 midi tracks. The audio has been sampled down to a standard stereo wav file for the import into Premiere. And yes, as the audio portion of this project got bigger and bigger, it caused a few reboots as well (not to mention drop-outs, studders and all the other fun stuff associated with audio production). With that, I was able to "compact" the Sonar file (basically a Sonar project defrag) and the reboot problem seems to have went away on that end.
The system itself SHOULD be able to handle this project...not top of the line, but pretty beefy. 2nd generation Intel i5 quad core, 16 gigs of Kingston DR-1600 RAM, Tascam US-428 for the audio and a good 2+ terabytes across 5 harddrives (3 internal 3 gig-per-second SATA's, 2 USB). Also has a 4 gig HIS vid card with ATI chipset (still can't afford a FirePro yet). While Premiere is installed on the (comparatively dinky) 160 gig C drive, I'm using the 500 gig E drive internal and a 500 gig USB drive as my work drives. Most of the Maya animations are on the internal E drive but the rest...the stills and Premiere files and such...are on the USB drive. I.e., the system itself should have plenty of rendering power for this. Also I have replaced the C drive with a nearly identical twin. After a recent crash, I finally broke down and got a backup C drive...in other words, I'm sure the drive(s) are a-ok...even put a brand new 500 watt power supply in just in case.
I have already re-installed XP64...a couple of times in fact, as just before I started this project one of those god-foresaken MS "critical updates" crashed the crap out of my computer. Then on the first reinstall, something hosed in .NET framework during the "night of a thousand updates" so I had to scrap it and start the reinstall all over again. Likewise, I reinstalled Premiere CS3 (along with everything else including Maya) once I finally had the computer running again.
A quick note here: I did create my own custom 1080 Hi Def widescreen settings for Premiere since CS3 didn't appear to have any such thing. For short projects they seem to work just fine...although admitedly, the render time is a serious b*tch. Likewise, all the Maya animations have been rendered out at 1080 widescreen, production quality (yea...the render time there was a killer too).
Another quick note: While I'm trying to use Premiere exclusively while I'm working, on occasion I have had to open either Photoshop or Maya to deal with a couple of stills...and when I open something else, I get a "windows virtual memory to low" (16 gigs of RAM and the virtual memory is too low??). Otherwise, except for Avira (virus scanner) I don't really have anything else running in memory...no screen savers, no desktop pictures, no Instant Messanger crap, etc.. Never cared for bells and whistles and such, so the system is pretty clean in that regard (and I do keep up on my degrags as well).
Finally, while I -am- grateful for any helpful suggestions regarding this, please do NOT simply tell me to upgrade something (Premiere, Windows, etc) as point blank; it ain't gonna happen. Aside from the fact that Adobe seems to have made Premiere CS4 and up much more difficult to use (I have -many- niggles about the newer interfaces there...using CS5.5 at the college and it's REALLY annoying) and aside from my wife being a MS programmer/developer and having to listen to her complain about Windows 7 and 8, we're in the process of buying a new house, so any and all "disposable income" is nill...and will be for quite some time. No money...zero...nadda...i.e. no upgrades. Further, while granted this is certainly the biggest project I've done to date, I've ran this setup/configuration for at least the past 3 years now without a hitch...this all seems to have started with that last MS critical update (at the risk of sounding paranoid, I'm really starting to think they slid a nasty in that last one to FORCE people to upgrade since they're discontinuing XP64 support soon).
Alrighty...I know that's a lot but I wanted to provide as many details as I could here in hopes that someone can help me get a handle on this reboot issue. Getting to be REALLY annoying having to save every 30 seconds or so. I have searched the help files, but got tired of randomly sorting thru all the blather and not finding anything helpful.
I'm grateful for any help here...thanks!
Jim

Well, I'm about 98% sure it isn't a hardware problem. I had already pulled the RAM and tried some backup RAM I have sitting in the box (8 gigs of Corsair), went thru the harddrives weeks ago with Chkdsk and everything was a-ok there (a couple of bad clusters on the old C drive, but that has since been replaced and is on the shelf as a backup), motherboard seems to be fine, re-seated all cards and cables, etc.. Again I even slapped a new 500 watt PS in just in case (the old one was a 400 watt and with all the crap I have on this system, thought it might have been a voltage drop off issue...nadda). I did have a bit of a heat problem a while back...one of the case cooling fans was going bad and the CPU was getting just hot enough to trip the system (about 5 degrees over). That said, that also shows up in the BIOS monitor as well and was easy enough to track down. Either way, the bad cooling fan has been replaced and I even added a "squirrel cage" style fan as well...system is running nice and cool now.
BTW...I used to be A+ certified on both PC's and Macs when I was a hardware tech (not to mention HP, IBM and Lexmark certified, Cat 5 installer, etc), so I like to think I know my hardware fairly well. Not just a weekend warrior on that front...used to do it for a living.
I had also already tried manually resizing the paging file as well...tried different sizes, tried spreading it out across the drives, etc.. Didn't really make a difference either way and again the only time the virtual memory low comes up is if I try to open Photoshop or Maya while this big project is open in Premiere. That said, Photoshop and Maya both tend to be pigs when it comes to memory/RAM (Photoshop especially). Doesn't seem to happen with Illustrator or any other program....just PS and Maya if this project is open in Premiere.
One other oddity I have noticed recently is actually with Maya. Before all of this started...in other words, before that last MS critical update and 3 days of reinstalling software...I used to be able to do a background render with Maya and still be able to keep working on stuff. I'd fire off batch render and then I could move on to other things...editing images in Photoshop (CS 5 there if it matters), surfing the web and even doing some light stuff in Premiere. Since this problem has been occuring however, I have noticed that the Maya batch renders are REALLY slowing down the system big time. Difficult to even check my email while a batch is running. Likewise, I have noticed that since I upgraded the Maya from 2011 to 2013, Maya has a nasty tendency to freeze during a batch render. If I have a long batch render, I'll set it up to run over night...when I get up the next moring, the render itself will still be running (you can see Mayabatch.exe still going in processes under Task Manager) but Maya is totally frozen up. Now I did that update at the same time as the rest of this mess happened so I don't know if these problems are due to the Maya upgrade or the (apparent) Windows problem...I'm inclined to believe the latter.
BTW...after having a project file get corrupted yesterday during one of these shut downs, I've been double saving the files (so as to have a backup) and that too seems to have made things a bit better. Hasn't actually shut down on me when I've been doing this. That said, it's also a serious pain in the butt having to save that way too.
With that, looking thru the rest of Hunt's article there, I did kill indexing services...at least on the work drives. it's about the only thing there that I haven't tried, so we'll see what happens this afternoon. I seriously doubt that would be the problem though as usually that would give an error or a lockup and not an instant shut down, but we'll see.

Out of Memory Error when transcoding

I am using winXP and Encore CS3. I don't have anything else open. My project is complete, but I cannot burn to DVD because I get this Out of Memory error, save and close to avoid loss. I am trying to transcode the audio track for the DVD. I've made 3 different projects. On one of the projects, I just downloaded, it did transcode. All of my menu work is in another program. Is there a way to get this one transcoded file over to the other project. Then I could be finished and burn. I don't understand why this one transcode will not work. the other music I brought in as assets for the menu and submenu transcoded fine. Sometime it will say 'transcode preset error'. I went all the way back to Premiere and changed setting there in hopes. can anyone help please

Thanks, disheartening? I'm distraught.
Everything else works, but not Encore. I tried to reinstall, but it keeps saying it cannot install until I close Bridge.
Bridge is not open.
I restarted. I uninstalled an earlier verion of Bridge.
Nothing doing.
still wants me to close Bridge.
I hate to do the whole thing over because of encore.
Help me think of a workaround!

CS3 "Running Low on System Memory" and crashing

Hi all
I'm running CS3 on my less than three year old PC with the following specs:
Intel Core 2 duo E8400 3.00 Ghz 6M 1333
3 Gigs of memory (DDR2 - two one gig chips, and two half gig chips) (max I can have on 32 bit XP, and well within Adobe's specifications)
XFX GEForce 9800GTX 512 675M DDR3 Dual Vid Card
Windows XP Professional 32 bit
C Drive: 250 GB Barracuda SATA 7200 RPM
D Drive (where I edit): 500 GB Barracuda 7200.11 SATA
The C drive is 33% free (40 GB free space)
The D drive is 40% free (188GB free space)
The scratch disks are all set for the D drive.
I actually specified this machine for running CS3 specifically. In the last few months, however, I have been having instances where it throws this error: "Adobe Premiere is running low on system memory. Please save the project and proceed with caution." I usually save then, and then if I perform a few more steps (like scrubbing through video, or moving a clip), it either freezes, or throws an error that it has met with a critical error and is going to shut down.
I don't understand why it has started to do this. The files I am using are not any larger than those I've used in the past. Some were shot with an SLR, but their file size and frame size are not and different than things I have sucessfully edited in the past.
I have had the machine to the shop, and they checked all the hardware, defragged the disks, validated that the memory is working, and that the vid card is working correctly. The also updated the bios and made sure that Windows was up to date.
Right now, my workflow goes something like: Open Premiere, edit for about six steps. Get the warning. Save. Go another couple of steps. Program crashes. Open again, do about six more steps.... around and around.
Can anyone help?
LTK

I'm using cs3, xp, pretty much same setup you have but bigger Hard drives and more room on mine...constantly defrag after doing a project etc...keep it fast as I can.... I added memory to my mobo to make 4 gig...just to eek out as much as I could out of the ram...xp doesnt see it all, but I did notice a improvement with adding the ram...
also, when I added the ram it was apparent that of the slowest memory of your ram chips is what all the ram defaults to...so if you have slow 512K chips but fast 1gig chips, all your ram will operate at the slower speed.
when I get a mssg ( only trying to edit HD , as I never have probs with SD footage at all ) --sys mem low, I save , shut off computer and restart and reopen the program.... start from scratch more or less....so all my resources are free ( for example, if I use photoshop or something else while editing there may be memory leaks with some of that ....where not all the mem is freed up for editing... to solve that as a potential cause I save, reboot and begin again....)
after a LOT OF TESTING ( and I mean a lot ! ) I have discovered I CANNOT EDIT HD MATERIAL WITH THIS MACHINE...PERIOD.
It is not powerful enough... and believe me, I tried, both 1080p and 720p ... after about 2-3 min of video on timeline at 720p at 24fps, this machine is gasping like a flounder out of water.
good luck
( bottom line ----upgrade to 64bit OS and pile on the fastest ram you can stuff onto your new mobo and get at least one more HD ( at least 1T for your project ) look at the suggestions here for raid arrays etc ) and keep them 1/4 full only if possible... the more full, the more time the heads are moving... more lost time...
mine

InDesign 2.0.2 & Out of Memory

I just want to state first I have searched everywhere and for every phrase I can think of, and while I have found a couple hits as to the cause, nothing has fixed this issue...
Background:
I work for a rather large media company who owns a mixture of online and print publications. We have been using InDesign 2.0.2 since it's release, and I have been one of the main persons responsible for it's usage in our workflow for the past 4 years. There have been a number of informal discussions, and even a formal discussion or two, about migrating the templates we use to InDesign CS3 which we also have licenses and installs for. However, that migration project keeps getting pushed aside for more important projects. So please keep in mind that upgrading, for us, is not an option in order to resolve this issue at this time.
A Quick Overview of What We Do:
There are two main products that we offer our child companies - One product for the companies themselves to list vehicles for their clients (in this product their clients are car dealerships), and another product for a private party (e.g., Joe Blow internet user) to list their cars for sell. Both applications run a fairly similar process in that they hand off data gathered from the websites to a custom built application. That application can be considered a parent application, and it then distributes work to its children processes which run on several different servers. Four of those servers run our InDesign processes.
Two of our InDesign machines are physical dedicated servers with a quad core CPU, and 2GB of RAM with 2GB swap. The other two InDesign machines are runnning as VMWare virtual machines with 2 CPU cores and 2GB of RAM with 2GB swap. All four machines are Windows Server 2003, and all files (artwork, XML files) in which these machines use to build the final output file are remotely connected via a file server.
In the past we've seen the issue I am about to describe on our virtual machines only, and on only one machine at a time. Each time we have corrected the issue by simply re-deploying that virtual machine and the InDesign application. However, now it's spread over to our physical boxes too, and currently happening on all four machines at this point in time.
The Problem and What We Have Tried:
As stated earlier, we run a parent/child setup on various servers where the parent hands off work to it's children processes whom are connected in a client/server model via a TCP connection. These children perform a single function - to process data dumped from the websites ultimately into an XML format readable by InDesign. There are other steps and XML outputs, but this is the only one that matters for this discussion.
This child then reports back to the parent that it has completed its work, and the parent will pass that work off to one of our InDesign servers. The child will then automatically launch InDesign, and InDesign will open the files it needs in order to populate various elements in the INDT file. This consists of EPS/PDF/JPEG images for Headers, Footers, Vehicle Images, etc. and also populates certain strings in the document to those read from the XML document to automate the population of the data. Basically we feed it some image files, an INDT, and an XML, and it gives us back a pretty PDF.
The problem that we're seeing is that upon opening some of our INDT files on these machines, InDesign will immediately pop up an error dialog stating that it's out of memory. Obviously, when looking at Task Manager we can see that memory is not an issue. InDesign will be using around 70mb of RAM, and the system will show 1.7GB free physical RAM.
Another problem is that it will go weeks, months, even maybe a year before happening again after re-building the machine its happening on. We have never been able to locate a root cause as to why this keeps happening. However, we have narrowed down that changes to the servers are not occurring at the time these issues start so we have ruled out configuration changes, system patches, etc.
One of the issues with the virtual machines that has seemed to have caused this, and was believed to be the issue until recently, was that the paging file would become corrupt. Thus rebuilding the VM was the only way to resolve. However, we have checked and double checked and the paging files on these servers are currently ok.
Obviously with such an old version of InDesign you can imagine that searching Google is quite difficult. Google likes to think we're asking about CS2, however, there have been a couple hits on 2.0.2.
These hits include information such as possible font corruption and deleting saved settings/defaults files. We have downloaded and used Microsoft's font validator on the fonts, and each have passed. We have also tried deleting the saved settings and defaults files numerious times, as well as deleting the font cache files so that InDesign will re-create them.
The paging files were also re-sized, turned off, moved to another local disk, etc. without any impact.
As this is the first time we've seen this impact multiple machines at the same time, and especially since its happening on both physical machines and virtual machines, we are trying to think of things which are common to these 4 servers. However, the only thing they really share are the mounted network shares. To get around this we've also tried opening our INDT's locally after copying them off the network, but the issue remains the same.
Another thing I've read is that the INDT itself may be corrupted, and to simply re-save the file. As I have a copy of InDesign locally to build these INDT's, this is also something I've tried but with no luck. The files don't seem to be corrupted. The same file which causes InDesign to crash on these four servers load perfectly fine on my local machine.
As we have escalated this to other key people here, our last suggestion was to either re-build the machines or contact Adobe for support. However, InDesign 2.0.2 is no longer a supported product due to its age so I am here - asking you, the community, for any assistance you can provide short of re-deploying these machines.
We would appreciate any assistance you can provide, and thank you for reading this.

Peter,
Thank you for the reply. In regards to...
"First, are you running InDesign Server, or trying to use a standalone ID
install as a server which is totally unsupported and probably not
allowed under the EULA? Nor is Windows Server a supported OS for
non-server versions of ID, so you're pretty much on your own as far as
what will work and what won't."
InDesign is setup, and launched, like any normal application on any other OS. We have a special user setup which runs the client process of our client/server model in the foreground, and it is that client process that then launches InDesign. This user is always logged in as a result.
"If, in fact, your templates are corrupt, in version 2.0.2 you're SOL as
far as being able to clean them up. Rebuild from scratch. The .inx
format was not introduced until version 3, and were you working in CS3
you could try Remove minor corruption by exporting but there would still be no guarantee of success."
This was one of the things I was trying to remember as I was typing. The .inx export, then re-saving as an .indt. However, as I build these templates locally, I have tried opening the file and re-saving it under a different file name. I then upload that new file and re-name back to the original name, although again, with no luck. I figure if the template is indeed corrupted that it's possible I'm just re-saving those issues even to a new file.
Re-Building from scratch is possible, however, this has happened with brand new templates as well. Again, this issue when it appears seems completely random. It chooses both new and old files alike, and those files appear to be just fine. It's just this time, for some reason, all four machines are doing it which has never happened before. Right now there are probably a few hundred templates which currently throw this error immediately upon loading (and all of the ones I've tried on my local desktop work just fine), and around the same amount that are exhibiting odd behavior with their output.
"Now on to the problem and solutions. You've already rejected the best
idea, which is to upgrade. The out of memory error might be file
corruption, or it might be realted to the use of .eps files which are
notorious for that sort of error. Reasaving in native formats is the
usual solution."
This is actually something I hadn't thought of or tried. I will re-save the EPS files as PDF's and give it ago with one, however, there are a couple things with that as well. One is that the Out of Memory error pops up on these machines as soon as I open the blank template. There are no graphics imported by default. So really it's just a plain document of whatever size, with a few boxes and text labels. Also, because we work in print and the fact these two applications have been used for so long, most of the artwork our child companies have provided us over the years are in this EPS format. There are a few thousand of them, and converting them all will take more time than it's worth for my company. They would not approve of my dedicating time to do that. New artwork we receive has been mostly in PDF as of late which does help in that regard, however.

Photoshop CS6 has out of memory errors under Mac OS X 10.7.4

Has anyone who has a 2008 MacBoo Pro with the NVIDIA GeForce 8600M GT 512 MB graphics card tried running Photoshop CS6 under Mac OS X 10.7.4?
On my MacBook Pro, PS CS6 launches; however, any action results in an out of memory error. The CS6 versions of After Effects, Premiere Pro and Illustrator all launch and run as expected under 10.7.4.
If I switch to my Mac OS X 10.6.8 startup volume, Photoshop CS6 runs as expected.
I have support cases open with Adobe, NVidia and Apple. Adobe thinks I need to update the display drivers. NVidia says display drivers must be provided by Apple. Apple says that the display drivers are current. The Apple support agent said that he can escalate the case if the issue can be reproduced on more than one computer.
I'd love to keep my MacBook Pro running another year or so without having to reboot in 10.6.8 every time I need to use Photoshop. I'd stay with 10.6.8, but of course iCloud requires 10.7.4.
I have not tried 10.8 yet, but it's on my troubleshooting list.
Also, PS CS6 runs fine under Mac OS X 10.7.4 on my 2010 iMac.
Thanks in advance for any feedback.
- Warren

It looks like it was indeed the display driver for the NVIDIA GeForce 8600 GT 512 MB graphics card inside my 2008 MacBook Pro.
It seems that this driver only gets installed if you upgrade from Mac OS X 10.6.7 to 10.7.4 while the startup drive is connected to the MacBook Pro itself. I had updated while the startup drive was connected to my 2010 iMac. Accordingly, I could have reinstalled Photoshop 100 times without it ever launching as expected. Having used the external startup drive with three other Apple computers (all 2010 or newer machines) with Photoshop CS6 launching as expected, I had just assumed (mistakenly) that it would work as expected with my 2008 computer.
So, this was simple enough to resolve by upgrading the OS on the external startup drive while having it connected to the MacBook Pro. In hindsight, this makes perfect sense.
-Warren

Converting to PDF - getting Out of Memory??

using CS3. Ive tried converting in press quality and smallest size and both give me out of memory. Have tried printing to PDF and get out of memory. Have tried dropping the INDD file into Acrobat Pro and get out of memory. Have tried printing to POstscript and get out of memory. I know I have plenty of hard drive space and ram so thats not a problem, I also convert to PDF's all the time and still can with other files but not this stubborn one. The only thing unique about this file is that its 36"x72" but its just basic text and a single not-so-great quality TIF enlarged in the background. What could be causing this?

its not really large of a file at all except for in dimensions but ive done poster sized stuff before with no probs. It never gave me any spicific errors other than just "OUt of Memory", nothing mentioned about DLL's. Out of curosity, I took off the feathering edges that I had on the background graphic and well, it worked! I have no idea why the feathering would have to do with it running out of memory but I guess Ill just have to deal with it with no feathering till I figure out otherwise

Printing error due to out of memory condition...

hi i got this problem of "printing error due to out of memory condition" and i cannot save it as a pdf file too. How to solve this prob? i using cs3 and acro 9.. pls help me... got a proj due and cannot afford to waste too much time...

I've also seen this error message for the first time today "printing error due to out of memory condition" - I have 2GB of RAM, 300Gb+ free on my hard drive and have closed all other programs that were using some memory, however have had no problems printing to pdf ever before in Indesign... is there a solution to this problem?

Premiere CS3 - I'm out of MEMORY?

Similar Messages

Maybe you are looking for