Return-Path: Received: from mail-qc0-f173.google.com ([209.85.216.173] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5397785 for AE-List@media-motion.tv; Wed, 05 Mar 2014 02:47:00 +0100 Received: by mail-qc0-f173.google.com with SMTP id r5so439494qcx.18 for ; Tue, 04 Mar 2014 17:47:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:mime-version:subject :message-id:date:references:in-reply-to:to; bh=FCyQePg+/2apwmPAW9fSwV3sfl6PjPuSLaw3AIXQzaw=; b=O+LvcwHt19Pfu9gy+n5FxV7v/oPny+bC2prrbhYrrT5h4zJVhpwZpW/pxff1e1MSpP pZd/UmD0joQoJA5VXsx0KZgp3Pd2kgBgFaky+w0j9URlhj4t9sky0VaVBfpltpE09Zjf 4LPlmM23KlWKccbz9k/EyN5m8kC4fHVgpnPiTEV2NRrJiJ2Iu+ZOgauoCuDxPdOw9XP4 sJ1ZXnUMtdS3fLGgjbkaVPO2XPX7VdW9f9T++Xwy9N0viGgetbgwOhKK6Bc4hq6z4/JX cYXgVS80R78RGbklR+D1BkSOEDMtmfvVtl1Q+djvRgiuIGTRFxRs41aqIVytveCeAuc0 DD0A== X-Received: by 10.224.163.139 with SMTP id a11mr3541276qay.1.1393984049626; Tue, 04 Mar 2014 17:47:29 -0800 (PST) Return-Path: Received: from [192.168.1.29] (cpe-24-90-203-116.nyc.res.rr.com. [24.90.203.116]) by mx.google.com with ESMTPSA id m11sm1029417qge.13.2014.03.04.17.47.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Mar 2014 17:47:28 -0800 (PST) From: Rendernyc Content-Type: multipart/alternative; boundary=Apple-Mail-9AF212CD-4DF1-4FB3-996D-4C389791B147 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Subject: Re: [AE] Clocking RAM preview speed Message-Id: <6467852A-E831-407A-9789-72F006604D3C@gmail.com> Date: Tue, 4 Mar 2014 20:47:28 -0500 References: In-Reply-To: To: After Effects Mail List X-Mailer: iPhone Mail (11B554a) --Apple-Mail-9AF212CD-4DF1-4FB3-996D-4C389791B147 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable My guess is if you are running the same settings as the final render ram pre= view should be always be a little faster since it doesn't have to write to d= isk. Now you also mention MP render. If ram preview is set to MP also then s= ee above. If not then it goes back to the comp being rendered if it is faste= r or slower with MP than not > On Mar 4, 2014, at 6:47 PM, Teddy Gage wrote: >=20 > Is there any way one could think of automatically getting the time it take= s to do a comp RAM preview, other than clicking a physical stopwatch? For ex= ample in the render queue it shows your render time, is there anything like t= hat for RAM preview? recorded/logged internally? or in a debug window someho= w?=20 >=20 > 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? >=20 > --=20 > _____________________________ > VFX & Motion Graphic Artist > teddygage dot com --Apple-Mail-9AF212CD-4DF1-4FB3-996D-4C389791B147 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

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

--Apple-Mail-9AF212CD-4DF1-4FB3-996D-4C389791B147--