Return-Path: Received: from mail-qg0-f43.google.com ([209.85.192.43] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5394746 for AE-List@media-motion.tv; Sat, 01 Mar 2014 18:33:23 +0100 Received: by mail-qg0-f43.google.com with SMTP id f51so6226435qge.2 for ; Sat, 01 Mar 2014 09:33:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HKc5BSoeyjFuBi49xQOqUMqhSGGEFeeVi41SmRKAdUQ=; b=fz1E10PwThyoamtyfbvH3ivFy3LcFXth5FGEnhxq/7ea+1aM3Ek3//Ie4ekIBN3BDq LUuTANI98HaXBOszNmaC7z+dwb7UnIodDmBQ81kOBLzzI0XFeukIt7KM2X9jgQVwSpW/ 56zysIHlDmQSdelM9XBPtE0QtShOC3Q/7iFbkRBVZtFp9I8fp2hHCgKgDtbdeX7sAaIf j6rVo4/Mg2Vj9S7TUeWpwnQrOiyoPIGEbw52celZV2M8cJLwSDojj3W1OO5k4GrfrTV0 2NRUKgZCOQ4J7Aa32cEw6ybebg7KUP8VDqxTGpq3TinHMDiwylca1cbwfdjpxKmlGJ69 2aGA== MIME-Version: 1.0 X-Received: by 10.140.37.146 with SMTP id r18mr11711061qgr.61.1393695226017; Sat, 01 Mar 2014 09:33:46 -0800 (PST) Received: by 10.96.240.41 with HTTP; Sat, 1 Mar 2014 09:33:45 -0800 (PST) In-Reply-To: References: Date: Sat, 1 Mar 2014 09:33:45 -0800 Message-ID: Subject: Re: [AE] Render questions AE vs. AME in CC12 From: Todd Kopriva To: After Effects Mail List Content-Type: multipart/alternative; boundary=001a11c1628edf3dc704f38ef4a5 --001a11c1628edf3dc704f38ef4a5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable As Walter says, the headless version of After Effects that is serving AME over Dynamic Link does not use the GPU or multiple background rendering processes. I recommend the workflow that Walter suggested: rendering a losslessly encoded master file out of After Effects and directing that file to a watch folder to be picked up for transcoding to delivery formats by AME. On Saturday, March 1, 2014, Walter Soyka wrote: > AME does not exploit Ae's multiprocessing feature. This explains the > difference in render times that you are seeing. > > You cannot import an .epr into Ae. For best performance, I usually render > a lossless intermediate out of Ae (with multiprocessing on) and encode wi= th > AME via watch folders. > --=20 -------------------------------- Todd Kopriva 1510 E Alder St Seattle, WA 98122 (206)437-2296 -------------------------------- "Mobility is more important than motion." - Gy=C3=B6rgy Seb=C5=91k --001a11c1628edf3dc704f38ef4a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable As Walter says, the headless version of After Effects that is serving AME o= ver Dynamic Link does not use the GPU or multiple background rendering proc= esses. I recommend the workflow that Walter suggested: rendering a lossless= ly encoded master file out of After Effects and directing that file to a wa= tch folder to be picked up for transcoding to delivery formats=C2=A0by AME.=

On Saturday, March 1, 2014, Walter Soyka <walter@keenlive.com> wrote:

AME does not exploit Ae's multiprocessing feature. This = explains the difference in render times that you are seeing.

You cannot import an .epr into Ae. For best performance, I u= sually render a lossless intermediate out of Ae (with multiprocessing on) a= nd encode with AME via watch folders.



--
--------------------------------
Todd Kopriv= a
1510 E Alder St
Seattle, WA 98122
(206)437-2296
-------------= -------------------
"Mobility is more important than motion."<= br> =C2=A0=C2=A0 - Gy=C3=B6rgy Seb=C5=91k
--001a11c1628edf3dc704f38ef4a5--