From: "Brendan Bolles" Received: from nail.lmi.net ([66.117.140.18] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTP id 6363948 for AE-List@media-motion.tv; Wed, 29 Nov 2017 21:29:30 +0100 Received: from [192.168.1.20] (unknown [12.42.42.62]) by nail.lmi.net (Postfix) with ESMTPA id 242FAE4293 for ; Wed, 29 Nov 2017 12:32:41 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: [AE] New AE script- Rendergarden In-Reply-To: Date: Wed, 29 Nov 2017 12:32:22 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "After Effects Mail List" X-Mailer: Apple Mail (2.1085) On Nov 29, 2017, at 11:46 AM, Stephen van Vuuren wrote: > Which brings up memory management. Anyone of limiting RAM that is used = per session? Otherwise my projects will eat it all =F0=9F=98=8A Like the regular AE applications, aerender will share the Adobe pool of = memory, set up in Preferences. If you have multiple running, they do = whatever Adobe applications do to try to share it. There is the -mem_usage argument to aerender that you could experiment = with, adding it to the aerender template. In our testing, -mem_usage = had some effect on the memory used, but not much. Mainly, if aerender = was holding onto frames in the image cache for no good reason, = -mem_usage would persuade it to clear them. But if a render needs all = that memory, nothing you do to -mem_usage will make it use less. Brendan