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 5472381 for AE-List@media-motion.tv; Tue, 13 May 2014 18:52:26 +0200 Received: from [10.0.1.10] (c-71-198-249-239.hsd1.ca.comcast.net [71.198.249.239]) by spike.lmi.net (Postfix) with ESMTP id 1A62D15406C for ; Tue, 13 May 2014 09:52:12 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: [AE] Lossless movie format From: Brendan Bolles In-Reply-To: Date: Tue, 13 May 2014 09:52:12 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "After Effects Mail List" X-Mailer: Apple Mail (2.1085) On May 13, 2014, at 9:16 AM, Py Fave wrote: > but one feature i see that could be needed is some frame by frame text=20= > that we could use to store standardly formatted data >=20 > perhaps xyz coordinates of some points, > to be used on playback time=20 > (driving lighting or motion controlled rig or anything else ) > and sound space information=20 >=20 > and subtitles=20 Good ideas all. Fortunately, I'm confident that the MXF container is = capable of holding subtitles and just about any kind of per-frame data. Granted, I don't think Premiere or After Effects have a mechanism to = provide me with those. Maybe Nuke? Brendan