Return-Path: Received: from omr7.networksolutionsemail.com ([205.178.146.57] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4750267 for AE-List@media-motion.tv; Mon, 18 Jun 2012 07:56:20 +0200 Received: from cm-omr6 (mail.networksolutionsemail.com [205.178.146.50]) by omr7.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q5I5xATd029109 for ; Mon, 18 Jun 2012 01:59:10 -0400 Authentication-Results: cm-omr6 smtp.user=russ@maehl.com; auth=pass (PLAIN) X-Authenticated-UID: russ@maehl.com Received: from [60.241.184.219] ([60.241.184.219:50996] helo=[10.1.1.9]) by cm-omr6 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 82/09-06495-DA3CEDF4; Mon, 18 Jun 2012 01:59:10 -0400 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1278) Subject: Re: [AE] AErender hangs at start From: aelist In-Reply-To: Date: Mon, 18 Jun 2012 15:59:08 +1000 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "After Effects Mail List" X-Mailer: Apple Mail (2.1278) The situation you describe has been my experience for years. You're right. Sometimes all the machines but one will take-off fine. = No reason as to why it has a problem. Sometimes just telling it to = start up again will do the trick, sometimes a restart of AE and = sometimes and actual reboot. Has always been a mystery, and hope someone comes up with some kind of = explanation, or at least a checklist of things you can use to debug the = problem. Russ On 18/06/2012, at 2:45 PM, Chris Zwar wrote: > Hi, >=20 > Just asking a question about something we've seen for years, and never = really thought to ask about before. > We have a Mac-based Deadline render farm, and all the slaves use the = AErender application to render - exactly the same as Lloyd's BG Render = script. It's the Adobe supplied render engine that comes with After = Effects. > Sometimes, on the individual slaves, the AErender application launches = and just hangs without beginning to actually render. We've never = figured out why this happens. It's not due to any errors such as fonts, = plugins, mounted drives etc etc. We just re-queue the render and = chances are it will begin working properly. Every so often we have to = kill all the orphaned aerender/ aerendercore processes that are sitting = there doing nothing except wasting memory. It doesn't seem to be = anything to do with Deadline itself, and we've never seen a pattern with = the projects that render normally and those that tend to stall. > Any suggestions as to what causes this? >=20 >=20 > -Chris >=20 >=20 >=20 >=20 >=20 > +---End of message---+ > To unsubscribe send any message to >=20