Return-Path: Received: from mail-qg0-f45.google.com ([209.85.192.45] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5394758 for AE-List@media-motion.tv; Sat, 01 Mar 2014 18:40:57 +0100 Received: by mail-qg0-f45.google.com with SMTP id j5so6214790qga.4 for ; Sat, 01 Mar 2014 09:41:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=q3/ZArz/1G4kYY83z7cNXVFDlESsuOhSXSRb/DXS8Lg=; b=B6v9etRVIhqgdojfqbxdyThuggvSBziTfZnXFch9ZVdyuMk+QbrCxDem7y0ePs1qZB xIJxB1Xj/Se03yPEKnyVjGjeAe0C3LXOpfEq7X3UIVQWvk7mJ9mtA2EBT5n+oe6u+siY CDKmjiejVVps+k7j8EbSkoBredGwtEEB5A9zlBNAxD/ptYyTLMifAdb5RZ8gGWDivsjn Idu2aw3t3uzKqWdySnVeqgnwTuL7uqRKu9VPzQaqWhjv7393YnjguRHmxuMz40dnefLR d24KR3m5VjcwXeWvZ24Si3KEOOao+OxIM+BZWYRFMwfN+T69wxzLY8azi/qcmTZv845t yTxg== X-Received: by 10.224.67.193 with SMTP id s1mr12191995qai.53.1393695679652; Sat, 01 Mar 2014 09:41:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.96.53.66 with HTTP; Sat, 1 Mar 2014 09:40:59 -0800 (PST) In-Reply-To: References: From: Hillary Knox Date: Sat, 1 Mar 2014 12:40:59 -0500 Message-ID: Subject: Re: [AE] Render questions AE vs. AME in CC12 To: After Effects Mail List Content-Type: multipart/alternative; boundary=001a11c32198e943bf04f38f0f39 --001a11c32198e943bf04f38f0f39 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Lots of people, including myself, are also big fans of BG Renderer: http://aescripts.com/bg-renderer/ which can be used in combination with the aforementioned AME workflow. On Sat, Mar 1, 2014 at 12:33 PM, Todd Kopriva wrote= : > 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 fi= le > 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 rende= r >> a lossless intermediate out of Ae (with multiprocessing on) and encode w= ith >> AME via watch folders. >> > > > -- > -------------------------------- > Todd Kopriva > 1510 E Alder St > Seattle, WA 98122 > (206)437-2296 > -------------------------------- > "Mobility is more important than motion." > - Gy=C3=B6rgy Seb=C5=91k > --001a11c32198e943bf04f38f0f39 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Lots of people, including myself, are also big fans of BG = Renderer:=C2=A0http://aescrip= ts.com/bg-renderer/ which can be used in combination with the aforement= ioned AME workflow.


On Sat, Mar 1= , 2014 at 12:33 PM, Todd Kopriva <toddkopriva@gmail.com>= wrote:
As Walter says, the headless version of Afte= r Effects that is serving AME over Dynamic Link does not use the GPU or mul= tiple 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 t= o 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 Kopriva
1510 E Alde= r St
Seattle, WA 98122
(206)437-2296
--------------------------------
"Mobility is more important than m= otion."
=C2=A0=C2=A0 - Gy=C3=B6rgy Seb=C5=91k

--001a11c32198e943bf04f38f0f39--