| ||||||||||
| 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 <AE-List@media-motion.tv>: > 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… of information!… 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 <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. > > |
