5 Replies Latest reply on Aug 21, 2011 6:15 AM by me_and_myself_999

    CS5 runs out of memory pre-rendering timelapse sequences

    me_and_myself_999

       

      I can see on the performance tab in Windows task manager that CS5 uses RAM at an exponential rate while importing and rendering a sequence of JPEG images for time-lapse. While editing 'normal'video clips CS5 works fine and knocks around at about 300-400 MB of RAM, but as soon I import JPEG images (usually about 300), or hit enter for a preview render RAM is eaten up until it reaches 99% and the whole system crashes.

       

       

      I know what you’re thinking, “How big are your images?” They are resized to 720x1280, each file being about 160KB in size.  That makes a typical (for me) sequence of 50MB, a fraction of my video clips and really brings home the problem – 8GB RAM to render a 50MB sequence!

       

       

      A solution already tried is importing stills as a numbered sequence. This has stopped CS5 freezing when importing, so just the render to solve now.

       

      System: Win 7 64bit, i7 2.6GHz, 8GB RAM, 3 physical hard drives for software, files and scratch respectively.

       

       

      CS5 is updated to 5.03

       

       

      Thanks

        • 1. Re: CS5 runs out of memory pre-rendering timelapse sequences
          Jim_Simon Level 8

          Have you tried an export, instead of a render?

          1 person found this helpful
          • 2. Re: CS5 runs out of memory pre-rendering timelapse sequences
            me_and_myself_999 Level 1

            Yup, I tried exporting media but the same thing happens - i.e. RAM is eaten up at a heck of a rate until it tops out and the the system freezes, that's when I ran out of ideas and posted here.

             

            This only happens with image files, there's no problem with video files (.MOV, m2ts...). By comparison I can use Pinnacle Studio 14 to create timelapse sequences using the same image files with no issues and all other software works as usual, so I'm pretty sure it's not a hardware issue.

             

            Another curiosity - if I manage to Ctrl-Alt-Del to close CS5 it remains in the processes list for quite a few seconds. Also, If I cancel the render and close the project no RAM is 'released', so CS5 sits there with no project loaded but hogging say 6GB RAM (or where ever it reached when I cancelled the render).

             

            Thanks for the quick response Jim.

            • 3. Re: CS5 runs out of memory pre-rendering timelapse sequences
              me_and_myself_999 Level 1

              An update: JPEG format causing is causing the problem

               

              Following some experimentation the issue seems to be with the JPEG file type. BMP, TIFF, GIF all import, preview and render without problems. Tellingly, if I save the sequence if stills as a TIFF but choose JPEG as the compression type Premiere returns the error message "unsupported compression...", but save as TIFF with no compression and no problem.

               

              BMP, TIFF are big files at 4-5MB each - too large?

              GIF - unsatisfactory quality.

              • 4. Re: CS5 runs out of memory pre-rendering timelapse sequences
                JAKE JONSON Level 1

                So, your sequence is composed of about 300 images?  What is the length (in time) of your sequence? What effects are you applying?

                I've heard that in most cases After Effects is used instead of PPRO for a time lapse with images from a DSLR with intervalometer, for instance.  If using AE is an option for you, it may be that AE has a better architecture for this type of thing. 

                • 5. Re: CS5 runs out of memory pre-rendering timelapse sequences
                  me_and_myself_999 Level 1

                  I'm creating movies of about 10 to 12 seconds at 25fps and applying no effects as I'm processing the images in Photoshop first. I did try AE which performed marginally better than PPro but still ultimately crashed.


                  Work-around solution:

                   

                  After some experimentation (see my update above) I've been working with stills in BMP format and everything works smoothly, and that's despite each frame being 4MB as opposed to half a megabyte.

                   

                  My PPro and AE seems to have fallen out with JPEGs - perhaps just a unique glitch/conflict on the system I'm using? Maybe future updates form Adobe and Microsoft will sort it out