When I wrote single instance, that meant only using one AeRender.exe. This just started on with CC, but I haven’t had a chance to investigate it thoroughly
yet.
[rendering a
single instance to a container file, like a .wmv or .mov]
From: After Effects Mail List [mailto:AE-List@media-motion.tv]
On Behalf Of Curtis Nichols
Sent: Monday, November 11, 2013 11:10 AM
To: After Effects Mail List
Subject: Re: [AE] aerender
(sent via the moons of Saturn)
On Mon, Nov 11, 2013 at 9:29 AM, Michael Powers <MPowers@cramer.com> wrote:
I have been using AeRender both locally and on farm mostly successfully with CC. The only problem
I have encountered is when rendering a single instance to a container file, like a .wmv or .mov. Rendering png’s and tga is working for me.
From: After Effects Mail List [mailto:AE-List@media-motion.tv]
On Behalf Of Phil Spitler
Sent: Friday, November 08, 2013 4:32 PM
To: After Effects Mail List
Subject: [AE] aerender
I am having major issues with the AE command line renderer since upgrading to CC.
Out of 10 render nodes I now have 4 that don't work.
If I simply run AErender from terminal it launches AE, loads the file then quits with a message saying successful.
But it doesn't even render a frame.
Tried with various files in various locations with zero plugins etc etc etc.
Anybody else having issues?