8 Replies Latest reply on Jul 27, 2012 5:02 PM by The Noble Robot

    AE CS6 renders 7-68 frames out of 889, but gives the "ding" and claims it's done!

    The Noble Robot Level 1

      So, I set up my first render with CS6. Nothing too complicated, 889 frames long. I hit "Render" and it starts.

       

      About 30 seconds later, I hear the "ding," and am surprised to see that according to the program, the render has finished successfully. "Wow," I think, "CS6 sure is fast. A little *too* fast..."

       

      And sure enough, the render only exported 13 frames! Umm, odd. I check my settings and yes, I've set it to export the entire comp (the Work Area spans the entire comp anyway).

       

      Okay, strange fluke. Try again.

       

      7 frames. "Ding!"

       

      Ugh, try again...

       

      15 frames. "Ding!"

       

      And so on... 68 frames. 35 frames. 9 frames. 37 frames.

       

      What the hell, man! Why does AE think it's done the render successfully, instead of throwing an error? This is completely unacceptable. Obviously I'm not doing anything wrong here, otherwise the number of frames would be consistant.

       

      When I import the partial renders back into the comp, lay them on top, and export again (to avoid re-rendering those frames), I can get a longer export. So clearly the problem ony comes when there's real work to be done by the renderer, but it never renders more than 70 unique frames each time, and usually I get far fewer, 15 on average.

       

      This is just stupid, I can't live like this. There's no logic to this problem, which pissed me off so much that I punched a door.

       

      I've had nothing put headaches with AE CS6 (the new 3D renderer won't initialize with my CUDA GPU, and refuses to fallback to CPU; Dynamic Linking is slower than CS4, etc.), but I've been able to put off troubleshooting these problems so far, and I wasn't worried because there's always an answer out there somewhere, but this is a frickin' showstopper.

       

      Please help!

        • 1. Re: AE CS6 renders 7-68 frames out of 889, but gives the "ding" and claims it's done!
          The Noble Robot Level 1

          Well, I've been able to work around it by disabling multiprocessing (well, so far, the render isn't finished yet, but it's gotten past 150 frames without being "done"). Very disappointing solution. I have a 8 cores across 2 Xeon processors (Win7-x64), and according to quick napkin math, it looks like I'm taking a 35% performance hit just to be able to render properly.

           

          I suppose there is probably something I can do to solve this, but the manifestation of the error is what is most frstrating to me. Under what circumstance would AE be fooled into thinking that it is finished with a render but isn't? Doesn't it know about which number is bigger than the other number?

           

          Just because my 8 cores are each working on a separate frame using a bunch of headless render engines doesn't mean that the main program should lose track of how many frames are rendered!

          • 2. Re: AE CS6 renders 7-68 frames out of 889, but gives the "ding" and claims it's done!
            Szalam Adobe Community Professional & MVP

            If you genuinely want help rather than just virtually punching a door, try sharing some of your system specs, your AE memory and multiprocessing settings, what type of footage you've got in the comp (format AND codec), what your render settings are, what effects you have applied, what troubleshooting steps you've taken etc.

             

            Try it on a different comp and see what happens.

            • 3. Re: AE CS6 renders 7-68 frames out of 889, but gives the "ding" and claims it's done!
              The Noble Robot Level 1

              Like I said, there is probably a solution, but my point for now is just to see if anyone knows anything about this insane non-error. When I have more time, I'll post details about my comp.

              • 4. Re: AE CS6 renders 7-68 frames out of 889, but gives the "ding" and claims it's done!
                Mylenium Most Valuable Participant

                Like I said, there is probably a solution, but my point for now is just to see if anyone knows anything about this insane non-error. When I have more time, I'll post details about my comp.

                 

                How should we? That's circular reasoning based on a lot of wrong assumptions.

                 

                1. You wrongly assume that a lot of people or everyone gets those errors.
                2. You again assume it has no relation to your settings.
                3. You also assume it has nothing to do with your system because everything works perfect in a previous version.

                 

                Now granted, CS6 is thouroughly effed up and the worst version ever since AE 6.0 as far as bugs and issues go (but then again, there is a magic number symmetry here), but really, just running off on a forum and venting isn't helping the matter in any way, either.

                 

                Mylenium

                • 5. Re: AE CS6 renders 7-68 frames out of 889, but gives the "ding" and claims it's done!
                  The Noble Robot Level 1

                  Great, let's make this about me and how I'm broken. That will help.

                   

                  I'm not assuming anything, and I don't disagree with you. I know more info is better, and I trust (blindly) that the problem is likely to be solved with some tweaking on my end (I said it like 3 times already). As I said, I just wanted to see if anyone else had this issue, or an had any insight for scenarios where AE might report "done" before all the frames have been rendered before I got deep into it describing every single layer, effect, and settings used in all of my nested comps.

                   

                  Sheesh.

                  • 6. Re: AE CS6 renders 7-68 frames out of 889, but gives the "ding" and claims it's done!
                    Rick Gerard Adobe Community Professional & MVP

                    I have never seen this issue.  What format are you using in the output module? CS 6 has been very good to me for a long time and I've been using it longer than the public if you know what I mean...

                     

                    The biggest rendering problems I have seen are related to specific codecs. 

                    • 7. Re: AE CS6 renders 7-68 frames out of 889, but gives the "ding" and claims it's done!
                      The Noble Robot Level 1

                      I'm using the default "Lossless" (AVI) settings in the output module, sometimes "Lossless with Alpha" or similar setting. I almost exclusively use uncopressed renders for all my AE projects, as I prefer to use AME or PrPro when rendering out to compressed codecs.

                       

                      I've been working with multiprocessing disabled for awhile, so I haven't had to deal with this problem. But I have a moment to breathe between jobs now so I can more fully describe my setup, and run some tests.

                       

                      Most (but not all) of my projects have been largely made up of RED footage (r3d files from the original RED ONE as well as Scarlet/Epic), both 1080p and 4K. But I also frequently work with DSLR footage in the dreaded h.264 format (both mpg and mov). Performance within the program itself (including previews) seems quite good, regardless of which codec my layers are made up of.

                       

                      For effects and such: some projects have nothing but text layers and masks, while others have extensive keying, color correction, and animation. And some use the 3D ray-tracer and are made up of nothing but shape layers and color mattes, having no video footage at all.

                       

                      Since I last moaned about this issue, I have re-installed the CUDA toolkit (instead of just the graphics driver), and now the ray-tracer is working better, and Dynamic Link performance is better, but unfortunately, the problem described in the original post remains...

                       

                      When I have Multiprocessing enabled, any render of a comp with more than one layer seems to exhibit this problem. After trashing my preferences, I have been able get a succesful render or two with multiprocessing enabled, if the project is not too complex, but soon after the problem returns for all projects (it's hard to be precise about exactly when, and what project, triggers its return). I have no idea if trashing my prefs has anything to do with granting a momentary fix, or if it's just a coincidence. When multiprocessing is disabled, I generally have no problems of any kind when rendering (other than it being much slower, as expected).

                       

                      My system:

                       

                      OS: Win7 x64 SP1

                      CPU: Xeon E5504 (x2) @ 2.0 Ghz (8 logical cores total)

                      GPU: Quadro FX 3800

                      RAM: 24 GB

                       

                      Multiprocessing settings:

                      RAM for other programs: 6GB

                      RAM per process/core: 2GB

                      Processors reserved for other programs: 0

                      Actual background processors used: 7 (this drops when I have PrPro or AME open reserving its own RAM, obviously)

                       

                      NVIDIA driver: 301.32

                      CUDA version: 4.2

                       

                      I can't seem to identify anything unusual about my setup or configuration, and my Multiprocessing settings use recommended guidelines from the AE team (which have proved optimal in the past).

                       

                      Is there any other information about my setup that would be useful?

                      • 8. Re: AE CS6 renders 7-68 frames out of 889, but gives the "ding" and claims it's done!
                        The Noble Robot Level 1

                        Now it's happening when I'm just trying to render a single video layer from r3d to lossless avi (to bring back into AE to for Mocha tracking, since Mocha doesn't read r3d files). My comp is just a single video layer, 71 frames, no audio.

                         

                        Render... 14 frames. Ding!

                        Try again... 63 frames. Ding!

                        Try again... 1 frame. Ding!

                         

                        Ugh... *sadface*