Return-Path: Received: from mail-ie0-f172.google.com ([209.85.223.172] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5398537 for AE-List@media-motion.tv; Wed, 05 Mar 2014 19:35:47 +0100 Received: by mail-ie0-f172.google.com with SMTP id as1so1531456iec.3 for ; Wed, 05 Mar 2014 10:36:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:message-id:mime-version :subject:date:references:to:in-reply-to; bh=ItwB73fy9nJhSx23cokKs4ab1A0HjQu7QW6AJkR19nk=; b=leNimVz9Xwe8oXSxkjrslc7sD5AQevYdIbOKlXx4AZF/VaYmGbFgeNycFqzA2SRs1C cAw3WqHDmyxldiSPeZDesmR5fVOhyrD7gPp2MrERHCbcLfKljZRvuM9X9G+U/p3u50MS oqjoTstW7uOwp1xrFgfXMWWa8BMClNSceVFZruUDtXv/OISwViJnItbBvCotEtdXkOfm 4FhVU/z6ofxTAUfKFDUXQZm2C9xqxNkOrzmaqFaUPdNSrmxI2RzrqPM9giAHdis6eiDk u6OAf4sE9SF9h23Y+4wql4FoeHkZpikYHiebNkDJGWTSVE790q8Folre/TPzFkjqD0aU q+Dg== X-Gm-Message-State: ALoCoQmoQxu56qD0Oz2NCiZ375+WmNQi00LGOw5O0r44XbNSdTFypecM+kJVhlcpcUUg0eolB5Y4 X-Received: by 10.42.10.82 with SMTP id p18mr5863188icp.30.1394044577802; Wed, 05 Mar 2014 10:36:17 -0800 (PST) Return-Path: Received: from [192.168.1.2] (c-24-118-184-204.hsd1.mn.comcast.net. [24.118.184.204]) by mx.google.com with ESMTPSA id c17sm63136494igo.4.2014.03.05.10.36.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Mar 2014 10:36:16 -0800 (PST) From: Carey Dissmore Content-Type: multipart/alternative; boundary="Apple-Mail=_D9EEF5C4-A3BD-48AE-A4E1-05AD5396532F" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: [AE] Clocking RAM preview speed Date: Wed, 5 Mar 2014 12:36:09 -0600 References: To: After Effects Mail List In-Reply-To: X-Mailer: Apple Mail (2.1874) --Apple-Mail=_D9EEF5C4-A3BD-48AE-A4E1-05AD5396532F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Since AE currently is using the essentially the same render pipe for RAM = preview and final renders (unless you are playing with quality settings, = resolution, etc. it should be relatively the same, storage subsystem = bottleneck-factor notwithstanding.=20 The way I=92m set up, with a dedicated SSD just doing Global Performance = cache, I=92m amazed at the performance I get, and if the previews were = full rez, they dramatically improve final render times. But to your = original point, I could see a RAM preview elapsed timer being = semi-useful. Maybe even log it somewhere.=20 I tend to configure MP off for RAM previews on most of the stuff I=92m = doing (background processes spooling up delay kills me), but on for = final render. I think I was one of the loudest voices crying for that = preference setting, and so glad it=92s there! carey On Mar 5, 2014, at 12:18 PM, Teddy Gage wrote: > 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? >=20 >=20 > On Tue, Mar 4, 2014 at 8:47 PM, Rendernyc 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 >=20 > 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 = 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?=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 >=20 >=20 >=20 > --=20 > _____________________________ > VFX & Motion Graphic Artist > teddygage dot com --Apple-Mail=_D9EEF5C4-A3BD-48AE-A4E1-05AD5396532F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Since = AE currently is using the essentially the same render pipe for RAM = preview and final renders (unless you are playing with quality settings, = resolution, etc. it should be relatively the same, storage subsystem = bottleneck-factor notwithstanding. 

The way I=92m = set up, with a dedicated SSD just doing Global Performance cache, I=92m = amazed at the performance I get, and if the previews were full rez, they = dramatically improve final render times. But to your original point, I = could see a RAM preview elapsed timer being semi-useful. Maybe even log = it somewhere. 

I tend to configure MP off = for RAM previews on most of the stuff I=92m doing (background processes = spooling up delay kills me), but on for final render. I think I was one = of the loudest voices crying for that preference setting, and so glad = it=92s = there!

carey

O= n Mar 5, 2014, at 12:18 PM, Teddy Gage <teddygage@gmail.com> = wrote:

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

= --Apple-Mail=_D9EEF5C4-A3BD-48AE-A4E1-05AD5396532F--