Return-Path: Received: from qmta14.emeryville.ca.mail.comcast.net ([76.96.27.212] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5063915 for ae-list@media-motion.tv; Wed, 08 May 2013 01:38:00 +0200 Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta14.emeryville.ca.mail.comcast.net with comcast id ZBeX1l0021smiN4AEBmmMs; Tue, 07 May 2013 23:46:46 +0000 Received: from [192.168.1.4] ([98.245.75.227]) by omta20.emeryville.ca.mail.comcast.net with comcast id ZBmk1l00o4uEfTW8gBml9a; Tue, 07 May 2013 23:46:45 +0000 From: David Baud Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: multipart/alternative; boundary="Apple-Mail=_67B6C6F6-B437-4620-8E7F-4DA5FBBBBB76" Subject: Re: [AE] Best AE Render Settings for Long Footage Date: Tue, 7 May 2013 17:46:44 -0600 In-Reply-To: To: "After Effects Mail List" References: Message-Id: <99130E16-6468-49AF-9496-68A18A908FCB@gmail.com> X-Mailer: Apple Mail (2.1283) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1367970406; bh=mNPplzds/pLElBpCXF+p+hHm47y6xibkbYhOJs1Yvw0=; h=Received:Received:From:Mime-Version:Content-Type:Subject:Date:To: Message-Id; b=srAldUeT/jPHUXJMDyBGobgU8zB+2S/rJgWR+IkN3BW8fAwD6+BKNhREW6gFqYKVf to3Mrnt8sa+2BktixpgfQ5TAU8PNq63/N4TKavmeXLm2dv3Kcf03PKtqwR6g7Lbesp k/5pIFsvCwl2HrQUZHLwp8iUQKWufnv5Tetlfwf4/CLkqu5YLm52RHo7Kd3COfN0j1 YYsXVPolNVVQLdZvcOW/QhpWYDIub2JATXcp3UnYUuKBXj4ufQpgod1K9oGQo4ZVtc frsxF+STPr8HoILFwS0TwD9lQp0et463OX9gN2eug2d9j5mYrB8m0RoH5AmoJFLuz0 jJx4ODk2oN90A== --Apple-Mail=_67B6C6F6-B437-4620-8E7F-4DA5FBBBBB76 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I think the point is you are better off doing your render to an = intra-frame codec first and then compress that file to your liking. For = the compression, if you do not have a player/platform requirement, I = would go with H.264 at a low-bit rate (using an mp4 wrapper) With most = compression software now you can setup a watch folder so that you can = automatize that process. David Baud K O S M O S P R O D U C T i O N S david@kosmos-productions.com www.kosmos-productions.com On May 7, 2013, at 4:39 PM, patrick Siemer wrote: > I agree...DNX HD, or Pro-res or Photo Jpeg compressors are super fast. = Not as small as H264, but quality is great. > On May 7, 2013, at 2:28 PM, Steve Oakley wrote: >>=20 >> personally I'd probably output DNxHD 145 or ProRes LT unless you need = to push the file across the net on a slower connection. even then it = might be faster to output a ProRes file, then encode to h.264 >>=20 --Apple-Mail=_67B6C6F6-B437-4620-8E7F-4DA5FBBBBB76 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I = think the point is you are better off doing your render to an = intra-frame codec first and then compress that file to your liking. For = the compression, if you do not have a player/platform requirement, I = would go with H.264 at a low-bit rate (using an mp4 wrapper) With most = compression software now you can setup a watch folder so that you can = automatize that process.

David Baud

K O S M O S P R O = D U C T i O N = S

<= /span>

david@kosmos-productions.com<= /a>

www.kosmos-productions.com<= /span>

I = agree...DNX HD, or Pro-res or Photo Jpeg compressors are super fast. Not = as small as H264, but quality is = great.

On May = 7, 2013, at 2:28 PM, Steve Oakley wrote:

personally I'd probably output DNxHD 145 or ProRes LT = unless you need to push the file across the net on a slower connection. = even then it might be faster to output a ProRes file, then encode to = h.264

<= /html>= --Apple-Mail=_67B6C6F6-B437-4620-8E7F-4DA5FBBBBB76--