Put me down for render history too. It is an essential part of my workflow. I often re-render the same compositions as things change or get updated. I also lay out segments of a comp for discreet renders and can sometimes just re-render a segment or two. I also work in multiple languages. Once the comps are set in one language, I can reuse the same comp and render settings for the other languages as well, making a minor change to the file name and perhaps changing the destination. That saves a lot of time.

AME comes in handy for transcoding when I can just set up a batch and walk away. I find it takes what seems to me to be a long time to load the clips to be transcoded into AME, however.

Jonathan

On May 24, 2014, at 12:49 AM, D wrote:

I second this! Having the render history there can be vital. 

I never use AME for anything. On the occasions where I've tried it I've experienced longer render times and sluggish performance generally. I automatically reach for MPEG streamclip for compression or batches. I've not tried AME on CC though and my current employers are using it so I'll try it again. 

On Saturday, 24 May 2014, rendernyc <AE-List@media-motion.tv> wrote:

its nice to have the RQ history attached to the project so that you can see what was rendered. how long it took. etc.

also when opening an old project or someone elses for revisions you see what came from where and to track down the comp where you need to make your changes.

JONATHAN PENZNER

VIDEO EDITING • MOTION GRAPHICS • DESIGN

sundancerealtime@me.com