Forum Replies Created

Page 2 of 2
  • James Osbun

    November 4, 2013 at 7:47 pm in reply to: After Effects ONLY USES 1 CORE for on fly render

    Hi Ridley,

    RAM use went from 2.95GB to 5.4GB utilization during a frame render. One core was active at 100% for 40 seconds until the frame rendered. I have allotted 4GB of RAM per core, so that use is within those parameters.

    I am going to try and test your jpg theory, however I must admit I am not entirely sure how to guarantee that AE wont have to decompress the images… As Paul mentioned, would it work to simple create a .psd? I have a meeting to head to but later this afternoon I will try and report back with the result. Any additional thoughts in the meantime a VERY appreciated.

    Thanks to everyone who is pitching in on this; its really been eating at my soul to work so slowly. 😀
    -James

  • James Osbun

    November 4, 2013 at 4:17 am in reply to: After Effects ONLY USES 1 CORE for on fly render

    Hi Dave,

    Thanks. I’ve tried the same project file with the card disabled. No difference.

    I am using the CLASSIC 3D renderer, which really doesn’t utilize the card that way. Within the Raytraced 3D renderer though, that gtx580 is very powerful and renders the same frame (that takes Classic 3D 30 seconds) in less than 3 seconds.

    The problem is not related to me asking AE to use too many cores either. As I mentioned in my first post, I’ve only allotted 8 out of my 24 cores to AE and given each of those 8 PHYSICAL cores 4 GBs of RAM.

    I’m still stuck wondering why all my CPU power is going to waste within the program. Perhaps its worth mentioning that when I render (especially using the Background Renderer script) all 24 cores are utilized and frames are rendered so much faster than when I am still working in my comp.

    Anybody shed light on this??

    Thanks!

  • James Osbun

    May 25, 2013 at 8:25 am in reply to: After Effects CS6 Render Error

    Hello all.

    I am running AE CS6 on a Hackintosh and started getting this problem for no apparent reason. I had even just rendered a few minutes prior to the error.

    My edit array has over 2TB free space out of 12 total, but space was the problem.

    Just as Martin above me says, clearing the cache is necessary. I cleared out 120GB of cache, and now it renders like a charm.

    Hope this helps you.
    James

    Producer, Vice President (Monarex)
    Film with Sony F3, Canon XF300 & 5D MKii (Zeiss glass, by Duclos)
    Finish with 3 Hackintosh Edit Bays (by Cy)

  • Producer, Vice President (Monarex)
    Film with Sony F3, Canon XF300 & 5D MKii (Zeiss glass, by Duclos)
    Finish with 3 Hackintosh Edit Bays (by Cy)

  • HACKINTOSH – 4:25

    2 x 2.5 GHz 6 core Xeons
    48GB DDR3
    2 x GTX 480 1.5GB
    Lion 10.7.5

    *Primary uses are: editing, color correction, and motion graphics

Page 2 of 2

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