Return-Path: Received: from atl4mhob11.myregisteredsite.com ([209.17.115.49] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5266363 for AE-List@media-motion.tv; Sun, 27 Oct 2013 23:50:40 +0100 Received: from mailpod.hostingplatform.com ([10.30.71.210]) by atl4mhob11.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r9RMptEX008016 for ; Sun, 27 Oct 2013 18:51:55 -0400 Received: (qmail 15375 invoked by uid 0); 27 Oct 2013 22:51:55 -0000 X-TCPREMOTEIP: 60.225.197.206 X-Authenticated-UID: chris@chriszwar.com Received: from unknown (HELO ?192.168.0.3?) (chris@chriszwar.com@60.225.197.206) by 0 with ESMTPA; 27 Oct 2013 22:51:54 -0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: [AE] Quick AE Render question. From: Chris Zwar In-Reply-To: Date: Mon, 28 Oct 2013 09:51:52 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "After Effects Mail List" X-Mailer: Apple Mail (2.1510) > Any ideas here? Is multiprocessing on? Try turning it off. I still think that MP is = something of a black art to get right. There are some cases where MP is = slower than normal / single processor rendering and I guess it's related = to memory. If your source files are 16bit tiffs then it could also be a network / = storage bottleneck as they can get pretty big, pretty fast. It might be = that the drive with your tiffs on it can't keep up with multiple = processors asking for multiple images. Also, when using 16 bit tiffs make sure LZW compression is turned off. = It only works for 8 bit tiffs, and having it on for 16 bit tiffs will = create larger files that take longer to open. Also, things like motion blur and frame blending can really slow things = down and you won't notice them until you're rendering at best quality. = If you've been working and previewing without motion blur on, but have = it turned on for the layers, then that could easily account for the long = time calculating the transforms and compositing. -Chris=