Return-Path: <teddygage@gmail.com>
Received: from mail-yk0-f169.google.com ([209.85.160.169] verified)
  by media-motion.tv (CommuniGate Pro SMTP 4.2.10)
  with ESMTP-TLS id 5398520 for AE-List@media-motion.tv; Wed, 05 Mar 2014 19:19:00 +0100
Received: by mail-yk0-f169.google.com with SMTP id 142so3662771ykq.0
        for <AE-List@media-motion.tv>; Wed, 05 Mar 2014 10:19:30 -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=mgEg7jdgXtD7Q6yFRXiQnUAxO/MzfhvUO5HhMTW1M4Y=;
        b=W3MrLJoj54LvA9GrYoKbuZJP68QbkEo1Y5fp03cmTJ23wDxcYY/riXePoi3ZSHb+j1
         r/XlWRG5yf8fA2zrkAkr5/S1h+u+Pnc+pnhyEk9ihbwOSLJSrFYndIJTycS50xbSeUs2
         c0woai4vSk/U4MCcvg8FRCQXAK9fQEJnPMTS33q2ykozEYdNZAOqnFy9Wt/JNWgjkd+/
         Tw1fA/wxUMXGWd9D6yA0rQoL5eWC0nLu//OGFt+zL7yq6c3Qo3voERl3hx3QzR/CTDJA
         kC0Oc3AgwniY6/KjZwNFqpl9qlNZ45z/XFEdyKmAqQ1eOtCwJYgqTqD+c6aYJkZfDVut
         W7lQ==
X-Received: by 10.236.74.162 with SMTP id x22mr2895330yhd.131.1394043570695;
 Wed, 05 Mar 2014 10:19:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.170.160.6 with HTTP; Wed, 5 Mar 2014 10:18:50 -0800 (PST)
In-Reply-To: <list-5397786@media-motion.tv>
References: <list-5397786@media-motion.tv>
From: Teddy Gage <teddygage@gmail.com>
Date: Wed, 5 Mar 2014 13:18:50 -0500
Message-ID: <CAPdXPWfss0nF44yMTFOW2=bSDWGBVRyFdCyfGo+Y-785+LMf6Q@mail.gmail.com>
Subject: Re: [AE] Clocking RAM preview speed
To: After Effects Mail List <AE-List@media-motion.tv>
Content-Type: multipart/alternative; boundary=20cf30051402d537f804f3e00fbf

--20cf30051402d537f804f3e00fbf
Content-Type: text/plain; charset=ISO-8859-1

Interesting. I am going to do some tests on RAM preview vs. render vs. MP.
With a stopwatch. Are there certain effects that push RAM more than others?
HDD / SDD more than others in order to isolate performance?


On Tue, Mar 4, 2014 at 8:47 PM, Rendernyc <rendernyc@gmail.com> wrote:

> My guess is if you are running the same settings as the final render ram
> preview should be always be a little faster since it doesn't have to write
> to disk.  Now you also mention MP render. If ram preview is set to MP also
> then see above. If not then it goes back to the comp being rendered if it
> is faster or slower with MP than not
>
> On Mar 4, 2014, at 6:47 PM, Teddy Gage <teddygage@gmail.com> wrote:
>
> Is there any way one could think of automatically getting the time it
> takes to do a comp RAM preview, other than clicking a physical stopwatch?
> For example in the render queue it shows your render time, is there
> anything like that for RAM preview? recorded/logged internally? or in a
> debug window somehow?
>
> Maybe a better question is: does a RAM preview take the same time as an MP
> render? Should I take render queue time to be roughly equivalent to the RAM
> preview time at full resolution? Or is one faster than the other?
>
> --
> _____________________________
> VFX & Motion Graphic Artist
> teddygage dot com
>
>


-- 
_____________________________
VFX & Motion Graphic Artist
teddygage dot com

--20cf30051402d537f804f3e00fbf
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Interesting. I am going to do some tests on RAM preview vs=
. render vs. MP. With a stopwatch. Are there certain effects that push RAM =
more than others? HDD / SDD more than others in order to isolate performanc=
e?</div>

<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Mar 4=
, 2014 at 8:47 PM, Rendernyc <span dir=3D"ltr">&lt;<a href=3D"mailto:render=
nyc@gmail.com" target=3D"_blank">rendernyc@gmail.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">

<div dir=3D"auto"><div>My guess is if you are running the same settings as =
the final render ram preview should be always be a little faster since it d=
oesn&#39;t have to write to disk. =A0Now you also mention MP render. If ram=
 preview is set to MP also then see above. If not then it goes back to the =
comp being rendered if it is faster or slower with MP than not</div>

<div><div class=3D"h5"><div><br>On Mar 4, 2014, at 6:47 PM, Teddy Gage &lt;=
<a href=3D"mailto:teddygage@gmail.com" target=3D"_blank">teddygage@gmail.co=
m</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"lt=
r">Is there any way one could think of automatically getting the time it ta=
kes to do a comp RAM preview, other than clicking a physical stopwatch? For=
 example in the render queue it shows your render time, is there anything l=
ike that for RAM preview? recorded/logged internally? or in a debug window =
somehow?=A0<div>



<br></div><div>Maybe a better question is: does a RAM preview take the same=
 time as an MP render? Should I take render queue time to be roughly equiva=
lent to the RAM preview time at full resolution? Or is one faster than the =
other?<br>



<div><br></div>-- <br><div dir=3D"ltr"><div><font size=3D"1">______________=
_______________</font></div><div><font style color=3D"#6aa84f" size=3D"1" f=
ace=3D"georgia, serif">VFX &amp; Motion Graphic Artist<br>

teddygage dot com</font></div></div>
</div></div>
</div></blockquote></div></div></div></blockquote></div><br><br clear=3D"al=
l"><div><br></div>-- <br><div dir=3D"ltr"><div><font size=3D"1">___________=
__________________</font></div><div><font style=3D"background-color:rgb(255=
,255,255)" color=3D"#6aa84f" size=3D"1" face=3D"georgia, serif">VFX &amp; M=
otion Graphic Artist<br>

teddygage dot com</font></div></div>
</div>

--20cf30051402d537f804f3e00fbf--