Return-Path: Received: from omr5.networksolutionsemail.com ([205.178.146.55] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4700308 for AE-List@media-motion.tv; Sun, 29 Apr 2012 03:03:10 +0200 Received: from cm-omr5 ([205.178.146.50]) by omr5.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id q3T14Pdg032039 for ; Sat, 28 Apr 2012 21:04:25 -0400 Authentication-Results: cm-omr5 smtp.user=chris@chriszwar.com; auth=pass (PLAIN) X-Authenticated-UID: chris@chriszwar.com Received: from [122.150.240.225] ([122.150.240.225:51324] helo=[192.168.0.5]) by cm-omr5 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id CB/C2-22294-8939C9F4; Sat, 28 Apr 2012 21:04:25 -0400 From: Chris Zwar Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-1-871977087 Subject: Re: [AE] Rendering Tiff Sequence Date: Sun, 29 Apr 2012 11:04:22 +1000 In-Reply-To: To: "After Effects Mail List" References: Message-Id: <091111F2-796E-4C6E-B473-858215F4FA39@chriszwar.com> X-Mailer: Apple Mail (2.1084) --Apple-Mail-1-871977087 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, It's important to know that the project rendering bit depth is unrelated = to the bit depth of the file format you're saving as. You can save an 8 = bit tiff, a 16 bit tiff or a floating point tiff regardless of whether = you render at 8,16 or 32 bpc. You will get a warning message if you = want to save a 16bit tiff while only rendering at 8 bit, but AE won't = stop you from doing it. If you use multiple output modules you can even = save all 3 versions at the same time, with only minimal increase in the = overall rendering time (not that there's any reason to do this, but know = that you can...) The rendering process is what takes up the time. Outputting the = rendered frame is negligible. How much slower it is to render at 16 or = 32 bit compared to 8 bit depends on the project, plugins, and the amount = of ram in your machine. In some cases rendering at 16 bit is not too = much slower than 8 bit, but unfortunately rendering at 32bit is much = slower again. In your case, if you tried rendering 32bpc with 8 instances of BG = render, I would suggest that you're running out of ram and this is = slowing down your entire machine. When you work at 16 bpc, you're = effectively halving the amount of stuff that can be stored in the image = cache, and if you render at 32bpc then you're reducing the effective = size of the image cache to a quarter. AE can quickly run out of memory, = and then things will slow to a crawl. You may get better results by = turning on multiple processing instead of using BG render, and = allocating each CPU at least 2GB ram. Or if your project uses lots of = ram, you may even get better results without multiple processing and = simply rendering within After Effects. But basically - saving a 16bit (trillions) tiff file is unrelated to the = time it takes to render something. -Chris=20 On 28/04/2012, at 2:30 AM, Rick wrote: > When I render in AE CS4 I render out to a TIFF sequence at millions of = colors and then go into Sony Vegas to mix it and render out an XDCamHD = file (or playout server format). Last night after making change 8 = billion to a :30 promo, I changed the comp to 32bit and changed the TIFF = Color Depth to Trillions. I meant to change it to 16bit, but I didn't = notice until this morning that I double punched it. I hit render last = night and it said 8.5 hours for the render. At 8bit, the render has = been taking around 20 minutes using the background render script and = running 8 instances of it. 4 each on 2 HP Z600's. >=20 > Anyway, I came in this morning and it had rendered only three frames = and took 31 minutes to do so based on the file time stamp. Is = 32bit/Trillions not a good combo? >=20 > Thanks, > =20 > Rick Emery > www.rickemery.com --Apple-Mail-1-871977087 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
When I render in AE CS4 = I render out to a TIFF sequence at millions of colors and then go into = Sony Vegas to mix it and render out an XDCamHD file (or playout server = format). Last night after making change 8 billion to a :30 promo, I = changed the comp to 32bit and changed the TIFF Color Depth to Trillions. = I meant to change it to 16bit, but I didn't notice until this morning = that I double punched it. I hit render  last night and it said 8.5 = hours for the render.  At 8bit, the render has been taking around = 20 minutes using the background render script and running 8 instances of = it. 4 each on  2 HP = Z600's.

Anyway, I = came in this morning and it had rendered only three frames and took 31 = minutes to do so based on the file time stamp. Is 32bit/Trillions not a = good = combo?

Thanks,
 
<= /blockquote>

= --Apple-Mail-1-871977087--