Return-Path: Received: from spike.lmi.net ([66.117.140.17] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4804563 for AE-List@media-motion.tv; Wed, 08 Aug 2012 04:38:37 +0200 Received: from [192.168.1.108] (c-76-24-199-52.hsd1.ma.comcast.net [76.24.199.52]) by spike.lmi.net (Postfix) with ESMTP id 9BB7A15415B for ; Tue, 7 Aug 2012 19:38:44 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: [AE] Compositing 3D render passes in AE From: Brendan Bolles In-Reply-To: Date: Tue, 7 Aug 2012 22:38:43 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "After Effects Mail List" X-Mailer: Apple Mail (2.1084) On Aug 7, 2012, at 6:28 PM, Teddy Gage wrote: > This brings up another question though - when rendering from a 32bit = project to an 8bit h264, how does AE tonemap the values? Does it = tonemap? is there a way to change this, or a filter to use? First of all, have you set your AE project to a linear color space? If = not, you'll get different results in AE than in Nuke, which always uses = a linear color space. Once you do that, you should be able to get the = exact same results with compositing your passes in AE that you would in = Nuke/Toxic because the math is the same. To answer your question, if there is no working space set, then AE will = directly convert your 32-bit 0.0-1.0 to 0-255 when it displays for the = screen or outputs H.264. If you use a linear working space, then AE = will preview the image with the sRGB curve and use that same curve when = converting to an 16- or 8-bit format. (That's the simple answer, = anyway.) The way to manage this stuff in AE is to set a project working space and = then check the color space being used in the output module. AE tries to = always show you what you'll end up looking at, doing all the necessary = color space conversions behind the scenes. Brendan