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 4754783 for AE-List@media-motion.tv; Fri, 22 Jun 2012 19:14:24 +0200 Received: from [192.168.1.143] (c-71-198-249-239.hsd1.ca.comcast.net [71.198.249.239]) by spike.lmi.net (Postfix) with ESMTP id 1683415402C for ; Fri, 22 Jun 2012 10:17:22 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: [AE] [PR] DPX Plus From: Brendan Bolles In-Reply-To: Date: Fri, 22 Jun 2012 10:17:22 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "After Effects Mail List" X-Mailer: Apple Mail (2.1084) On Jun 22, 2012, at 10:06 AM, rendernyc wrote: > whats the downside? since you mention youd rather us use the builtin = reader My main concern is that DPX Plus will now be loading the 10-bit DPXs as = well, so if you hand off your project to someone else they will need to = re-load the footage with the built-in reader. Wouldn't be an issue if = the built-in reader was the default. Also, AE's reader is a little faster and supports timecode. There's = currently no way for image sequence plug-ins to pass timecode to AE. Brendan