Return-Path: Received: from oproxy13-pub.unifiedlayer.com ([69.89.16.30] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with SMTP id 5037947 for AE-List@media-motion.tv; Sun, 14 Apr 2013 05:41:07 +0200 Received: (qmail 547 invoked by uid 0); 14 Apr 2013 03:49:06 -0000 Received: from unknown (HELO box473.bluehost.com) (74.220.219.73) by oproxy13.unifiedlayer.com with SMTP; 14 Apr 2013 03:49:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=helium14.com; s=default; h=Mime-Version:Content-Transfer-Encoding:To:Date:Message-Id:In-Reply-To:Content-Type:From:References:Subject; bh=cJl3iIrM1b2FVfIHyDxtM4IeMEwoDf4PMvYPYhr7IKE=; b=WqeJmUHVweOULz/Viiso/kMLKxgsg1Yljr1153DXfkxerq4Txs2eTb66LsnyeyR2JnxCjkZ6UFJszig8K8Is21kMbr7H/jsxWVwKZMOBgDnxoO/gCc0gVaStFg2RhKre; Received: from [166.137.216.202] (port=60164 helo=[10.142.215.139]) by box473.bluehost.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80) (envelope-from ) id 1URDw3-0007r8-OQ for AE-List@media-motion.tv; Sat, 13 Apr 2013 21:49:06 -0600 Subject: Re: [AE] a tip about Caps Lock References: From: Eric James Wood Content-Type: multipart/alternative; boundary=Apple-Mail-C3FED47E-5ED4-423E-85D9-EBD8EC522CD0 X-Mailer: iPhone Mail (10B329) In-Reply-To: Message-Id: <86ED94C8-E8E9-4614-9E26-25298D95E6BD@helium14.com> Date: Sat, 13 Apr 2013 20:47:42 -0700 To: After Effects Mail List Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) X-Identified-User: {1790:box473.bluehost.com:heliumon:helium14.com} {sentby:smtp auth 166.137.216.202 authed with list@helium14.com} --Apple-Mail-C3FED47E-5ED4-423E-85D9-EBD8EC522CD0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Chris, well background rendering is slower than rendering in app. I use it a= ll the time, but it is slower.=20 No multi proc rendering in the background.=20 It is quite measurable difference rendering lock on or hiding the window. Ea= sy to check, render a comp both ways and clear the cache before each. Tell u= s what happens.=20 Sent from my iPhone On Apr 13, 2013, at 20:28, Chris Zwar wrote: > I've never understood the obsession with rendering with caps-lock on. Bac= k in the 3.1 days, when we were working on machines where the speed was meas= ured in megahertz and memory in megabytes - yes. It made a small difference= to render with caps lock on and save the machine the time needed to draw th= e output. And also because we were using crappier operating systems that di= dn't multitask properly, once you hit the 'render' button there wasn't much e= lse to do but wait. Caps lock back in those days made a small but measurabl= e difference. But that was about 10 years ago, or more. >=20 > These days we have multi processor computers, multi-threaded applications,= running at gigahertz with gigabytes of RAM and usually with loads of applic= ations open at the same time. You no longer sit around doing nothing while w= aiting for renders. If you're not rendering in the background (and you shou= ld be) then you probably have your browser opening checking Facebook or some= thing. That's going to make a bigger difference than caps lock. >=20 > Caps lock=E2=80=A6 I just don't get it. >=20 > -Chris >=20 > On 14/04/2013, at 1:01 PM, Michael Malone wrote: >=20 >>=20 >>=20 >>=20 >> On Apr 12, 2013, at 3:38 pm, Todd Kopriva wrote: >>=20 >>> Here's something I just tweeted: >>>=20 >>> "to all who use CAPS LOCK when rendering in After Effects: Don't. Dock R= ender Queue panel over Composition panel. Same result; less shouting." >>>=20 >>> I'm going to try to get this change made in our Standard workspace, too.= >>> +---End of message---+ >>> To unsubscribe send any message to >=20 --Apple-Mail-C3FED47E-5ED4-423E-85D9-EBD8EC522CD0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Chris, well background rendering is sl= ower than rendering in app. I use it all the time, but it is slower. 

No multi proc rendering in the background. 

It is quite measurable difference rendering lock on or= hiding the window. Easy to check, render a comp both ways and clear the cac= he before each. Tell us what happens. 

Sent from my iPhone
=

On Apr 13, 2013, at 20:28, Chris Zwar <chris@chriszwar.com> wrote:

I've never understood the obsession with rendering with c= aps-lock on.  Back in the 3.1 days, when we were working on machines wh= ere the speed was measured in megahertz and memory in megabytes - yes.  = ;It made a small difference to render with caps lock on and save the machine= the time needed to draw the output.  And also because we were using cr= appier operating systems that didn't multitask properly, once you hit the 'r= ender' button there wasn't much else to do but wait.  Caps lock back in= those days made a small but measurable difference.  But that was about= 10 years ago, or more.

These days we have multi processo= r computers, multi-threaded applications, running at gigahertz with gigabyte= s of RAM and usually with loads of applications open at the same time.  = ;You no longer sit around doing nothing while waiting for renders.  If y= ou're not rendering in the background (and you should be) then you probably h= ave your browser opening checking Facebook or something.  That's going t= o make a bigger difference than caps lock.

Caps loc= k=E2=80=A6 I just don't get it.

-Chris

On 14/04/2013, at 1:01 PM, Michael Malone <mmalone@mac.com> wrote:




On Apr 12, 2013, at 3:38 pm, Todd Kopriva <kopriva@adobe.com> wrote:

Here's something I just tweeted:

"to all who use CAP= S LOCK when rendering in After Effects: Don't. Dock Render Queue panel over C= omposition panel. Same result; less shouting."

I'm going to try to ge= t this change made in our Standard workspace, too.
+---End of message---+=
To unsubscribe send any message to <ae-list-off@media-motion.tv>



<= /body>= --Apple-Mail-C3FED47E-5ED4-423E-85D9-EBD8EC522CD0--