signature1

Return-Path: Received: from mail-pb0-f42.google.com ([209.85.160.42] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5431151 for AE-List@media-motion.tv; Fri, 11 Apr 2014 23:28:01 +0200 Received: by mail-pb0-f42.google.com with SMTP id rr13so5922005pbb.15 for ; Fri, 11 Apr 2014 14:29:43 -0700 (PDT) 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=U2Ll56GVASE+zHDY2b/VbWnRzYImeEXn0vlNhQAOaPM=; b=GULBB/a3A670tmEYEc/NTcUBNTg8rHmlx2zhHzO/5t7Fh0ZIQD1afashYI8rPSlAVu RFaGEvHdqw4ixwcMzVH/IyXWXIW1MwcePgmjvNfCRmuIS1KhVKVJYuZotshFW2B97cfC 8mV3qzqT/logQv5IJ6u9xhI0pMjErmf49eohrEJITkUlbj0mvWVStZUzyIv6HXMwpIvQ hZ8UG9kfxk/6TDbMeYl6qvFg4/iAS/nXYGS8XHEl/8UsSCbctshUDoKuWXrp6QWcEH3j Rd3LyWqtRk5aiLJH7Ccxjtm+wpk3ZQGplGeePLniA3U8l8dotLGxdo+eBLSDI/lCogiI HL0Q== X-Gm-Message-State: ALoCoQke41LGiJyu2jBnPBUB8DHHrUwDgRo6+UzdTn/wIxMvAbpPWAW/AJ9jPVZxcmBQs3Ds0q9C X-Received: by 10.68.163.197 with SMTP id yk5mr29993230pbb.57.1397251783112; Fri, 11 Apr 2014 14:29:43 -0700 (PDT) Return-Path: Received: from [10.0.0.180] ([65.223.58.66]) by mx.google.com with ESMTPSA id pv4sm17693409pbb.55.2014.04.11.14.29.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Apr 2014 14:29:42 -0700 (PDT) From: Phil Spitler Content-Type: multipart/alternative; boundary="Apple-Mail=_3373227D-1E22-4E7C-BFA3-026D974757CC" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: [AE] TIFF vs PNG vs other? Date: Fri, 11 Apr 2014 14:29:42 -0700 References: To: "After Effects Mail List" In-Reply-To: X-Mailer: Apple Mail (2.1510) --Apple-Mail=_3373227D-1E22-4E7C-BFA3-026D974757CC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I gave up on rendering image sequence out of AE, the time to compile = them into QT sucks. I tried all kinds of tricks including writing Apple scripts and using = command line tools to compile into QT files. What we do now is render to a bunch of QT files and join those. Joining = 50 QT files is so much quicker than joining 2000 still images. Phil Phil Spitler | Creative Technologist | Bonfire Labs | t : = 415.394.8200 m : 415.571.3139 Website | Facebook | LinkedIn On Apr 11, 2014, at 10:50 AM, scott.aelist = wrote: > Does anyone have any tips or a link for reading up on how to decide on = an image sequence format. I'm currently working on a project where we're = rendering 16bit 4k TIFF sequences, and then converting those to prores = or DNxHD. I feel like the sheer size of these TIFF sequences is really = slowing us down, both in reading the sequences into AE and server = traffic. Am I wrong in thinking we could speed things up using PNG or = another format? --Apple-Mail=_3373227D-1E22-4E7C-BFA3-026D974757CC Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1 I gave up on rendering image sequence out of AE, the time to compile them into QT sucks.

I tried all kinds of tricks including writing Apple scripts and using command line tools to compile into QT files.

What we do now is render to a bunch of QT files and join those. Joining 50 QT files is so much quicker than joining 2000 still images.

Phil

On Apr 11, 2014, at 10:50 AM, scott.aelist <scott.aelist@gmail.com> wrote:

Does anyone have any tips or a link for reading up on how to decide on an image sequence format. I'm currently working on a project where we're rendering 16bit 4k TIFF sequences, and then converting those to prores or DNxHD. I feel like the sheer size of these TIFF sequences is really slowing us down, both in reading the sequences into AE and server traffic. Am I wrong in thinking we could speed things up using PNG or another format?

--Apple-Mail=_3373227D-1E22-4E7C-BFA3-026D974757CC--