Skip to main content
C
Chris Dowsett
Participant
February 21, 2014
Answered

"RAM preview needs 2 or more frames to render playback" AE CC

  • February 21, 2014
  • 14 replies
  • 30974 views

This issue started out of nowhere for what I consider to be no reason. Working on average sized 720p compositions with modest animations.

I have tried all suggested solutions on this forum yet nothing has worked. I am running fresh comps in AE CC with absolutely no plugins, freshly purged memory, cleaned cache, restarted comp, no other applications running on computer and 13 gb of memory allocated to AE... etc.

I cannot seem to fix this issue.

Whats the next step?

      This topic has been closed for replies.
      Correct answer Todd_Kopriva

      jimlefevre wrote:

      I'm doing an entire Lipsyncing project. Do you have any progress on this? I used to have it way back in the old days but not for ages and now having gone up to CC and then to CC2014 I'm stymied and I've got a serious deadline on Monday.  I can't restart every few minutes.

      Then I would suggest you use CC for the part where you're lip syncing then only open your project in CC 2014 when you need to use some of the new features. And, since you've already done a lot of work in CC 2014, you will be happy to know that CC 2014 can save back to version CC. (Also, if you've uninstalled CC, you can reinstall it from the cloud software, see here: Creative Cloud Help | Install, update, or uninstall apps.)


      Note that the memory leak with audio scrubbing is listed as fixed in the upcoming update:

      http://adobe.ly/1pFGGRE

      14 replies

      luiss76110615
      luiss76110615
      Participating Frequently
      February 21, 2015

      Guys, I think I got it, I looked in a forum on Apple to see if there was a way to fix the memory leaks on Mac Os X 10.10.02, and there is, it takes 5 minutes but it works, for the first time in 3 days I've been able to preview one of my projects, please take a look:

      Guide: How to solve Yosemite memory leaks and C... | Apple Support Communities

      the_dudes
      the_dudes
      Inspiring
      March 19, 2015

      This is still off topic and I suggest you open a new thread.

      luiss76110615
      luiss76110615
      Participating Frequently
      February 20, 2015

      iMac 2013 / Yosemite OS X 16Gig RAM here

      The problem started out of nowhere this week, it's been 3 days, I've uninstalled and reinstalled CS6, installed CC2014 using my office license, reset all caches, disabled and enabled quad processing, used the secret settings to purge every 30 frames, changed the memory allocation, I honestly don't know what else to do, but it's alarming that Adobe has no idea where this is coming from and how to fix it, meanwhile my clients are starting to get mad. Upgrades? Success is about stability, not about bells and whistles, that's basic.

        M
        martinc13962311
        Known Participant
        December 16, 2014

        Sorry you are not getting anywhere dude, we have lost patience also.

        We are currently running tests in Yosemite using Nuke as an alternative to AE. The performance and playback is so advanced, stability has been great too. Yosemite isn't even supported in Nuke! Trouble is we have spent so much money on our AE pipeline it will be a wrench! I will let you know how it goes.

        stridermax22
        stridermax22
        Participating Frequently
        December 16, 2014

        I like nuke, but its just so much of a difference in workflow from AE its not worth it to me

        So just got off chatting with the worst, and un experienced Tech i have gotten so far. Time to call and throw a fit because apparently thats the only thing that gets results

        stridermax22
        stridermax22
        Participating Frequently
        December 14, 2014

        I have After Effects 13.1.3 and I'm using a 2011 mac pro 17" with 16GB of ram, but I have any project I have I'm not able to work on due to After Effects not being able to render more then one frame at a time. When I go to RAM Preview it says "After Effects Error: RAM Preview needs 2 or more frames to playback." This phenomenon used to happen whenever I had Adobe Premiere open at the same time, but Thats not the case anymore. It just happens all the time. I can open a project, but after a little less then 3 minutes it reverts back to only rendering one frame. Purging the memory does absolutely nothing, in fact purging anything makes the problem come up immediately.

        This is frustrating! I have deadlines to meet. Not to mention having to pay out of pocket for software that hasn't worked well since Mac OS X 10.8. I shouldn't have to pay for defective software.

          M
          martinc13962311
          Known Participant
          December 14, 2014

          I feel your pain as many do... Wouldn't say too much on here though. Not really what Adobe want to hear!

          Try manually deleting your cache folders e.t.c. Look in prefs and see where you have them saving to, delete all the folders. Also use memory freer, it seems to be a work around until they can be bothered to address the issue. 32gb upgrade might also help longer term.

          I totally agree on paying for software that doesn't work, pretty scandalous but you will be banging your head against a brick wall trying to get them to listen. They just write you off as being negative! They don't want to actually hear about the chaos these constant broken upgrades cause. If you want to have a laugh ring the support line and waste a day or two of your life.

          Hope these fixes can get you working again, patched us up for now.

            stridermax22
            stridermax22
            Participating Frequently
            December 15, 2014

            "Try manually deleting your cache folders e.t.c. Look in prefs and see where you have them saving to" - Would that be in Media And Disk Cache area?


            So I have memory freer and It doesn't seem to help. I also have Tried to work in After Effects 12 and same problem. I only can assume its because of me updating Mavericks OS X 10.9 to Yosemite OSX10.10. I have a feeling that Yosemite is to be blames, but apple and adobe sure don't have time to look into such a "small" problem. Both companies just keep saying, "well it should work, so you appear to be good" I don't play to contact or call either companies because I have little to zero faith that they can actually help me, but by all means I'm willing for them to prove me wrong.

            M
            M9_MHM
            Known Participant
            October 29, 2014

            I can also report that this bug is still randomly occurring for me, on OS X 10.9.5 running AE CC 2014.1.1

            I was motivated to post this report, because I literally saw this bug happen for absolutely no reason on the comp I am currently working on. I was RAM previewing one second, and after making a single parameter change to a position keyframe, when I tried to RAM preview again, I got the "2 frame warning error of death (aka "TFWEOD"). Nothing fixed it: not a complete Disk/RAM cache purge, restarting AE, tuning off audio in the Preview pallete, etc.

            So no, contrary to what Adobe is claiming, this problem is NOT fixed in 2014.1.1

            Szalam
            Community Expert
            SzalamCommunity Expert
            Community Expert
            October 29, 2014

            M9_MHM wrote:

            So no, contrary to what Adobe is claiming, this problem is NOT fixed in 2014.1.1

            Adobe is not claiming that this error will never show up. All Adobe has claimed is that the particular bug that caused a memory leak when scrubbing audio is fixed (and it is). Your issue is completely different and may indicate a memory leak somewhere else.

            In order to track down the cause of the issue (since it seems to happen randomly and only to a few people), Adobe is going to need a lot more information from you. If you could try to recreate the conditions where it occurred and find the exact steps to follow and the right combination of effects, plugins, etc., it would be greatly helpful when you file your bug report: Adobe - Feature Request/Bug Report Form

            M
            M9_MHM
            Known Participant
            November 25, 2014

            Szalam wrote:

            M9_MHM wrote:

            So no, contrary to what Adobe is claiming, this problem is NOT fixed in 2014.1.1

            Adobe is not claiming that this error will never show up. All Adobe has claimed is that the particular bug that caused a memory leak when scrubbing audio is fixed (and it is). Your issue is completely different and may indicate a memory leak somewhere else.

            In order to track down the cause of the issue (since it seems to happen randomly and only to a few people), Adobe is going to need a lot more information from you. If you could try to recreate the conditions where it occurred and find the exact steps to follow and the right combination of effects, plugins, etc., it would be greatly helpful when you file your bug report: Adobe - Feature Request/Bug Report Form

            Of course, I agree with you on a semantic level. But I was responding to the greater "issue" itself, regardless of what may be causing it.

            That said, I have since discovered that a temporary "fix" for this issue on Mac OS X (10.9.5, in my case), is to manually purge the OS X system disk cache, by issuing the following command in the Terminal:

            sudo purge

            This will temporarily work to get your RAM Previews working again, but you will need to keep re-running the command every so often (even in the same AE launch session) because eventually, the 2-frames error will pop up again

            J
            Josh JMFE
            Inspiring
            October 16, 2014

            My memory leak is gone after the newest AE update to 13.1.1.3.   So if anyone's issue was related to audio scrubbing, that should do it.

            A
            almosdone20112
            Participant
            October 9, 2014

            I just updated my CC 2014 and the bug has been fixed.  Been working on a project for the past 3 hours and no error as of now.

            http://adobe.ly/1pFGGRE

            If you have any previous versions, like AE 6 or 5.5, the problem may still occur. I am referencing only AE CC 2014 that the bug has been fixed and you should update

            L
            Leroy Filon
            Participating Frequently
            October 10, 2014

            Thanks for the heads up! Will update and check it out

            N
            Navarro Parker
            Inspiring
            October 3, 2014

            Yup same problem here!

            M
            misfit_edit
            Inspiring
            September 16, 2014

            I'm having this same issue, but it is NOT related to audio scrubbing. I have no audio in my comb at all and still get the error after about 20 minutes of working.

            J
            Josh JMFE
            Inspiring
            September 11, 2014

            You can add me to the list.  AE CC 2014, hits around 21 GB of Ram, then I get the "2 frames" error and can't purge.  And yes, it definitely seems connected to audio scrubbing.  Sure, restarting takes 10 seconds, but its QUITE the annoying bug.

            Show more replies
            Terms & ConditionsAccessibility statement
            Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices