Communigate Pro AE-List@media-motion.tv Message 54240

I'm very excited you are moving forward with this Brendan! I love the name(mox or MOX) too.

I second the comments made from everyone. I agree with Teddy that extra channels would be really helpful along with 32bit color as well. There aren't many options for rendering when you need 32bit or alpha channels. If you could make the channels arbitrary like openEXR, that would be even better. Being able to embed multiple alphas, or depth or some other thing into the video would be great.

Here's my summary

Open and Ubiquitous
cross platform
Extensible
Accurate color/gamma
32bit floating point color
arbitrary channels
metadata
fast
stable

On Mon, Jun 9, 2014 at 3:07 PM, Teddy Gage <AE-List@media-motion.tv> wrote:

What those guys said. Could not have said it better myself.

I would put in a vote for embedding codec within media file - is that even possible? seems tricky considering there may be revisions and updates to the source?

My request would be for EXR-like multiple layer support, but maybe that's asking too much. But even an extra channel or two for depth passes etc would be amazing. I've always wanted a PSD-like layered video file that didnt have the 32bit requirement overhead of EXR. You could export multiple tracks of animation at once, in a compressed 8bit format, like a layered video .tiff...

On Mon, Jun 9, 2014 at 2:03 PM, Steve Oakley <AE-List@media-motion.tv> wrote:

codecs not installed is the #1 problem of QT, especially ProRes on PC, or QT in general on PC. more of a problem with non-video types.

#2 gamma problems.

no one I work with uses OMF so I don't have those problems.

MXF Folders..."smart" producers who pull the media files out of the folders and hand those off :( but since this is going to be a single file format, not a problem.

so really the big goals should be :

no codec install problems - apps should natively support the format. however, as BACKUP having a QT/AVfoundation component might also be a good idea to get MOX files open in apps that due use QT but don't have native support. this might be really important to small developer's that don't have the resources of larger ones.

auto code updates - part of the API should be that if the codec is updated, the app can go pull it down from the web if its 1.2 and the file content is 2.0.

************ >>>>>>>

in fact here is an idea - Put the codec IN the media file as an option. this would guarantee codec install problems would never be a problem. its a minor bit of file bloat but if the actual codec code is a couple kb, even 50kb thats really nothing. this would solve all sorts of problems around users not having the latest codec, or correct one assuming down the road MOX opens up and extends to new codecs.

-----------------------

enough metadata to also have good gamma / FPS / log curve / Camera viewing LUT / TC interpretation by apps supporting the format. options like camera info would also be good.

S

On Jun 9, 2014, at 12:15 PM, Brendan Bolles <AE-List@media-motion.tv> wrote:

> On Jun 8, 2014, at 12:05 PM, Louai Abu-Osba wrote:
>
>> I hadn't realized this picked up again. I'm so beyond excited. I think MOX is a great name and I love the proposal.
>
>
> Thanks for the encouragement, Louai.
>
> I have a question for everyone: what have been your past struggles with existing file formats that you hope to solve with MOX?
>
> In other words: let's hear your rant about QuickTime/AVI/OMF/etc.
>
>
> Your responses will help me with the Kickstarter video and other messaging blah blah blah.
>
>
> Brendan
>
>
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>

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

--
_____________________________
VFX & Motion Graphic Artist
teddygage dot com