Adobe CS6 Render Speed

[Walter Soyka]

[Micheal Bemma] “disable layer cache. Purge every 10 frames.”

Mucking with stuff in the secret menu can actually slow down your render times. While this was sometimes necessary in the olden days of Ae CS4 and prior due to memory limitations, it really shouldn’t be necessary anymore.

[Micheal Bemma] “3:26 to render. Disable the mutiprocessing
it took 3:13 to render. My disk cache is on a SSD hd. Think i’m missing something.”

Multiprocessing can take a long time to start up. On shorter renders, this can make multiprocessing take longer than rendering without multiprocessing.

On longer renders, the time savings of rendering multiple frames at the same time can far outweigh the time cost of starting up multiprocessing.

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

[Ericbowen]

What codec/format are you exporting to? Is this Windows or OSX?

Eric-ADK
Tech Manager
support@adkvideoediting.com

[Micheal Bemma]

Ok, to start.
made the comp longer (40 seconds) at 40k to test with 6 processors for rendering and 2 for background (3gb to each)
so still doing the multi processing, early results
after effects shows 9% of ram being used.
windows task manager averages 14% CPU usage.
Occasional burst up to 96-100% cpu, but not for more then a few seconds.
took off the check marks in the secret menu, purge to 300.
(not sure what the defaults are supposed to be)

Out putting to quicktime : cinepak (I think it’s called)
100 quality

Be another 20 or so minutes before I can start the next render with out multiprocessors.

It’s a dedicated render machine.
So no other programs running (besides the mandatory ones) so nothing stealing any processing.

[Ericbowen]

Try AVI lossless or download Lagarith and try that under AVI. I know PNG does not thread well at all right now in AE on Windows. I wouldn’t be surprised if what your using doesn’t as well. Some codecs don’t thread as well as others. As a rule of thumb though, use AVI based codecs when possible on Windows with AE. Quicktime codecs that thread better or well include Pro Res, DNxHD, MP4, and I believe Jpeg 2000 though that encoding always takes a while. I believe Tiff and the other still based formats thread well. Tried most of them but cant remember if I tried all the others besides PNG.

Eric-ADK
Tech Manager
support@adkvideoediting.com

[Brian Charles]

[Micheal Bemma] “Out putting to quicktime : cinepak (I think it’s called) 100 quality”

I hope you mean Cineon, cinepak is one of the oldest and most lossy of all codecs.

Typical workflow would be to output an uncompressed format (e.g. Animation) and then compress using Adobe Media Encoder or similar software.

[Micheal Bemma]

It was the first codec that I tried that didn’t have a issue with 4k.
redoing it now with Mov uncompressed (it’s the format that I could need in the future).
see how this one works.
just cancelled and restarted.

Never thought the codec would matter for the processors running.

[Walter Soyka]

Re-reading this thread, I don’t quite understand your methodology. What kind of footage do you have, what are your comp settings, what exactly are you doing to the footage in the comp?

I’m just trying to understand what it is you are doing.

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

[Micheal Bemma]

It’s a animated photo, with some text effects, particular fog.
originally a 1080, I upscaled it to 4k just to make it harder on the system.
I upgrade my system from 1 quad core xeon 2.83 to 2 of em, from 10gb ram to 32, so I’m trying to find setting to make it work well.

I apply for funding for indie films, if approved, I need to be able to transfer it to XDCAM, and the company near by wants it as uncompressed MOV to do the transfer.

Normally my source footage is .mts avchd, 24,30 or 60p.
Depending on what. then various effects.

[Micheal Bemma]

Ok, on the render machine now.
Going to quicktime uncompressd 4:2:2
(i’ll try avi lossless next)
a 40 second comp, with out multiprocessing
43:42
with multiprocessing (6 out of 8 processors)
30:34

I can’t believe the difference in speed just to codec.

I wasn’t able to render out things before, i kept getting memory errors (hench the secret menu), but I don’t know the default purge frames

[Walter Soyka]

[Micheal Bemma] “with multiprocessing (6 out of 8 processors)”

What are your multiprocessing settings? Some people set them too aggressively, not leaving enough free RAM or free CPU for the system operate well. Starving your system of RAM or overscheduling the CPU can result in slower renders, not faster ones.

[Micheal Bemma] “I can’t believe the difference in speed just to codec.”

It’s possible you were spending more time actually compressing the output than you were rendering the frame.

You can get more information in the render queue about what the render is actually doing by clicking the disclosure triangle next to current render. The “Stage” line describes what is happening at any given moment. If you see a lot of time spent on “Compressing and Writing,” you know that your render is bottlenecking at output.

See this image for a reference:

[Micheal Bemma] “I wasn’t able to render out things before, i kept getting memory errors (hench the secret menu), but I don’t know the default purge frames”

The default setting is 0, which never forces a purge.

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