Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects Adobe CS6 Render Speed

  • Ericbowen

    June 17, 2014 at 3:24 pm

    Codecs are mathematical algorithms that process data and often compress it. The greater the compression, the more complex the algorithm. This directly correlates to the threading capability of the codecs most of the time. Mpeg based codecs especially mp4/avc have very complex algorithms to process along with partial frame data that has to be anticipated. This makes prediction much more difficult which limits threading capability. In other words the harder it is for the Player to predict data in codecs the harder it is for the application designers to multithread that processing. Then on top of this the players themselves have different levels of efficiency in threading/processing codecs/formats. For example Quicktime on OSX threads PNG great in AE. However Quicktime on Windows with AE does not. This means there are differences in the format library files. This directly correlates to the player and processing efficiency of that version.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • Micheal Bemma

    June 17, 2014 at 3:50 pm

    Finally back to the computer, still haven’t ran the avi loseless.

    For setting
    3gb ram reserved for other operations
    29gb available for AE
    2 CPU’s for other applications, 6 for AE
    ram per background 3gb each

    unchecked all the secret menu stuff, set it to 0.

    Been running it, (avi no codec) 8ish mins, it’s spending about 50% of the time
    on compressing & writing, about 30% blank, about 20% on other ones that flash too fast for me to read.
    (estimated file size is 56.2 gb).

    avi uncompressed won’t do 4k. put it back to quicktime uncomp 4:2:2 and it’s still spending about 50% on compressing and writing.

    (and since i haven’t said it yet, a big THANK YOU, to everyone, I don’t post here much ,but I read here alot. I couldn’t find an answer to this specifically. It really does help out alot having a great resource like you guys around! )

  • Walter Soyka

    June 17, 2014 at 3:54 pm

    [Micheal Bemma] “3gb ram reserved for other operations”

    I encourage you to leave more RAM available to other apps. Try 8 GB.

    [Micheal Bemma] “avi uncompressed won’t do 4k. put it back to quicktime uncomp 4:2:2 and it’s still spending about 50% on compressing and writing.”

    How about an image sequence? PSD and TIF might be good options. (You will get large file sizes, but since you’re already using uncompressed, I know you’re not afraid of that!)

    Walter Soyka
    Designer & Mad Scientist at Keen Live [link]
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    @keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]

  • Micheal Bemma

    June 17, 2014 at 4:17 pm

    i got about 200 gb free right now,
    i can free it up to the 2tb if i need.
    frame times
    1 or 2 seconds noramlly,
    average of 1
    (with quick time 4:2:2)

    (at the beginging of PNG sequence, and right now, it’s bad.
    average of 3 seconds per frame (just reread, you said PSD / TIFF)
    I’ll still run this for 5sih mins to see if it speeds up.
    CPU usage 14%, ram is 8%

    doing PSD now, about the same maybe 5% faster then quick time 4:2:2 (still average of 1 sec, but I see alot of 0 second frames)
    CPU in the area of 80% (many peaks at 100, then drops to 50%, but stays at 100 more then at 50. after effects still says ram at 8%

    Going to let this run out, then do a quicktime run, and see the total times for both.
    But I think I have the setting fixed, and now using atleast some decent codec

  • Walter Soyka

    June 17, 2014 at 4:21 pm

    [Micheal Bemma] “(at the beginging of PNG sequence, and right now, it’s bad. “

    PNG uses DEFLATE or ZIP compression on the images. It’s lossless and space-efficient, but it’s SLOW.

    [Micheal Bemma] “doing PSD now, about the same maybe 5% faster then quick time 4:2:2 (still average of 1 sec, but I see alot of 0 second frames)”

    QuickTime is generally a bit slower than other formats because 64-bit Ae has to communicate with a separate 32-bit helper process to use the 32-bit QuickTime libraries.

    With large image sequences, it’s easy to get IO-bound quickly — meaning the speed of your storage becomes the bottleneck. Balance is important in a workstation: fast CPUs with lots of RAM also want fast storage!

    Walter Soyka
    Designer & Mad Scientist at Keen Live [link]
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    @keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]

  • Micheal Bemma

    June 17, 2014 at 5:06 pm

    Next purchase might be a large SSD.
    Right now my conformed drive is my operating drive C.
    My SSD cache is D.
    And my source / output is E.

    A good size ssd for the output, can’t hurt.

    I like PNG for most things that I use. My brain just say P and sequence and filled in the rest 🙂

    I only deal in 1080p right now, but I wouldn’t mind dabbling in 4k. want to make sure i can do it (maybe not extremely well, but well enough to atleast be able to do it)

    So PSD sequence was 27:03 to render out 40 seconds, 59.94 fps, 4k, a few effects.
    nothing else difference, quicktime 4:2:2 8bit, took 22:19.

  • Ericbowen

    June 17, 2014 at 5:52 pm

    Check your ram usage with task manager. Don’t rely on AE’s reading. That does not include all of the ram AE uses. I believe that is limited to the player usage or the engine alone.

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy