From: "David Baud" Received: from qmta08.emeryville.ca.mail.comcast.net ([76.96.30.80] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5498818 for ae-list@media-motion.tv; Wed, 11 Jun 2014 01:50:11 +0200 Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta08.emeryville.ca.mail.comcast.net with comcast id CnYC1o0031ZMdJ4A8nqAiv; Tue, 10 Jun 2014 23:50:10 +0000 Received: from [IPv6:2601:1:8200:284:2859:26a3:b586:805] ([IPv6:2601:1:8200:284:2859:26a3:b586:805]) by omta16.emeryville.ca.mail.comcast.net with comcast id Cnq91o0040KrhEe8cnq9so; Tue, 10 Jun 2014 23:50:10 +0000 Content-Type: multipart/alternative; boundary="Apple-Mail=_F940A534-4CD8-4DBE-A397-0AC06F23B0E4" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: [AE] Lossless movie format Date: Tue, 10 Jun 2014 17:50:08 -0600 References: To: After Effects Mail List In-Reply-To: X-Mailer: Apple Mail (2.1874) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1402444210; bh=+8SJSM/bJ81awJ/9EbkaZju/zeO3deCmPasTp3d5ZLE=; h=Received:Received:From:Content-Type:Message-Id:Mime-Version: Subject:Date:To; b=eMJ7TwLxOIhbTZghwgYyfM2VqDMJ0f9AmVCCIOADTu9m2M+SI/ovDJvTj9YNmVkcB DQ6CqXfeK0bPTQ6W9kZ82lcZ6/1NWX/qBCi9vcn6mhP50gYbjqnzfyFXKabCU7huK4 kP8uV4zDvSg/41rAFJhh6mcAyv/Qjuz06cQ2jPrLfeGX5q1NjM30WzwXOdR5a1pklr WSbu5kc8+v8Rlvi1rphhZSnvbYk/o6E7IK9EMk9sxQIrMKIVBLuN4Os3xMVQf7M//7 dVUAYKE1vycNMbWQwl+o4euvEQ7CxIQy9Bnqx+7KiPkduXWvu7FYu9RfXbA0IIAwSS shfToAxKZNtCA== --Apple-Mail=_F940A534-4CD8-4DBE-A397-0AC06F23B0E4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Yes I am also very much excited about MOX! A file format we could rely = on for the full post-production workflow without being afraid to leave = behind some bits=85 of information!=85 who knows maybe a camera = manufacturer could even adopt it ;-) Like others have already mentioned it, I would love to have metadata in = place with MOX, including LUTs so that we can confidently look at the = same things when opening a file from across the globe! How difficult will it be to implement them do you think? Thanks Brendan, 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 Jun 10, 2014, at 15:20 , Brendan Bolles = wrote: > Yeah, I've been thinking about that one and it should be do-able. = MXF, like many container formats, lets you put any number of tracks into = it. The key will be coming up with a standard way to attach meaning to = the different tracks. Since EXR is already going to be a part of MOX, I = guess EXR-style channel access would make the most sense. --Apple-Mail=_F940A534-4CD8-4DBE-A397-0AC06F23B0E4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Yes I = am also very much excited about MOX! A file format we could rely on for = the full post-production workflow without being afraid to leave behind = some bits=85 of information!=85 who knows maybe a camera manufacturer = could even adopt it ;-)

Like others have already = mentioned it, I would love to have metadata in place with MOX, including = LUTs so that we can confidently look at the same things when opening a = file from across the globe!
How difficult will it be to = implement them do you think?

Thanks = Brendan,

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>
AE-List@media-motion.tv> = wrote:

Yeah, I've been thinking about that one and it should be = do-able.  MXF, like many container formats, lets you put any number = of tracks into it.  The key will be coming up with a standard way = to attach meaning to the different tracks.  Since EXR is already = going to be a part of MOX, I guess EXR-style channel access would make = the most sense.

= --Apple-Mail=_F940A534-4CD8-4DBE-A397-0AC06F23B0E4--