From: "D" Received: from mail-wg0-f44.google.com ([74.125.82.44] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5499221 for AE-List@media-motion.tv; Wed, 11 Jun 2014 17:15:30 +0200 Received: by mail-wg0-f44.google.com with SMTP id x13so6282454wgg.3 for ; Wed, 11 Jun 2014 08:15:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=i8y3OpjDbXvQQpmF7cSxKPRelq5hqZqa4EtkQR4zVi4=; b=gyhJT0ryDTSnOTw33tAhP/dFnsiCiT2mEBqVepvabaL/UjgC+yZUC+RuFDrSWTofmI PcJ7+PnbhvACfz2GSGUMLHftDdsREDM1lk7ndavEN/P6peOFDKo6Vy2md6BGRPsnr/xp ChcGqevscK8JVJr1eA/DZ/DkBOBPy61du+1AZlhVr/ETEz4GdkZ/MspjXNUBniHVYtT5 PodUYCjbitHXDAfdLxqmMixOtLc74eVpfE6j7poD/+ZrCV5tDFd5sByMW9/HcxQhSXeI 9JRL0csdrAcoKM+WBPDAoOhI2VNuwNtHeyUBHFEyKJXbkP7wVERtF0GpeBRTGCFCsEYY Zs/A== MIME-Version: 1.0 X-Received: by 10.194.79.36 with SMTP id g4mr50885282wjx.71.1402499727413; Wed, 11 Jun 2014 08:15:27 -0700 (PDT) Received: by 10.217.55.137 with HTTP; Wed, 11 Jun 2014 08:15:27 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 Jun 2014 16:15:27 +0100 Message-ID: Subject: Re: [AE] Lossless movie format To: After Effects Mail List Content-Type: multipart/alternative; boundary=047d7bb03ab80cda9704fb90eacd --047d7bb03ab80cda9704fb90eacd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Brendan, Don=E2=80=99t know where you=E2=80=99re at with a logo but here=E2=80=99s m= y idea: an open container with a play icon. https://www.dropbox.com/sh/5u3geff65ctg00i/AADbi5K2sx2Z6ad5rdSNoMCSa In my sketches I tried putting the letters M O X on each of the outer container faces, which kinda works as the letters all fit neatly in a square, but I kind of like the simplicity of this. Let me know what you think. I could work into it when I get some more time. Cheers. On 11 June 2014 10:06, Py Fave wrote: > motion control data , > tracking data, > perhaps a camera with accelerometers or optical tracking could > simplify stabilization , > and keep it in one file . > > btw in another topic : does someone have experience on a workflow with > such data files ? > > i feel the files should be "shot centered" > > and one important thing is that the format could be improved later > while keeping compatibility with older files , > and that older software can read newer files (discarding information > that it can't interpret) > > imagine you want to keep a camera projection mapping project in one file, > with data from shooting to video projection . > > this would be very new . > and useful. > > Thanks for this great project > > py > > > > > > > > > > > > > > 2014-06-11 1:50 GMT+02:00 David Baud : > > 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=E2=80=A6 of information!=E2=80=A6 who knows maybe a camera ma= nufacturer 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 differen= t > > tracks. Since EXR is already going to be a part of MOX, I guess > EXR-style > > channel access would make the most sense. > > > > > > +---End of message---+ > To unsubscribe send any message to > --047d7bb03ab80cda9704fb90eacd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Brendan,

Don=E2=80=99t know where yo= u=E2=80=99re at with a logo but here=E2=80=99s my idea: an open container w= ith a play icon.=C2=A0


In my sketches I tried putting the letters M O X = on each of the outer container faces, which kinda works as the letters all = fit neatly in a square, but I kind of like the simplicity of this. Let me k= now what you think. I could work into it when I get some more time.

Cheers.


<= div class=3D"gmail_quote">On 11 June 2014 10:06, Py Fave = <AE-List@me= dia-motion.tv> wrote:
motion control data ,
tracking data,
perhaps a camera with accelerometers or optical tracking could
simplify stabilization ,
and keep it in one file .

btw in another topic : does someone have experience on a workflow with
such data files ?

i feel the files should be "shot centered"

and one important thing is that the format could =C2=A0be improved later while keeping compatibility with older files ,
and that older software can read newer files (discarding information
that it can't interpret)

imagine you want to keep a camera projection mapping project in one file, with data from shooting to video projection .

this would be very new .
and useful.

Thanks for this great project

py













2014-06-11 1:50 GMT+02:00 David Baud <AE-List@media-motion.tv>:
> Yes I am also very much excite= d about MOX! A file format we could rely on
> for the full post-production workflow without being afraid to leave be= hind
> some bits=E2=80=A6 of information!=E2=80=A6 who knows maybe a camera m= anufacturer could even
> adopt it ;-)
>
> Like others have already mentioned it, I would love to have metadata i= n
> 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 =C2=A0 =C2=A0 P R O D U C T i O N S
> david@kosmos-productio= ns.com
> www.ko= smos-productions.com
>
>
> On Jun 10, 2014, at 15:20 , Brendan Bolles <AE-List@media-motion.tv> wrote:
>
> Yeah, I've been thinking about that one and it should be do-able. = =C2=A0MXF, like
> many container formats, lets you put any number of tracks into it. =C2= =A0The key
> will be coming up with a standard way to attach meaning to the differe= nt
> tracks. =C2=A0Since EXR is already going to be a part of MOX, I guess = EXR-style
> channel access would make the most sense.
>
>

+---End of message---+<= br> To unsubscribe send any message to <ae-list-off@media-motion.tv>

--047d7bb03ab80cda9704fb90eacd--